Critical Status - Database-Oriented Issues Plus

It seems that everything has a critical status, especially when it comes to databases and software development! Here's a place for listing issues and ideas relating to database and development issues. I'll list problems and ideas mainly related to SQL Server 2005. Post your thoughts, advice or complaints! Later this year will be the 25th anniversary of being in the trenches of the IT industry. I specialize in database applications development. I'd like to share my experiences with everyone and learn of those of others. You never stop learning.

Wednesday, November 12, 2008

Error When Deploying a Large RS Report Model
by David Leibowitz | May 30, 2008

You may recieve the error during the deployment of a Reporting Services model:
There was an exception running the extensions specified in the config file.
Maximum request length exceeded.
To correct, you need to increase the file size limit currently in place in the web.config on the RS Server.
Find the web.config file located in the directory:
[SQL Server Directory]/[MSSQL RS Instance]/Reporting Services/ReportServer
Locate the node and add the attribute maxRequestLength and a number, or simply modify the value until you increase the limit such that you can deploy.
Mine looked like this when I was done:

Save the file and redeploy. You can switch it back if you like when you are done deploying.

Full attribute listing for httpRuntime here:
http://msdn.microsoft.com/en-us/library/e1f13641(VS.80).aspx
http://jetlounge.net/blogs/teched/archive/2008/05/30/error-when-deploying-a-large-rs-report-model.aspx
Posted by at

1 comment:

daspeac said...

I have heard about another way of how to make a pdf file corrupted recovery. Besides, you can visit my blogs at: http://daspeac.livejournal.com/ or http://daspeac.blogspot.com/ where I’m trying to share my experience with regard to data corruption issues

October 30, 2010 at 9:14 AM

Post a Comment

Subscribe to: Post Comments (Atom)