"HTTP 400: Bad Request" - Reporting Services 2005

Question

Post reply

"HTTP 400: Bad Request" - Reporting Services 2005

caffeinated

Ten Centuries

Points: 1271
More actions
November 8, 2005 at 10:07 am

#165915

Has anyone ran into this error yet while testing Report Manager?
"The request failed with HTTP status 400: Bad Request."
I can deploy and access reports directly, but I receive the above error when hitting the http://localhost/Reports URL (i.e. ReportManager)
Also, I'm seeing DCOM errors in the NT event log whenever this happens.  A search in the registry find CLSID references to network components (Network Connection Manager Class, Network Connection Manager Connection Enumerator Class, LAN Connection Manager Class, etc). Any ideas? Is there a security configuration that I'm missing?
Here's an example entry:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date:  11/8/2005
Time:  8:23:48 AM
User:  NT AUTHORITY\NETWORK SERVICE
Computer: *SERVERNAME*
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

caffeinated Ten Centuries Points: 1271 More actions · Answer 1

fyi, I found the problem, here's the resolution...

IP Address Mapping

Reporting Services requires that the default Web site IP address is mapped to (All Unassigned). To verify this setting, open the Default Web Site Properties dialog box in Internet Information Services. The IP address is specified on the Web Site tab.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsinstall/htm/gs_installingrs_v1_8k82.asp

Pratul Patel SSC Journeyman Points: 79 More actions · Answer 2

Yes that's correct. It did solve my problem but anyway to solve that problem? We have multiple web sites on a box and cant do "All Unassigned" for the default web site.

caffeinated Ten Centuries Points: 1271 More actions · Answer 3

No, not yet. We moved reporting services to its own website, and it still came up with the same error when not mapped to "All Unassigned".

Some of the documents and forum posts I've been reading suggest it will be required to modify Reportmanager and ReportServices *.config files to set the correct URL. The default website is satisfying our requirements for now, but we'll need to do more research.

Tim Hatcher SSC Enthusiast Points: 145 More actions · Answer 4

Came accross this problem and have solved it

In the RSWebApplication.config file in the ReportManager folder for your SQL 2005 Reporting Services instance.

If you 2005 instance is called SQL2005 you will have the block of XML:

<UI>

<ReportServerVirtualDirectory>ReportServer$SQL2005</ReportServerVirtualDirectory>

<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>

</UI>

If you change this to:

<UI>

<ReportServerUrl>http://<Servername>/ReportServer$SQL2005</ReportServerUrl>

<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>

</UI>

All worked for me.

Tim

Amedeo Feroce SSChasing Mays Points: 607 More actions · Answer 5

Amedeo Feroce

SSChasing Mays

Points: 607

July 18, 2006 at 12:38 pm

#649907

Thanks Thuan! Your solution solved my problem!

Melissa Kenny SSC Rookie Points: 43 More actions · Answer 6

There's a subtle issue that I didn't catch when reading Tim's post. You can't specify both <ReportServerUrl> and <ReportServerVirtualDirectory>, so if you add a full URL for the <ReportServerUrl> value, you need to delete the <ReportServerVirtualDirectory> value.

Otherwise, this suggestion fixed my problem. The strange thing is that it had been working for months until it failed today. Go figure.

Melissa

ayla.donalson SSC Rookie Points: 45 More actions · Answer 7

Many thanks I had the same problem with my reporting server and this fixed it.

Ayla:)

Agustin Espinosa SSC Enthusiast Points: 141 More actions · Answer 8

Thanks Tim, I had the same problem and your solution fixed the issue.

dave-dj SSChampion Points: 11297 More actions · Answer 9

Tim,

I'm yet another person to benifit from your fix. 😀

Thanks - work like a charm

_____________________________________________________________________________MCITP: Business Intelligence Developer (2005)

becklery Hall of Fame Points: 3315 More actions · Answer 10

The account used to access data is the one in data sources not the service or app pool account. You can make sure the account is right and has permission by using SQL Reporting configuration tool.

Hope this helps.

RAQ Report: Web-based Excel-like Java reporting tool[/url]

Nic21 SSC Rookie Points: 41 More actions · Answer 11

I have same error message but with any document that i upload on the Report Manager. On the report server directly documents open but throught the Report manager I have :

The remote server returned an error: (400) Bad Request.

This is in the configuration file:

UI>

<ReportServerUrl>http://99.99.999.99/reportserver

</ReportServerUrl>

<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>

</UI>

<DefaultRenderingExtension>MHTML</DefaultRenderingExtension>

</RSEmailDPConfiguration>

</Configuration>

</Extension>

</DeliveryUI>

</Extensions>

Any idea what could be wrong. Just to mention that Mime types are added to the iis manager.