Setup cannot access Reporting Server

Setup cannot access Reporting Server

• Ness22

  I'm replying to this, since I had a similar error and found a solution (whether it solves this individual's error, I don't know).

  I went into the setup log and pulled out the entire command and ran it from a dos prompt. It failed with the same error, but it also mentioned a 404 error.

  It was trying to hit the reporting server and was using the machine name, but my machine had multiple IP addresses, and the one that hosted the report server was not the same as the one the machine name resolved to.

  So, I changed the IP address of the report server in IIS to match the machine name IP (stopping for a moment the other web site), and setup finished successfully.

  jdn

  
  

• masoftheund

  I think I narrowed the problem down. The command that the installer tries to execute that fails starts out like this:

  <TFS install dir>\Tools\createds.exe /setup /install http://<machinename>/ReportServer/ReportService.asmx ...

  If I try to connect to http://<machinename>/ReportServer from a browser window on my machine it asks for credentials. If I enter them (my current logon information) then it takes me to the webpage.

  However, if I go to http://localhost/ReportServer it works fine without asking for credentials. I think that's where the problem occurs...TFS tries to connect using the machine name and for some reason in that scenario it wants credentials which TFS doesn't supply, thus causing the command to timeout and fail.

  Running the exact same command from the DOS prompt, but switching that one part to localhost makes it run just fine.I did this in the command prompt and then hit retry and the installation completed successfully (leaving me to wonder if this will cause problems down the road).

  So now the real question is why am I getting asked for credentials when I try to connect to the reports page with the machine name in the path Is this some setting in IIS or somewhere else that I need to set, so that it doesn't ask me

  Thanks.

  /s2

  
  

• Ben Chess

  Yes, i am using the RC of TFS, but i did a single-installation. Only option i chose referring to dual-installation was installting sharepoint services 2.0 for server farm, because i read this is better for TFS-Installation.
  
  
  So, any further ideas
  
  

• Robert Cotran

  Check out the warehouse trouble-shooting guide

  http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=154526&SiteID=1

  
  
  

• sunbar07

  I don't remember exactly which log it is, but you'll want to look in the usual places (c:\windows\, c:\windows\system32, and your profile's temp directory...I believe it is in the temp directory) and find the log that has a timestamp that matches the failure time. Inside that log you should find the exact error message and the command that caused it.

  In IIS manager, the easiest thing to do is stop all web sites running on port 80 except the one that has the report server, which should be the default web site. It will have a virtual directory called /ReportServer. You may need to set the IP address for that site to the IP address that is reported when you ping your machine name from a DOS prompt (instead of the default *All unassigned*).

  jdn

  
  

• Gerard van de Ven

  jdn -

  I am having a similar problem. Could you tell me where to look in IIS for the IP address of the report server

  Also - which log file contained the setup command you used in the DOS prompt I have found one in each:

  Setup Log Parameters: /launcher="C:\DOCUME~1\TFSSet~1\LOCALS~1\Temp\"
  MSI Log: e:\atdt\vs_setup.msi

  Thanks

  
  

• palestine

  Unfortunately that did not resolve my problem.
  
  I still get the error:
  
  Error 28804.Setup cannot connect to the SQL Server 2005 Reporting Services report server. Verify that SQL Server 2005 Reporting Services report server is installed and running, and that you have sufficient privileges to access it. Fore more information, see setup logs.
  
  
  
  

• William Fontinele Franca

  1) home page is displayed
  
  2) all items are checked, including the ones you excepted!
  
  
  
  
  

• levous

  I don't know if this will help or not:
  If this is a dual-server install, and you're using the RC version of TFS, the SQL Reporting Services get installed on the Application tier, not the Data tier.
  
  

• Funchip

  Here are some more details about my setup experience:

  I have successfully installed Team Foundation on a computer in Workgroup mode. Server appears to run as intended.

  When I try to install Team Foundation on a computer that is part of the domain it fails when nearly complete. The failure error message is:

  Error 28806.An unexpected error has occurred. Verify that SQL Server 2005 Reporting Services report server is installed and running, and that you have sufficient privileges to access it. For more information, see the setup logs.

  I have attempted the install using DHCP on the server and also with a fixed IP address. When I try to navigate to http://localhost/reports, I get prompted with a login box to "Connect to 127.0.0.1"

  If I login to the prompt using the TFSSetup account I get an ASP.NET exception page stating: The event source "Report Manager" does not exist.

  This error is also one of the errors that appears in the MSI setup log. Strangely the event source does actually exist on the server.

  I have no idea whether this has to do with limited rights defined in the GPO of the domain or relates to the IP address fix that jdn spoke of. I have tried the installation on a clean system many times to no avail. Each time has been successful in workgroup mode, however.

  
  

• BobHSC

  On a single server install, report server is configured by SQL, not by TFS install. Before you install TFS, you can try the following to ensure that the report server is installed properly and running.

  1) run http://localhost/reports, you get "SQL server reporting services" home page displayed,

  2) go to Start\Programs\Microsoft SQL Server 2005\Configuration tools\Reporting Services Configuration. After you connect to your machine, you should see in the left pane all the items are checked except Email settings, Execution Accout and Encryption Keys.

  Bo

  
  

• LeeFbx

  I am having the same problem as the original poster on a single server install. At the very end of the install I get the 28804 error. Running the command that causes it from the command prompt also yields the following: "The underlying connection was closed: The connection was closed unexpectedly".

  I have used the Report Server Configuration tool and everything appears normal there. I am able to access localhost\reports and localhost\reportserver just fine. I have no clue why this error is occuring and have found absolutely 0 help in trying to get any help with it.

  Any advice would be appreciated.

  
  

• Steve Swasey

  How many IP addresses do you have

  What are the settings in IIS for the site that hosts the virtual directory /reports

  You can try setting the IP address to *All unassigned* and see if that works. It sounds like some other site has the all unassigned and so that's the web site that is responding.

  jdn

  
  

• cipher2079

  The report service account only needs to be a domain account (or local machine account in work group mode). You should not be adding this user to any groups because TFS install will take care of permissions.

  Either create a new account for report service, or remove the permissions associated with this account.

  
  
• Setup cannot access Reporting Server