June 12, 2007 at 9:42 am
I've got a test SQL2005 Reporting Server set up on an XP test machine, and have an interesting issue. The reports all work correctly from a browser on the server.
But all attempts to run the report from any other machine results in:
What do I need to do to allow remote machines to run reports?
Warm Regards,Greg Wilsonsolidrockstable.com
June 12, 2007 at 5:41 pm
You need to use the surface area configuration tool to enable browser service and choose local and remote connection. And you also need to go to Management Studio and change your authentication from Windows to both Windows and SQL Server authentication. This seems like a lot but I have also recently run into reporting services not keeping connection info in the dataset. Hope this helps.
Kind regards,
Gift Peddie
June 13, 2007 at 12:14 pm
I tried all the things that you suggested with no improvement.
One new thing I notice is that the log files record the following on each failed attempt to pull a report from any machine other than the web-server where RS is installed:
Message
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Warm Regards,Greg Wilsonsolidrockstable.com
June 13, 2007 at 12:24 pm
(Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON')
The above means one connection to reporting services login info is dropped, that was the last thing I explained, check all your connection properties you will see the property without login information, I started getting it three days ago. I found mine in the Reports node in solution explorer, it was the last place I expected to look. The error was strange all my configuration was correct, checked and refreshed login in designer, server explorer and then checked solution explorer dataset connection property and the login info was empty, add it and the error it was fixed. Hope this helps.
Kind regards,
Gift Peddie
June 13, 2007 at 1:18 pm
I'm not passing in login information. I'm using integrated windows security. (Which worked fine in RS2K in similar scenarios)
Warm Regards,Greg Wilsonsolidrockstable.com
June 13, 2007 at 1:30 pm
If you are using integrated security that error means Asp.net runtime is not a user in your SQL Server and database. Hope this helps.
Kind regards,
Gift Peddie
June 13, 2007 at 3:31 pm
Why would it use the ASP.NET acount for non-local browser connections, and correct windows identity information on local browser connections? The web site is set to not allow anonymous authentication, and to use integrated authentication.
Warm Regards,Greg Wilsonsolidrockstable.com
June 13, 2007 at 3:39 pm
If you are not using Asp.net then reporting services account maybe local systems account which means it is not a domain account. Removing anonymous user does not remove the need for account to be created in SQL Server and the database. It is the same thing with users I always tell people a Windows Integrated just means you need to add that account into SQL Server on the server level and in the database.
Kind regards,
Gift Peddie
June 13, 2007 at 6:16 pm
You removing anonymous user does not remove the need for Asp.net runtime having permissions in SQL Server and the database, try the thread below for details.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=196449
Kind regards,
Gift Peddie
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply