April 27, 2005 at 7:27 am
I've been using RS for about a year now. We've had a shaky, yet satisfying relationship. That relationship is on the rocks now. I wanted to show a fellow coder the Sample Reports I had downloaded a few months ago. Much to my chagrin, I can't open the report manager!
"The request failed with HTTP status 401: Access Denied."
This was on our dev server, which is set up as a webserver and SQL database server.
Does anyone know how to check permission in the various config files?
I was also getting random 'can't connect to database' errors, but I think I fixed them using the rsconfig utility.
This morning I find I can't open Report Manager on the production webserver now. This is getting scary. Fortunately I can get to the reports via URL and my apps are still working.
Any help/ ideas appreciated.
dave
April 27, 2005 at 8:09 am
Additional information:
If I try to connect using http://[servername]/reportserver , I get the message:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help
The reportserver database has the same user it has always had, with RSexec permissions. This all used to work. I can't figure out what has changed!
April 28, 2005 at 2:05 am
The "Cannot initialize SSPI package" usually refers to making a trusted connection via Windows Security. Did accounts, or policies change recently?
If the ReportServer service uses LocalSystem, then you need to add 'NT AUTHORITY\SYSTEM' as a login in SQL Server and grant it access to the ReportServer databases.
--------------------
Colt 45 - the original point and click interface
April 28, 2005 at 5:59 am
Thanks for the reply Phil,
I took care of Post#2, by using rsconfig. I had a typo the first time I used it.
I still can't open the Report Manager page. http://[webserver]/reports
If I use http://[webserver]/ReportServer/, I can do directory browsing and open the reports.
I'm sure if I could edit the right .config file, I could get things squared away. See the first post for deatails.
April 28, 2005 at 6:08 am
What server are you running. I've heard of some issues with Windows Server 2003 after applying SP1.
--------------------
Colt 45 - the original point and click interface
April 28, 2005 at 7:24 am
Problem resolved.
I re-ran SP1 and everything is OK now. Seems like I took the easy way out, but I've got plenty of other things to do and I'm just happy everything is clicking.
Thanks for your input Phil. BTW, I'm running Win2k Advanced Server.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply