2003 Server SP1 broke Reporting Services

Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
request failed with HTTP status 401: Unauthorized." I've re-set the database
credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
Any help would be appreciated.Sounds like ASP.NET permissions issue. What is the application pool set to
run as?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"geoff" <geoff@.discussions.microsoft.com> wrote in message
news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> "The
> request failed with HTTP status 401: Unauthorized." I've re-set the
> database
> credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> it.
> Any help would be appreciated.|||It is set to run as Network Service account. The ReportServer service is in
fact running as Network Service.
"Brian Welcker [MSFT]" wrote:
> Sounds like ASP.NET permissions issue. What is the application pool set to
> run as?
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "geoff" <geoff@.discussions.microsoft.com> wrote in message
> news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> > "The
> > request failed with HTTP status 401: Unauthorized." I've re-set the
> > database
> > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> > it.
> > Any help would be appreciated.
>
>|||Hi,
I get the same thing running SQL Server Reporting Services SP 1 on Server
2003 Enterprise Edition with SP 1.
The location of SQLRS is non-standard in that the site running SQLRS will
only respond to a FQDN through the host header. It all worked before so I
know it is not a configuration issue.
You can see the reports folder by entering http://xxx.xxxxx.xxx/reportserver
and then navigating to a report. Also, the scheduled report tasks run ok.
Here is a copy of the error from the log:
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.878.00</Product>
<Locale>en-US</Locale>
<TimeZone>GMT Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
<SystemName>SWIPER</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing MaxScheduleWait
to default value of '1' second(s) because it was not specified in
Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
DatabaseQueryTimeout to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing InstanceName to
default value of 'MSSQLSERVER.1' because it was not specified in
Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
ProcessRecycleOptions to default value of '0' because it was not specified
in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
RunningRequestsScavengerCycle to default value of '30' second(s) because it
was not specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
RunningRequestsDbCycle to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
RunningRequestsAge to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
CleanupCycleMinutes to default value of '10' minute(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not specified
in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
status 401: Unauthorized.
w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The request failed with HTTP status 401:
Unauthorized.
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.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
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.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1b70!02/04/2005-09:20:58:: 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)
Cheers
Glen
"geoff" wrote:
> It is set to run as Network Service account. The ReportServer service is in
> fact running as Network Service.
> "Brian Welcker [MSFT]" wrote:
> > Sounds like ASP.NET permissions issue. What is the application pool set to
> > run as?
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> > > "The
> > > request failed with HTTP status 401: Unauthorized." I've re-set the
> > > database
> > > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> > > it.
> > > Any help would be appreciated.
> >
> >
> >|||I can browse as you suggest and the scheduled reports do run. I can browse
the reports folder as you suggest through .../reportserver, but I can do so
without using the FQDN as well. I can't get anything to work with .../reports
I have my SQL Report Server database on another box...don't know if this is
impacting anything.
Hopefully MSFT will help us out on this one.
"GlenConway" wrote:
> Hi,
> I get the same thing running SQL Server Reporting Services SP 1 on Server
> 2003 Enterprise Edition with SP 1.
> The location of SQLRS is non-standard in that the site running SQLRS will
> only respond to a FQDN through the host header. It all worked before so I
> know it is not a configuration issue.
> You can see the reports folder by entering http://xxx.xxxxx.xxx/reportserver
> and then navigating to a report. Also, the scheduled report tasks run ok.
> Here is a copy of the error from the log:
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.878.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>GMT Daylight Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
> <SystemName>SWIPER</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing MaxScheduleWait
> to default value of '1' second(s) because it was not specified in
> Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> DatabaseQueryTimeout to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing InstanceName to
> default value of 'MSSQLSERVER.1' because it was not specified in
> Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> ProcessRecycleOptions to default value of '0' because it was not specified
> in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> RunningRequestsScavengerCycle to default value of '30' second(s) because it
> was not specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> RunningRequestsDbCycle to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> RunningRequestsAge to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> CleanupCycleMinutes to default value of '10' minute(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> SecureConnectionLevel to default value of '1' because it was not specified
> in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> DisplayErrorLink to 'True' as specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> WebServiceUseFileShareStorage to default value of 'False' because it was not
> specified in Configuration file.
> w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
> status 401: Unauthorized.
> w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The request failed with HTTP status 401:
> Unauthorized.
> 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.ListSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> 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.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!1b70!02/04/2005-09:20:58:: 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)
> Cheers
> Glen
>
> "geoff" wrote:
> > It is set to run as Network Service account. The ReportServer service is in
> > fact running as Network Service.
> >
> > "Brian Welcker [MSFT]" wrote:
> >
> > > Sounds like ASP.NET permissions issue. What is the application pool set to
> > > run as?
> > >
> > > --
> > > Brian Welcker
> > > Group Program Manager
> > > Microsoft SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > > Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> > > > "The
> > > > request failed with HTTP status 401: Unauthorized." I've re-set the
> > > > database
> > > > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> > > > it.
> > > > Any help would be appreciated.
> > >
> > >
> > >|||Same here,
same error, sysadmin is unauthorized to http://localhost/Reports,
I can browse and see the files...
any suggestion other than uninstall the SP1?
Thank you,
--
ejr
"geoff" <geoff@.discussions.microsoft.com> wrote in message
news:97FDD47E-4BCD-4A15-8FD0-B342920FAD78@.microsoft.com...
> I can browse as you suggest and the scheduled reports do run. I can
browse
> the reports folder as you suggest through .../reportserver, but I can do
so
> without using the FQDN as well. I can't get anything to work with
.../reports
> I have my SQL Report Server database on another box...don't know if this
is
> impacting anything.
> Hopefully MSFT will help us out on this one.
> "GlenConway" wrote:
> > Hi,
> >
> > I get the same thing running SQL Server Reporting Services SP 1 on
Server
> > 2003 Enterprise Edition with SP 1.
> >
> > The location of SQLRS is non-standard in that the site running SQLRS
will
> > only respond to a FQDN through the host header. It all worked before so
I
> > know it is not a configuration issue.
> >
> > You can see the reports folder by entering
http://xxx.xxxxx.xxx/reportserver
> > and then navigating to a report. Also, the scheduled report tasks run
ok.
> >
> > Here is a copy of the error from the log:
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.878.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>GMT Daylight Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
> > <SystemName>SWIPER</SystemName>
> > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > <OSVersion>5.2.3790.0</OSVersion>
> > </Header>
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
MaxScheduleWait
> > to default value of '1' second(s) because it was not specified in
> > Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > DatabaseQueryTimeout to default value of '30' second(s) because it was
not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
InstanceName to
> > default value of 'MSSQLSERVER.1' because it was not specified in
> > Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > ProcessRecycleOptions to default value of '0' because it was not
specified
> > in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > RunningRequestsScavengerCycle to default value of '30' second(s) because
it
> > was not specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > RunningRequestsDbCycle to default value of '30' second(s) because it was
not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > RunningRequestsAge to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > CleanupCycleMinutes to default value of '10' minute(s) because it was
not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > SecureConnectionLevel to default value of '1' because it was not
specified
> > in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > DisplayErrorLink to 'True' as specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > WebServiceUseFileShareStorage to default value of 'False' because it
was not
> > specified in Configuration file.
> > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
> > status 401: Unauthorized.
> > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The request failed with HTTP status 401:
> > Unauthorized.
> > at
> >
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
Message
> > message, WebResponse response, Stream responseStream, Boolean asyncCall)
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> > at
> >
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at
> > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname)
> > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > 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.Control.InitRecursive(Control namingContainer)
> > at System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!1b70!02/04/2005-09:20:58:: 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)
> >
> > Cheers
> >
> > Glen
> >
> >
> > "geoff" wrote:
> >
> > > It is set to run as Network Service account. The ReportServer service
is in
> > > fact running as Network Service.
> > >
> > > "Brian Welcker [MSFT]" wrote:
> > >
> > > > Sounds like ASP.NET permissions issue. What is the application pool
set to
> > > > run as?
> > > >
> > > > --
> > > > Brian Welcker
> > > > Group Program Manager
> > > > Microsoft SQL Server Reporting Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > > >
> > > > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > > > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > > > Installation of WS2003SP1 broke reporting services SP2Beta. I now
get
> > > > > "The
> > > > > request failed with HTTP status 401: Unauthorized." I've re-set
the
> > > > > database
> > > > > credentials via RSCONFIG. I think it's in IIS, but I can't seem
to find
> > > > > it.
> > > > > Any help would be appreciated.
> > > >
> > > >
> > > >|||Getting the same problem also on one of our test machines.
"ejr" wrote:
> Same here,
> same error, sysadmin is unauthorized to http://localhost/Reports,
> I can browse and see the files...
> any suggestion other than uninstall the SP1?
> Thank you,
> --
> ejr
>
> "geoff" <geoff@.discussions.microsoft.com> wrote in message
> news:97FDD47E-4BCD-4A15-8FD0-B342920FAD78@.microsoft.com...
> > I can browse as you suggest and the scheduled reports do run. I can
> browse
> > the reports folder as you suggest through .../reportserver, but I can do
> so
> > without using the FQDN as well. I can't get anything to work with
> .../reports
> >
> > I have my SQL Report Server database on another box...don't know if this
> is
> > impacting anything.
> >
> > Hopefully MSFT will help us out on this one.
> >
> > "GlenConway" wrote:
> >
> > > Hi,
> > >
> > > I get the same thing running SQL Server Reporting Services SP 1 on
> Server
> > > 2003 Enterprise Edition with SP 1.
> > >
> > > The location of SQLRS is non-standard in that the site running SQLRS
> will
> > > only respond to a FQDN through the host header. It all worked before so
> I
> > > know it is not a configuration issue.
> > >
> > > You can see the reports folder by entering
> http://xxx.xxxxx.xxx/reportserver
> > > and then navigating to a report. Also, the scheduled report tasks run
> ok.
> > >
> > > Here is a copy of the error from the log:
> > >
> > > <Header>
> > > <Product>Microsoft SQL Server Reporting Services Version
> > > 8.00.878.00</Product>
> > > <Locale>en-US</Locale>
> > > <TimeZone>GMT Daylight Time</TimeZone>
> > > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > > Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
> > > <SystemName>SWIPER</SystemName>
> > > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > > <OSVersion>5.2.3790.0</OSVersion>
> > > </Header>
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
> file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> MaxScheduleWait
> > > to default value of '1' second(s) because it was not specified in
> > > Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > DatabaseQueryTimeout to default value of '30' second(s) because it was
> not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> InstanceName to
> > > default value of 'MSSQLSERVER.1' because it was not specified in
> > > Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > ProcessRecycleOptions to default value of '0' because it was not
> specified
> > > in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > RunningRequestsScavengerCycle to default value of '30' second(s) because
> it
> > > was not specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > RunningRequestsDbCycle to default value of '30' second(s) because it was
> not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > RunningRequestsAge to default value of '30' second(s) because it was not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > CleanupCycleMinutes to default value of '10' minute(s) because it was
> not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > SecureConnectionLevel to default value of '1' because it was not
> specified
> > > in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > DisplayErrorLink to 'True' as specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > WebServiceUseFileShareStorage to default value of 'False' because it
> was not
> > > specified in Configuration file.
> > > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
> > > status 401: Unauthorized.
> > > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
> > > --Details--
> > > System.Net.WebException: The request failed with HTTP status 401:
> > > Unauthorized.
> > > at
> > >
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> Message
> > > message, WebResponse response, Stream responseStream, Boolean asyncCall)
> > > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > > methodName, Object[] parameters)
> > > at
> > >
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > > at
> Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > > at
> Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > > at
> > > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > > methodname)
> > > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > > 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.Control.InitRecursive(Control namingContainer)
> > > at System.Web.UI.Page.ProcessRequestMain()
> > > w3wp!ui!1b70!02/04/2005-09:20:58:: 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)
> > >
> > > Cheers
> > >
> > > Glen
> > >
> > >
> > > "geoff" wrote:
> > >
> > > > It is set to run as Network Service account. The ReportServer service
> is in
> > > > fact running as Network Service.
> > > >
> > > > "Brian Welcker [MSFT]" wrote:
> > > >
> > > > > Sounds like ASP.NET permissions issue. What is the application pool
> set to
> > > > > run as?
> > > > >
> > > > > --
> > > > > Brian Welcker
> > > > > Group Program Manager
> > > > > Microsoft SQL Server Reporting Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > > >
> > > > > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > > > > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > > > > Installation of WS2003SP1 broke reporting services SP2Beta. I now
> get
> > > > > > "The
> > > > > > request failed with HTTP status 401: Unauthorized." I've re-set
> the
> > > > > > database
> > > > > > credentials via RSCONFIG. I think it's in IIS, but I can't seem
> to find
> > > > > > it.
> > > > > > Any help would be appreciated.
> > > > >
> > > > >
> > > > >
>
>|||Hi Guys,
Microsoft resolved this problem for us. We created a DWORD entry called
DisableLoopbackCheck to HKLM\System\CurrentControlSet\Control\Lsa. Setting
this key to a value of 1 fixed our issue.
For more information, see:
http://flarepath.blogspot.com/2005/04/2003-service-pack-1-and-sql-server.html
Thanks
Glen
"geoff" wrote:
> Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
> request failed with HTTP status 401: Unauthorized." I've re-set the database
> credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
> Any help would be appreciated.|||Did the suggestion from GlenConway work for you? If not, I have another
solution that may work for you.
"geoff" wrote:
> Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
> request failed with HTTP status 401: Unauthorized." I've re-set the database
> credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
> Any help would be appreciated.|||adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
Any other suggestions?|||Thanks for the link Glen, this resolve my problem.
"GlenConway" wrote:
> Hi Guys,
> Microsoft resolved this problem for us. We created a DWORD entry called
> DisableLoopbackCheck to HKLM\System\CurrentControlSet\Control\Lsa. Setting
> this key to a value of 1 fixed our issue.
> For more information, see:
> http://flarepath.blogspot.com/2005/04/2003-service-pack-1-and-sql-server.html
> Thanks
> Glen
> "geoff" wrote:
> > Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
> > request failed with HTTP status 401: Unauthorized." I've re-set the database
> > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
> > Any help would be appreciated.|||I'm also looking for other option/suggestion.
The Report Manager works fine for adding role/user to reports/folders, but
the same operation in RS API has the 401 error. Other OS works fine too just
this 2003 SP1 machine.
Thanks,
Lianghong
"Khubieb" wrote:
> adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> Any other suggestions?|||Me too! We are able to access everything through
http://ServerName/reportserver but cannot get thru to
http://ServerName/reports. Keeps giving us the "401: Unauthorized" error.
Even after applying the Registry change AND rebooting the server, we are
still down. This is a production server with 100s of users - phone ringing
off the hook...any ideas?
Note that we have found some users are able to access the Reports Manager
while others are not... not sure why. We are continuing to work with IIS
security but nothing has been changed recently.
"Lianghong" wrote:
> I'm also looking for other option/suggestion.
> The Report Manager works fine for adding role/user to reports/folders, but
> the same operation in RS API has the 401 error. Other OS works fine too just
> this 2003 SP1 machine.
> Thanks,
> Lianghong
> "Khubieb" wrote:
> > adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> > Any other suggestions?|||What finally fixed this for us was going into IIS and for the 'ReportServer'
folder, we removed all permissions and then added them all back. After doing
this, the Reports Manager worked again for everyone.
We didn't change anything or give any new permissions, just removed and
re-added the permissions that were already there.
We are very concerned this will happen again in the future as we had done
nothing to that server in several days and this happenned apparently
unprovoked. It appears to be an IIS security issue - not a Reporting Services
issue.
"MoranTugTom" wrote:
> Me too! We are able to access everything through
> http://ServerName/reportserver but cannot get thru to
> http://ServerName/reports. Keeps giving us the "401: Unauthorized" error.
> Even after applying the Registry change AND rebooting the server, we are
> still down. This is a production server with 100s of users - phone ringing
> off the hook...any ideas?
> Note that we have found some users are able to access the Reports Manager
> while others are not... not sure why. We are continuing to work with IIS
> security but nothing has been changed recently.
> "Lianghong" wrote:
> > I'm also looking for other option/suggestion.
> > The Report Manager works fine for adding role/user to reports/folders, but
> > the same operation in RS API has the 401 error. Other OS works fine too just
> > this 2003 SP1 machine.
> >
> > Thanks,
> > Lianghong
> >
> > "Khubieb" wrote:
> >
> > > adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> > > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> > > Any other suggestions?|||I tried this as well with no avail. Still get 'cannot connect to data source'
when running report (with my user logged in). If I use windows it flys with
the same account. just doesn't make any sense.
"MoranTugTom" wrote:
> What finally fixed this for us was going into IIS and for the 'ReportServer'
> folder, we removed all permissions and then added them all back. After doing
> this, the Reports Manager worked again for everyone.
> We didn't change anything or give any new permissions, just removed and
> re-added the permissions that were already there.
> We are very concerned this will happen again in the future as we had done
> nothing to that server in several days and this happenned apparently
> unprovoked. It appears to be an IIS security issue - not a Reporting Services
> issue.
>
> "MoranTugTom" wrote:
> > Me too! We are able to access everything through
> > http://ServerName/reportserver but cannot get thru to
> > http://ServerName/reports. Keeps giving us the "401: Unauthorized" error.
> > Even after applying the Registry change AND rebooting the server, we are
> > still down. This is a production server with 100s of users - phone ringing
> > off the hook...any ideas?
> >
> > Note that we have found some users are able to access the Reports Manager
> > while others are not... not sure why. We are continuing to work with IIS
> > security but nothing has been changed recently.
> >
> > "Lianghong" wrote:
> >
> > > I'm also looking for other option/suggestion.
> > > The Report Manager works fine for adding role/user to reports/folders, but
> > > the same operation in RS API has the 401 error. Other OS works fine too just
> > > this 2003 SP1 machine.
> > >
> > > Thanks,
> > > Lianghong
> > >
> > > "Khubieb" wrote:
> > >
> > > > adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> > > > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> > > > Any other suggestions?