HELP! Report Manager Error: HTTP status 400: Bad Request
in [Reports]
|
From: R Mariotti <R on 21 Mar 2006 17:22 Hello, I have been struggling with installing SQL Server 2005 Reporting services for several days now, so I figured that I?d post my experience on this TechNet to see if anyone has any suggestions. Basically, the Server Manager always returns ?The request failed with HTTP status 400: Bad Request.? I?ve read similar posts on TechNet, as well as other newsgroups about this issue, and I will note where I have tried a solution below. Details about the server this reporting services is being installed on is in NOTE 6, at the end of this message. When installing SQL Server 2005 Developer Edition (came with my Visual Studio 2005) on this server (for development/testing purposes), I choose to install both the SQL Server Database Engine as well as Reporting Services. As a test, I use the domain admin account, and install the new 2005 version as a named instance: ?DEVELOPMENT?. When the installation proceeds to the section to install Reporting Services, the install fails, with a note: ?Failed on Reporting Services setup: The setup has encountered an unexpected error while setting reporting service and share point exclusion path.? Sharepoint doesn?t appear to have anything to do with this (see NOTE 1). After Reporting Services fails to install, I have to click ?Cancel?, then re-install Reporting Services from Add/Remove Programs->SQL Server 2005->Change. During the reinstall, the option to "Install but do not configure the server" was preselected/disabled, so I had no option to install and configure. A ?Details?? button next to this revealed a message, NOTE 2. This re-install appears to be successful. Since I didn?t have the option to install AND configure, I then open Reporting Services Configuration, and connect to <server>, instance DEVELOPMENT. In Reporting Services Config, I proceed to install the Report Server and Report Manager Virtual Directories, give the Web Service the app pool of DefaultAppPool, and proceed to Database Setup. Since this is a new install and doesn?t have a Reports database, I click ?New?? to create the Reports db on server <server>\DEVELOPMENT using ?Service Credentials?. At this point, all ?Tasks? in the left pane of the Reports Services Config are check marks except for ?Encryption?, which has a !, but I understand this is optional. Now for IIS: In IIS, I see both the Reports and ReportServer virtual directories under Default Web Site, which currently listens on IP: 192.168.16.2, port 80 and 443 (SSL). In prior posts, I see some have achieved success by changing to ?All Unassigned?, but I have other web sites that listen on other IP addresses, so this is not a good option, and shouldn?t be required. The DefaultAppPool runs under Identity: ?Network Service?. When I go to http://cfsdev/ReportServer, things seem to work, as it just displays basic text, see NOTE 3. However, when I browse to: http://cfsdev/Reports, I am greeted with a red error image, along with ?The request failed with HTTP status 400: Bad Request.? There are no events in the Event Log when this happens. The only details on what?s happening behind the scenes is in a file E:\Program Files\SQL Server 2005\MSSQL.2\Reporting Services\LogFiles\ReportServerWebApp__03_21_2006_14_06_06.log, details in NOTE 4. I have, in prior attempts, changed the ReportServerURL key in the RSWebApplication.config file under Report Manager to: <ReportServerUrl>https://cfsdev/ReportServer</ReportServerUrl>, but still no change in behavior. It is currently changed back to it?s default, see NOTE 5. I get similar results when browsing from a LAN client or on the actual server computer. So I?m out of ideas, and I need this development installation to support and develop reporting apps for my production SQL Server 2005. Anyone with ideas, please help! -R. Mariotti NOTE 1: I have tried uninstalling SharePoint (http://support.microsoft.com/?kbid=829114), then retrying the install fresh (after an uninstall of SQL Server 2005), but the ?Failed on Reporting Services setup? error persists. So share point doesn?t appear to be the issue. NOTE 2: ?The prerequisite check failed for a default report server installation: First time install, the SQL instance is either not selected or is not a local install? NOTE 3: cfsdev/ReportServer - / ---------------------------------------------------------- ---------------------------------------------------------- Microsoft SQL Server Reporting Services Version 9.00.1399.00 NOTE 4: w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: The request failed with HTTP status 400: Bad Request. w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: HTTP status code --> 500 -------Details-------- System.Net.WebException: The request failed with HTTP status 400: Bad Request. at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods() at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods() at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname) at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection() at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level) at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) w3wp!ui!7!3/21/2006-14:06:22:: 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) NOTE 5: E:\Program Files\SQL Server 2005\MSSQL.2\Reporting Services\ReportManager\RSWebApplication.config: <UI> <ReportServerUrl></ReportServerUrl> <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory> <ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel> </UI> NOTE 6: Server: Windows Small Business Server 2003 SP1 ISA Server, Exchange 2003, SQL Server 2000 (Default instance)
From: HuttMan on 28 Mar 2006 19:31 Try setting your Default Website IP address to <All Unassigned>. Worked for me on a SQL 2000 RS installation today. "R Mariotti" wrote: > Hello, > > I have been struggling with installing SQL Server 2005 Reporting services > for several days now, so I figured that I?d post my experience on this > TechNet to see if anyone has any suggestions. Basically, the Server Manager > always returns ?The request failed with HTTP status 400: Bad Request.? I?ve > read similar posts on TechNet, as well as other newsgroups about this issue, > and I will note where I have tried a solution below. Details about the > server this reporting services is being installed on is in NOTE 6, at the end > of this message. > > When installing SQL Server 2005 Developer Edition (came with my Visual > Studio 2005) on this server (for development/testing purposes), I choose to > install both the SQL Server Database Engine as well as Reporting Services. > As a test, I use the domain admin account, and install the new 2005 version > as a named instance: ?DEVELOPMENT?. When the installation proceeds to the > section to install Reporting Services, the install fails, with a note: > > ?Failed on Reporting Services setup: > The setup has encountered an unexpected error while setting reporting > service and share point exclusion path.? > > Sharepoint doesn?t appear to have anything to do with this (see NOTE 1). > After Reporting Services fails to install, I have to click ?Cancel?, then > re-install Reporting Services from Add/Remove Programs->SQL Server > 2005->Change. During the reinstall, the option to "Install but do not > configure the server" was preselected/disabled, so I had no option to install > and configure. A ?Details?? button next to this revealed a message, NOTE 2. > This re-install appears to be successful. Since I didn?t have the option to > install AND configure, I then open Reporting Services Configuration, and > connect to <server>, instance DEVELOPMENT. > > In Reporting Services Config, I proceed to install the Report Server and > Report Manager Virtual Directories, give the Web Service the app pool of > DefaultAppPool, and proceed to Database Setup. Since this is a new install > and doesn?t have a Reports database, I click ?New?? to create the Reports db > on server <server>\DEVELOPMENT using ?Service Credentials?. At this point, > all ?Tasks? in the left pane of the Reports Services Config are check marks > except for ?Encryption?, which has a !, but I understand this is optional. > Now for IIS: > > In IIS, I see both the Reports and ReportServer virtual directories under > Default Web Site, which currently listens on IP: 192.168.16.2, port 80 and > 443 (SSL). In prior posts, I see some have achieved success by changing to > ?All Unassigned?, but I have other web sites that listen on other IP > addresses, so this is not a good option, and shouldn?t be required. The > DefaultAppPool runs under Identity: ?Network Service?. > > When I go to http://cfsdev/ReportServer, things seem to work, as it just > displays basic text, see NOTE 3. However, when I browse to: > http://cfsdev/Reports, I am greeted with a red error image, along with ?The > request failed with HTTP status 400: Bad Request.? There are no events in > the Event Log when this happens. The only details on what?s happening behind > the scenes is in a file E:\Program Files\SQL Server 2005\MSSQL.2\Reporting > Services\LogFiles\ReportServerWebApp__03_21_2006_14_06_06.log, details in > NOTE 4. > > I have, in prior attempts, changed the ReportServerURL key in the > RSWebApplication.config file under Report Manager to: > <ReportServerUrl>https://cfsdev/ReportServer</ReportServerUrl>, but still no > change in behavior. It is currently changed back to it?s default, see NOTE > 5. I get similar results when browsing from a LAN client or on the actual > server computer. > > So I?m out of ideas, and I need this development installation to support and > develop reporting apps for my production SQL Server 2005. Anyone with ideas, > please help! > > -R. Mariotti > > > NOTE 1: > I have tried uninstalling SharePoint > (http://support.microsoft.com/?kbid=829114), then retrying the install fresh > (after an uninstall of SQL Server 2005), but the ?Failed on Reporting > Services setup? error persists. So share point doesn?t appear to be the > issue. > > NOTE 2: > ?The prerequisite check failed for a default report server installation: > First time install, the SQL instance is either not selected or is not a > local install? > > NOTE 3: > cfsdev/ReportServer - / > ---------------------------------------------------------- > ---------------------------------------------------------- > Microsoft SQL Server Reporting Services Version 9.00.1399.00 > > NOTE 4: > w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: The request failed with HTTP status > 400: Bad Request. > w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: HTTP status code --> 500 > -------Details-------- > System.Net.WebException: The request failed with HTTP status 400: Bad Request. > at > Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods() > at > Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods() > at > Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String > methodname) > at > Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection() > at > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel > level) > at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object > sender, EventArgs args) > at System.EventHandler.Invoke(Object sender, EventArgs e) > at System.Web.UI.Control.OnInit(EventArgs e) > at System.Web.UI.Page.OnInit(EventArgs e) > at System.Web.UI.Control.InitRecursive(Control namingContainer) > at System.Web.UI.Page.ProcessRequestMain(Boolean > includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) > w3wp!ui!7!3/21/2006-14:06:22:: 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) > > > NOTE 5: > E:\Program Files\SQL Server 2005\MSSQL.2\Reporting > Services\ReportManager\RSWebApplication.config: > <UI> > <ReportServerUrl></ReportServerUrl> > <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory> > <ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel> > </UI> > > NOTE 6: > Server: Windows Small Business Server 2003 SP1 > ISA Server, Exchange 2003, SQL Server 2000 (Default instance) >
From: R Mariotti on 29 Mar 2006 12:42 Yeah, I had read that solution a few times during my research. Problem is, the machine is a SBS2003 machine and therefore runs ISA Server with an internal and external NIC. Additionally, the internal NIC hosts multiple web sites on different IPs. For example: ROUTER | 192.168.1.2 (external NIC) | ISA SERVER | 192.168.16.2 (web site 1) 192.168.16.3 (web site 2) So you can see that setting "All Unassigned" won't work as I need ISA Server's web publishing rules to be able to forward requests to a specific site. As a test, however, I created yet another test web site, manually re-created the "reports" and "reportserver" virtual directories, and set the site to All Unassigned. Still no luck; that test site has since been removed. Thanks for the suggestion... R. Mariotti "HuttMan" wrote: > Try setting your Default Website IP address to <All Unassigned>. Worked for > me on a SQL 2000 RS installation today. > > "R Mariotti" wrote: > > > Hello, > > > > I have been struggling with installing SQL Server 2005 Reporting services > > for several days now, so I figured that I?d post my experience on this > > TechNet to see if anyone has any suggestions. Basically, the Server Manager > > always returns ?The request failed with HTTP status 400: Bad Request.? I?ve > > read similar posts on TechNet, as well as other newsgroups about this issue, > > and I will note where I have tried a solution below. Details about the > > server this reporting services is being installed on is in NOTE 6, at the end > > of this message. > > > > When installing SQL Server 2005 Developer Edition (came with my Visual > > Studio 2005) on this server (for development/testing purposes), I choose to > > install both the SQL Server Database Engine as well as Reporting Services. > > As a test, I use the domain admin account, and install the new 2005 version > > as a named instance: ?DEVELOPMENT?. When the installation proceeds to the > > section to install Reporting Services, the install fails, with a note: > > > > ?Failed on Reporting Services setup: > > The setup has encountered an unexpected error while setting reporting > > service and share point exclusion path.? > > > > Sharepoint doesn?t appear to have anything to do with this (see NOTE 1). > > After Reporting Services fails to install, I have to click ?Cancel?, then > > re-install Reporting Services from Add/Remove Programs->SQL Server > > 2005->Change. During the reinstall, the option to "Install but do not > > configure the server" was preselected/disabled, so I had no option to install > > and configure. A ?Details?? button next to this revealed a message, NOTE 2. > > This re-install appears to be successful. Since I didn?t have the option to > > install AND configure, I then open Reporting Services Configuration, and > > connect to <server>, instance DEVELOPMENT. > > > > In Reporting Services Config, I proceed to install the Report Server and > > Report Manager Virtual Directories, give the Web Service the app pool of > > DefaultAppPool, and proceed to Database Setup. Since this is a new install > > and doesn?t have a Reports database, I click ?New?? to create the Reports db > > on server <server>\DEVELOPMENT using ?Service Credentials?. At this point, > > all ?Tasks? in the left pane of the Reports Services Config are check marks > > except for ?Encryption?, which has a !, but I understand this is optional. > > Now for IIS: > > > > In IIS, I see both the Reports and ReportServer virtual directories under > > Default Web Site, which currently listens on IP: 192.168.16.2, port 80 and > > 443 (SSL). In prior posts, I see some have achieved success by changing to > > ?All Unassigned?, but I have other web sites that listen on other IP > > addresses, so this is not a good option, and shouldn?t be required. The > > DefaultAppPool runs under Identity: ?Network Service?. > > > > When I go to http://cfsdev/ReportServer, things seem to work, as it just > > displays basic text, see NOTE 3. However, when I browse to: > > http://cfsdev/Reports, I am greeted with a red error image, along with ?The > > request failed with HTTP status 400: Bad Request.? There are no events in > > the Event Log when this happens. The only details on what?s happening behind > > the scenes is in a file E:\Program Files\SQL Server 2005\MSSQL.2\Reporting > > Services\LogFiles\ReportServerWebApp__03_21_2006_14_06_06.log, details in > > NOTE 4. > > > > I have, in prior attempts, changed the ReportServerURL key in the > > RSWebApplication.config file under Report Manager to: > > <ReportServerUrl>https://cfsdev/ReportServer</ReportServerUrl>, but still no > > change in behavior. It is currently changed back to it?s default, see NOTE > > 5. I get similar results when browsing from a LAN client or on the actual > > server computer. > > > > So I?m out of ideas, and I need this development installation to support and > > develop reporting apps for my production SQL Server 2005. Anyone with ideas, > > please help! > > > > -R. Mariotti > > > > > > NOTE 1: > > I have tried uninstalling SharePoint > > (http://support.microsoft.com/?kbid=829114), then retrying the install fresh > > (after an uninstall of SQL Server 2005), but the ?Failed on Reporting > > Services setup? error persists. So share point doesn?t appear to be the > > issue. > > > > NOTE 2: > > ?The prerequisite check failed for a default report server installation: > > First time install, the SQL instance is either not selected or is not a > > local install? > > > > NOTE 3: > > cfsdev/ReportServer - / > > ---------------------------------------------------------- > > ---------------------------------------------------------- > > Microsoft SQL Server Reporting Services Version 9.00.1399.00 > > > > NOTE 4: > > w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: The request failed with HTTP status > > 400: Bad Request. > > w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: HTTP status code --> 500 > > -------Details-------- > > System.Net.WebException: The request failed with HTTP status 400: Bad Request. > > at > > Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods() > > at > > Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods() > > at > > Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String > > methodname) > > at > > Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection() > > at > > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel > > level) > > at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object > > sender, EventArgs args) > > at System.EventHandler.Invoke(Object sender, EventArgs e) > > at System.Web.UI.Control.OnInit(EventArgs e) > > at System.Web.UI.Page.OnInit(EventArgs e) > > at System.Web.UI.Control.InitRecursive(Control namingContainer) > > at System.Web.UI.Page.ProcessRequestMain(Boolean > > includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) > > w3wp!ui!7!3/21/2006-14:06:22:: 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) > > > > > > NOTE 5: > > E:\Program Files\SQL Server 2005\MSSQL.2\Reporting > > Services\ReportManager\RSWebApplication.config: > > <UI> > > <ReportServerUrl></ReportServerUrl> > > <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory> > > <ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel> > > </UI> > > > > NOTE 6: > > Server: Windows Small Business Server 2003 SP1 > > ISA Server, Exchange 2003, SQL Server 2000 (Default instance) > >
From: Sean on 29 Mar 2006 20:20 The below solution is working for me. 1) make up backup copy of both Rsreportserver and RSwebapplication.config files 2) In RsReportServer.config file change the <UrlRoot>http://machine/ReportServer</UrlRoot> to <UrlRoot>http://hostheadername/ReportServer</UrlRoot> 3) And in RSWebapplication.config file, remove the <ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory> and change the <ReportServerUrl>http://machinename/ReportServer</ReportServerUrl> to <ReportServerUrl>http://hostheadername/ReportServer</ReportServerUrl> 4) Recycle the IIS server (ie. start ? run ? iisreset) "R Mariotti" wrote: > Hello, > > I have been struggling with installing SQL Server 2005 Reporting services > for several days now, so I figured that I?d post my experience on this > TechNet to see if anyone has any suggestions. Basically, the Server Manager > always returns ?The request failed with HTTP status 400: Bad Request.? I?ve > read similar posts on TechNet, as well as other newsgroups about this issue, > and I will note where I have tried a solution below. Details about the > server this reporting services is being installed on is in NOTE 6, at the end > of this message. > > When installing SQL Server 2005 Developer Edition (came with my Visual > Studio 2005) on this server (for development/testing purposes), I choose to > install both the SQL Server Database Engine as well as Reporting Services. > As a test, I use the domain admin account, and install the new 2005 version > as a named instance: ?DEVELOPMENT?. When the installation proceeds to the > section to install Reporting Services, the install fails, with a note: > > ?Failed on Reporting Services setup: > The setup has encountered an unexpected error while setting reporting > service and share point exclusion path.? > > Sharepoint doesn?t appear to have anything to do with this (see NOTE 1). > After Reporting Services fails to install, I have to click ?Cancel?, then > re-install Reporting Services from Add/Remove Programs->SQL Server > 2005->Change. During the reinstall, the option to "Install but do not > configure the server" was preselected/disabled, so I had no option to install > and configure. A ?Details?? button next to this revealed a message, NOTE 2. > This re-install appears to be successful. Since I didn?t have the option to > install AND configure, I then open Reporting Services Configuration, and > connect to <server>, instance DEVELOPMENT. > > In Reporting Services Config, I proceed to install the Report Server and > Report Manager Virtual Directories, give the Web Service the app pool of > DefaultAppPool, and proceed to Database Setup. Since this is a new install > and doesn?t have a Reports database, I click ?New?? to create the Reports db > on server <server>\DEVELOPMENT using ?Service Credentials?. At this point, > all ?Tasks? in the left pane of the Reports Services Config are check marks > except for ?Encryption?, which has a !, but I understand this is optional. > Now for IIS: > > In IIS, I see both the Reports and ReportServer virtual directories under > Default Web Site, which currently listens on IP: 192.168.16.2, port 80 and > 443 (SSL). In prior posts, I see some have achieved success by changing to > ?All Unassigned?, but I have other web sites that listen on other IP > addresses, so this is not a good option, and shouldn?t be required. The > DefaultAppPool runs under Identity: ?Network Service?. > > When I go to http://cfsdev/ReportServer, things seem to work, as it just > displays basic text, see NOTE 3. However, when I browse to: > http://cfsdev/Reports, I am greeted with a red error image, along with ?The > request failed with HTTP status 400: Bad Request.? There are no events in > the Event Log when this happens. The only details on what?s happening behind > the scenes is in a file E:\Program Files\SQL Server 2005\MSSQL.2\Reporting > Services\LogFiles\ReportServerWebApp__03_21_2006_14_06_06.log, details in > NOTE 4. > > I have, in prior attempts, changed the ReportServerURL key in the > RSWebApplication.config file under Report Manager to: > <ReportServerUrl>https://cfsdev/ReportServer</ReportServerUrl>, but still no > change in behavior. It is currently changed back to it?s default, see NOTE > 5. I get similar results when browsing from a LAN client or on the actual > server computer. > > So I?m out of ideas, and I need this development installation to support and > develop reporting apps for my production SQL Server 2005. Anyone with ideas, > please help! > > -R. Mariotti > > > NOTE 1: > I have tried uninstalling SharePoint > (http://support.microsoft.com/?kbid=829114), then retrying the install fresh > (after an uninstall of SQL Server 2005), but the ?Failed on Reporting > Services setup? error persists. So share point doesn?t appear to be the > issue. > > NOTE 2: > ?The prerequisite check failed for a default report server installation: > First time install, the SQL instance is either not selected or is not a > local install? > > NOTE 3: > cfsdev/ReportServer - / > ---------------------------------------------------------- > ---------------------------------------------------------- > Microsoft SQL Server Reporting Services Version 9.00.1399.00 > > NOTE 4: > w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: The request failed with HTTP status > 400: Bad Request. > w3wp!ui!7!3/21/2006-14:06:21:: e ERROR: HTTP status code --> 500 > -------Details-------- > System.Net.WebException: The request failed with HTTP status 400: Bad Request. > at > Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods() > at > Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods() > at > Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String > methodname) > at > Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection() > at > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel > level) > at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object > sender, EventArgs args) > at System.EventHandler.Invoke(Object sender, EventArgs e) > at System.Web.UI.Control.OnInit(EventArgs e) > at System.Web.UI.Page.OnInit(EventArgs e) > at System.Web.UI.Control.InitRecursive(Control namingContainer) > at System.Web.UI.Page.ProcessRequestMain(Boolean > includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) > w3wp!ui!7!3/21/2006-14:06:22:: 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) > > > NOTE 5: > E:\Program Files\SQL Server 2005\MSSQL.2\Reporting > Services\ReportManager\RSWebApplication.config: > <UI> > <ReportServerUrl></ReportServerUrl> > <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory> > <ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel> > </UI> > > NOTE 6: > Server: Windows Small Business Server 2003 SP1 > ISA Server, Exchange 2003, SQL Server 2000 (Default instance) >
|
Pages: 1 Prev: ReportViewer error Next: Email subscriptions not working - SSRS 2005 |