sql server reporting services: I am getting this error when I try to upload an rpt in the the Reports
Manager web site.

"The request failed with HTTP status 413: Request Entity Too Large."

I can upload an rpt that is 12k but not 30k. I did get an error after
install that said it could not activare the reportservice and that I would
need to do it manually. I did that and it reported success. Everything else
appears to be working. I can upload VERY SMALL reports and run them but when
the rpt get over a certain size it fails with the error above. I don't know
what that size is exactly, but 30k will not upload.

I have turned on verbose logging to see what is going on. Here is the
ReportsServerWebApp log contents. I have replaced the machinename and
username with XXXXX:

<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.878.00</Product>
<Locale>en-US</Locale>
<TimeZone>US Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__12_15_2004_16_55_24.log</Path>
<SystemName>XXXXXX</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing MaxScheduleWait
to default value of '1' second(s) because it was not specified in
Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
DatabaseQueryTimeout to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing InstanceName to
default value of 'MSSQLSERVER.1' because it was not specified in
Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
ProcessRecycleOptions to default value of '0' because it was not specified
in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
RunningRequestsScavengerCycle to default value of '30' second(s) because it
was not specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
RunningRequestsDbCycle to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
RunningRequestsAge to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
CleanupCycleMinutes to default value of '10' minute(s) because it was not
specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not specified
in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing DisplayErrorLink
to 'True' as specified in Configuration file.
w3wp!library!ba0!12/15/2004-16:55:24:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!ui!ba0!12/15/2004-16:55:24:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!ba0!12/15/2004-16:55:37:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Import.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!970!12/15/2004-16:55:42:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!55c!12/15/2004-16:55:46:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!55c!12/15/2004-16:55:48:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!970!12/15/2004-16:55:49:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!ba0!12/15/2004-16:55:51:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Import.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!7dc!12/15/2004-16:55:57:: v VERBOSE: User
map'<Users><User><Name>XXXXX</Name><Paths><Path>/Reports/Pages/Import.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
w3wp!ui!7dc!12/15/2004-16:55:57:: e ERROR: The request failed with HTTP
status 413: Request Entity Too Large.
w3wp!ui!7dc!12/15/2004-16:55:57:: e ERROR: HTTP status code --> 500
-------Details--------
System.Net.WebException: The request failed with HTTP status 413: Request
Entity Too Large.

at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)

at
Microsoft.SqlServer.ReportingServices.ReportingService.CreateReport(String
Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[]
Properties)

at Microsoft.SqlServer.ReportingServices.RSConnection.CreateReport(String
Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[]
Properties)

at Microsoft.ReportingServices.UI.ImportPageCtrl.ApplyChanges()

at Microsoft.ReportingServices.UI.BaseApplyPage.ApplyBtn_Click(Object
sender, EventArgs e)

at Microsoft.ReportingServices.UI.ScriptButton.OnClick(EventArgs e)

at Microsoft.ReportingServices.UI.ScriptButton.RaisePostBackEvent(String
eventArgument)

at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)

at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)

at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!7dc!12/15/2004-16:56:03:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)

Any help would be great. Thanks, Jason

Jason,

I'm having the same problem getting this error when trying to upload
files larger than ~15K

"The request failed with HTTP status 413: Request Entity Too Large"

Looked in logs, pulled up a sniffer but aren't having much luck at this
time.

Did you get this resolved?

Thanks!

Paul

SOLVED.......

Snippet from:

http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/q=
ss_wss_troubleshooting.mspx

Internet Information Services 6.0 Product Documentation
Troubleshooting

SNIP =EF=83=A8
Client Cannot Negotiate Request and Returns an HTTP 413 Error
If client certificates are enabled on a Web server, Web site, or on
individual directories or files on the site, clients might see an HTTP
413 error when uploading large files.
If a client sends a long HTTP request, for example, a POST request, to
a Web server running IIS 6.0, the IIS worker process might receive
enough data to parse request headers, but not receive the entire
request entity body. When the IIS worker process detects that client
certificates are required to return data to the client, IIS attempts to
renegotiate the client connection. However, the client cannot
renegotiate the connection because it is waiting to send the remaining
request data to IIS.
If client renegotiation is requested, the request entity body must be
preloaded using SSL preload. SSL preload will use the value of the
UploadReadAheadSize metabase property, which is used for ISAPI
extensions. However, if UploadReadAheadSize is smaller than the content
length, an HTTP 413 error is returned, and the connection is closed to
prevent deadlock. (Deadlock occurs because a client is waiting to
complete sending a request entity, while the server is waiting for
renegotiation to complete, but renegotiation requires that the client
to be able to send data, which it cannot do).
The solution is to ensure that client is not blocked from sending the
entire entity body. To do so, change the value of UploadReadAheadSize
to a value larger than the content length.
The following example shows how to set the value for
UploadReadAheadSize to 200KB on the Web server.
cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 200 **WARNING NOT
CORRECT**
For more information about UploadReadAheadSize, see
UploadReadAheadSize.
=EF=83=A7 ENDSNIP
I believe that the parameter is a byte value not a KB value as after
running the command, with any interaction with the /reports site, I
rec=E2=80=99d the error:

=E2=80=9CThe request failed with HTTP status 413: Request Entity Too Large=
=E2=80=9D

i=2Ee I couldn=E2=80=99t do anything

My suggestion is to do a =E2=80=9Cget=E2=80=9D 1st to determine what the =
original
value is

cscript adsutil.vbs get w3svc/1/uploadreadaheadsize

Assuming that it is indeed a byte value, I set it to 200,000 bytes per
the following

cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 200000

I just uploaded my largest report file of 76KB with no problems

I=E2=80=99d like to know what caused this problem in the 1st place =E2=80=
=93 if
anybody has any ideas, I=E2=80=99d be interested.

Thanks,

Paul