SSRS 2005 post installation problems

From your SQL Server version number (9.0.1399) I can tell that you haven't installed any Service Packs.  I recommend to install SP2.  It's available here:http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&displaylang=en

It fixes several issues with SSRS, could be that your problems are due to this.

Hope this helps.

Valentino, could you elaborate a bit, pls.  I downloaded the SP2 for x64, can I just install it or I need to backup all databases first? I do not plan to go back to pre-SP2 SQL Server...

Do I need to uninstall SSRS before applying SP2?

Thanks

Backing up your databases before applying a patch or SP is always my preferred approach.  The installation will do a rollback in case anything goes wrong, but it doesn't hurt to have a backup yourself, right?

There's no need to uninstall anything. SSRS is part of SQL Server so if you install SP2, SSRS will get upgraded as well.

I also recommend to read through the information on the download page, including the Readme (http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm).

I installed SP2, version is now correct (3042).

However, SSRS still does not work. I checked Configuration and now Web Service Identity is not setup. Help says to create Virtual Directory first, but it IS created, checked and kind of working (when Authentication set to Basic)...

see screen shot at http://clip2net.com/page/m0/395532

I restarted SQL Server and IIS,  registered ASP - does not help.

Another problem which I failed to mention before (or did not notice then) is that I do not see DataSources when I setup reports on the server. I do see them when I browse folders on server, but when I try to setup a datasource for a report I see the tree with nodes but not a single datasource (and I uploaded two)...

any ideas what to do or what tests to run?

I was thinking to reinstall SSRS but did not see how to uninstall it...

thanks

If I run a report

Does the ASPNET user exist on your server?  I haven't seen this issue myself but have been searching the web a bit and in many cases it seems to have something to do with ASP.NET, either the account or some other issue.

If that's not the problem then the explanation through the following link may have a solution for you: http://developmentnow.com/g/115_2007_8_0_0_1008242/Web-Service-Identiy-is-red-in-report-configuration-tool.htm

Finally got to test the problem and so far no luck.

Yes, user ASPNET exists and has permissions to both Virt Dirs. I went through that exercise with recreating both Virt Dirs and now I have all buttons checked in SSRS Configurator, including Web Identity. Still I am getting Login Failed error on local machine and have to lower Autherntication to from Windows Identity to Basic to be able to access the Reports folder from another computer on the network...

Please, more ideas...

Thanks
Below is fresh snapshot from SSRS log...

w3wp!library!7!11/05/2008-23:58:48:: i INFO: Call to RenderFirst( '/test/Report2' )
w3wp!library!7!11/05/2008-23:58:48:: 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!7!11/05/2008-23:58:48:: 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, Boolean isLinkedReport, 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.RenderPageContent()
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
w3wp!library!7!11/05/2008-23:58:52:: i INFO: Call to RenderFirst( '/test/Report2' )
w3wp!library!7!11/05/2008-23:58:52:: 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!7!11/05/2008-23:58:52:: 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 ---

First question...are you using ACTIVE DIRECTORY to administrate your userID's a nd Passwords...???

I would recommend creating GROUPS for logins,..then you can simply ADD the User's to their designated groups.

....? >>>>>????

to CRXIuser2005:
No, I am not using AD, should I? Is it a must? Can I create groups using Server Users Management tool?

If YES, could you please elaborate? You suggest to create group, say, ReportUsers and permit it to do what? who should be mebers of that group? ASPNET? Real people who run reports?

thank you

Well, the asker (me) is still interested bu tif  there are indeed no experts available then we have to close it...

I don't know what you mean by Server Users Management Tool.

But the Windows Active Directory works fine. I would recommend using AD.

I've been crazy busy..so ....I'll have to research a little and get back with you...from what I remember it took a while to understand HOW it works..but once you see the concept...its no problem...

M

Server Users Management Tool is Server component where I create users and assign them to groups. If needed I can provide few screen shots...

looking forward to see your instructions how to do AD... Although I was under impression that it is not needed, to use AD. If ASPNET has enough permissions on the server and remote user has access to IIS to run ASP.NET applications (which SSRS is) - is that not enough?? Can it be that SSRS internal roles and permissions need some configuration?

thanks
Naum