Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


"HTTP 400: Bad Request" - Reporting Services 2005


"HTTP 400: Bad Request" - Reporting Services 2005

Author
Message
caffeinated
caffeinated
Valued Member
Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)

Group: General Forum Members
Points: 50 Visits: 234

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.


caffeinated
caffeinated
Valued Member
Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)

Group: General Forum Members
Points: 50 Visits: 234

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
Pratul Patel
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 5
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
caffeinated
Valued Member
Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)Valued Member (50 reputation)

Group: General Forum Members
Points: 50 Visits: 234

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
Tim Hatcher
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 59

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>
<ReportServerUrl></ReportServerUrl>
<ReportServerVirtualDirectory>ReportServer$SQL2005</ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>

If you change this to:

<UI>
<ReportServerUrl>http://<Servername>/ReportServer$SQL2005</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>

All worked for me.

Tim


Amedeo Feroce
Amedeo Feroce
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 36
Thanks Thuan! Your solution solved my problem!
Melissa Kenny
Melissa Kenny
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 2

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
ayla.donalson
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 2
Many thanks I had the same problem with my reporting server and this fixed it.
AylaSmile
Agustin Espinosa
Agustin Espinosa
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 174
Thanks Tim, I had the same problem and your solution fixed the issue.
dave-dj
dave-dj
SSC-Addicted
SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)SSC-Addicted (438 reputation)

Group: General Forum Members
Points: 438 Visits: 1149
Tim,

I'm yet another person to benifit from your fix. :-D

Thanks - work like a charm

_____________________________________________________________________________
MCITP: Business Intelligence Developer (2005)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search