The following list of symptoms and resolutions was compounded by myself over the past few years during the setup of SSRS 2005 and a VS 2005 web application.
Help yourself if you see a similar problem to your own.
Symptom:
When attempting to browse to a report using IE the following error message is displayed:
“The user ‘MachineName\ASPNET’ does not have sufficient access to perform the requested operation”
Resolution:
Open Internet Information Services from Administrative Tools in Control Panel. Right Click Report Server and select Properties.
Under Anonymous access and authentication control, click the Edit… button.
Check the Anonymous access checkbox. Next, click Browse….
In the “Enter the object name” textbox, enter “Machinename\ASPNET”. Click OK Click OK once again on the window just above. Try to access the report once again.
-------------------------------------------------------
Symptom:
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.20'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)
Resolution:
“This is usually an issue where RS is configured to the wrong DB. You should use the config tool to configure RS to a ReportServer DB.”
“In the ReportServer Configuration tool, does the Database tab have a green check? If not you need to go to that tab and choose the Report Server Database that you want to use.”
-------------------------------------------------------
Symptom:
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"
Resolution:
“1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
2. On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
3. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply.
Note Click OK when you receive the following message:Changes to Connection Settings will not take effect until you restart the Database Engine service.
4. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Service, click Stop, wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service.”
-------------------------------------------------------
Symptom:
“Login failed for user ‘NT Authority\Network Service’”
Resolution:
1. In SQL Server Management Studio go to Security. Expand Logins.
2. Right click NT Authority\Network Service.
3. Change the default database to the database that you are trying to access.
4. In the left pane, click server roles. Check the sys admin server role.
5. Click OK to save the changes.
-------------------------------------------------------
Symptom:
"The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request."
Resolution:
It is possible that the webserver may have more than one IP address.
“I was reading through the IIS logs and app logs and discovered that the web server has two IP addresses. Each IP is statically assigned to other websites hosted by this server and are both using port 80. When you type in [hostname] it is defaulting to the other website and causing the error. I changed the port to 81 on the site for the geneva software and that worked locally and remotely”
For example: http://greg:81/WebApplication/Default.aspx
Refer to the following KB article if this does not solve the issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315158
-------------------------------------------------------
Symptom:
"Cannot Retrieve Application. Authentication Error” when trying to access report manager on a remote machine.
Resolution:
Using IIS, grant anonymous access to the /Reportserver/ReportBuilder directory.
Symptom:
All sorts of strange behavior surrounding timeout issues, i.e. “Execution ‘’ could not be completed”.
Resolution:
http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
Create a file called sessionTimeout.rss and paste the following code in it:
Public Sub Main()
Dim props() as [Property] props = new [Property] () { new [Property](), new [Property]() }
props(0).Name = "SessionTimeout"
props(0).Value = timeout
props(1).Name = "SessionAccessTimeout"
props(1).Value = timeout
rs.SetSystemProperties(props)
End Sub
Run the following command from the directory in which the sessionTimeout.rss file is stored:rs -i sessionTimeout.rss -s http://localhost/reportserver -v timeout="6000"
This example sets the SessionTimeout and SessionAccessTimeouts to about an hour and a half.
-------------------------------------------------------
Symptom:
"Page cannot be found" when browsing aspx pages in Windows Server 2003 with IIS 6.0
Resolution:
1. From your Run command, type inetmgr and press enter.
2. Expand the appropriate nodes in the IIS to locate the "Webservice Extensions" Node
3. Click on the same.
4. You will find a list of "prohibited" extensions in the right.
5. Click on ASP.NET and "allow" it
-------------------------------------------------------
Symptom:
The permissions granted to user 'NT AUTHORITY\NETWORK SERVICE' are insufficient for performing this operation. (rsAccessDenied)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=262746&SiteID=1
Resolution:
Add NT AUTHORITY\NETWORK SERVICE role assignment to security in report manager.
-------------------------------------------------------
Symptom:
The remote server returned an error: (403) Forbidden.
Resolution:
Apply default settings to the report server virtual directory in reporting services configuration manager
Add full access for the Network Service account to 'C:\WINDOWS\Microsoft.NET\Framework\V2.0.050727\Temporary ASP.NET Files'
Go to: 'C:\WINDOWS\Microsoft.NET\Framework\V2.0.050727\Temporary ASP.NET Files'. (or where ever your .NET framework is installed on your machine)Right click on the "Temporary ASP.NET Files" and select properties->secutity.See if the "NETWORK SERVICE" is already part of the "User/Group" section.
If not add it by typing "Network Service".
If it's already there then grant the write permissions.
Assign access to everything under the sun in SQL and in IIS for Reports and ReportServer.
-------------------------------------------------------
Symptom:
The SQL Server 2005 installer says the tools are installed but they in fact are not. When I run SqlRun_Tools.msi and select 'Managment Tools' and/or 'Business Intelligense Development Studio' it gives an message "A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component. (OK)". Press OK and the setup exits.
Resolution:
Try this command from the setup folder of CD2:
start /wait setup.exe /qb INSTANCENAME=MSSQLSERVER UPGRADE=SQL_Tools90
msiexec runs for a while in the background, no errors displayed. Still no management tools...
Rebooted and then the install worked.
0 comments:
Post a Comment