all groups > sql server reporting services > may 2006 >
You're in the

sql server reporting services

group:

Reports fail to load in the reporting services web UI



Reports fail to load in the reporting services web UI srirzosh NO[at]SPAM googlemail.com
5/2/2006 6:41:57 AM
sql server reporting services: Hi All,

I've been playing around with SRS 2005 enterprise on Windows 2003 SP1
as an pre-cursor to upgrading our existing SRS 2000 solutions.

It's been a remarkable "interesting" procedure so far, with everything
from SQL 2005 failing to install from a network share (finally found
you need the files in a specific folder structure), to integrated
security failing to work with reporting services (a "feature" in 2003
SP1 to do with local loopback security), to the report builder failing
to activate/run (required anonymous access enabled).

Anyways, I've seemingly fixed all of the problems I've had apart from
one rather major one, that is no reports actually work through the web
UI. No reports have ever actually worked on this machine so it's not
been caused by my fiddling (I believe).

I can happily build/preview/deploy reports using the Business
Intelligence Studio (local and remote data sources), but whenever I
load a report that I could happily preview in BIS it fails with:

Logon failed.
Logon failure: unknown user name or bad password. (Exception from
HRESULT: 0x8007052E)

Reports do not work in the report builder either, though a built and
deployed data model lets me browse columns etc (I assume this is a
red-herring as the model contains the destination schema).

I've tried basic and integrated access to the reports manager
application itself. I've tried windows, SQL, integrated access within
the data sources that these reports use, including saved credentials
within SRS. I've changed the identity of the web sites to a domain
account with local admin on both the SRS machine and the destination
database server. I've tried connecting to both SQL 2000 and 2005 data
sources. I've tried the SQL Reporting Server Service as both network
service and local service. I've tried explicitly matching the
collations in the data source to the collation of the destination
server (SQL 2005 defaults to kana sensitive and width sensitive, SQL
2000 didn't).

I've ran some SQL profiles on the local SRS machine while connecting to
a data source pointing at a local database, using my domain
administrator context. I see various SRS internal queries being run to
determine details of the report its executing, and I do see my
credentials logging on to the data source destination (a local DB i
restored to test), after my logon no further SQL statements are run in
my context.

Someone please put me out of my misery and give me a clue what I've
messed up :)
Re: Reports fail to load in the reporting services web UI srirzosh NO[at]SPAM googlemail.com
5/2/2006 7:01:26 AM
This is from the SRS logs by the way, not a lot of new information
here...

w3wp!library!1!05/02/2006-14:19:53:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed. ---> System.Runtime.InteropServices.COMException
(0x8007052E): Logon failure: unknown user name or bad password.
(Exception from HRESULT: 0x8007052E)
at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String
pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName,
String pDomain, String pPassword)
at
Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType
credType, Guid dataSourceId, String userName, String userPwd, String
domain)
--- End of inner exception stack trace ---
w3wp!webserver!1!05/02/2006-14:19:53:: e ERROR: Reporting Services
error Microsoft.ReportingServices.Diagnostics.Utilities.RSException:
Logon failed. --->
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed. ---> System.Runtime.InteropServices.COMException
(0x8007052E): Logon failure: unknown user name or bad password.
(Exception from HRESULT: 0x8007052E)
at
System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String
pRPCEndpointName, Int32 type, Guid dataSourceId, String pUserName,
String pDomain, String pPassword)
at
Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType
credType, Guid dataSourceId, String userName, String userPwd, String
domain)
--- End of inner exception stack trace ---
at
Microsoft.ReportingServices.Diagnostics.ImpersonationContext.Login(CredentialsType
credType, Guid dataSourceId, String userName, String userPwd, String
domain)
at
Microsoft.ReportingServices.Diagnostics.ImpersonationContext..ctor(CredentialsType
credType, Guid dataSourceId, String userName, String password, String
domain)
at
Microsoft.ReportingServices.Library.SurrogateContextFactory.CreateContext(ExecutionType&
execType)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext
reportContext, ItemProperties properties, ParameterInfoCollection
effectiveParameters, Guid reportId, ClientRequest session, String
description, ReportSnapshot intermediateSnapshot,
DataSourceInfoCollection thisReportDataSources, Boolean
cachingRequested, Warning[]& warnings, ReportSnapshot&
resultSnapshotData, DateTime& executionDateTime,
RuntimeDataSourceInfoCollection& alldataSources, UserProfileState&
usedUserProfile)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters)
at
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
--- End of inner exception stack trace ---
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService
rs, CatalogItemContext reportContext, ClientRequest session, JobType
type, Warning[]& warnings, ParameterInfoCollection&
effectiveParameters, String[]& secondaryStreamNames)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(HttpResponseStreamFactory
streamFactory)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.DoStreamedOperation(StreamedOperation
operation)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType
itemType)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent()
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
Re: Reports fail to load in the reporting services web UI jp
5/2/2006 7:15:02 AM
I'm trying to troubleshoot a simlar problem but I don't even know where to
find the SRS logs you are referring to (I checked the security, system, and
application logs as well as the log file on the server).

Please share the location of the log you are getting your error reporting
from.

Thanks you.
--
John Shahan


[quoted text, click to view]
Re: Reports fail to load in the reporting services web UI srirzosh NO[at]SPAM googlemail.com
5/2/2006 7:29:32 AM
<drive>\Program files\Microsoft SQL Server\<InstanceID>\Reporting
Services\LogFiles

HTH
Re: Reports fail to load in the reporting services web UI jp
5/2/2006 7:40:03 AM
Thanks much.

PS: I just resolved my logon failure issue. In case it helps, this is the
deal:
Reports would execute beautifully in VS but would produce a logon failure
when run in SRS.
Following the advice on another post, I disabled the execution account and
the sun came out and the birds are singing again.
(SSRS v 2005 and VS 2003)
--
John Shahan


[quoted text, click to view]
Re: Reports fail to load in the reporting services web UI srirzosh NO[at]SPAM googlemail.com
5/2/2006 8:35:34 AM
BINGO!

Removing the unattended execution account has fixed all of my reports.
The unattended execution account was a low priviledge local account
with no access to SQL server, why it was using this account rather than
my explicit credentials is a matter for contemplation, but who cares
eh?

You're a scholar and a gentleman sir.

Cheers,
AddThis Social Bookmark Button