IT Analytics Solution stops working and won't properly configure when NS 6.0.6074 SP3 R7 or higher is installed

Article:TECH39077  |  Created: 2008-02-07  |  Updated: 2009-04-08  |  Article URL http://www.symantec.com/docs/TECH39077
Article Type
Technical Solution


Issue



IT Analytics Solution stops working and won't properly configure when installed on NS 6.0.6074 SP3.

Environment



This issue is isolated to the following environment:
  • The instance of SQL Server 2005 Reporting Services used by Altiris IT Analytics Solution is on the same host and website as the Notification Server 6.0 (running R7 or higher)

Cause



In this instance, the application of R7 or higher will force the Website that houses the virtual directories for Notification Server to operate under .NET 1.1. This means that any other virual directory hosted under the same website in IIS will be forced to use .NET 1.1 regardless of whether or not those virtual directories have been set to use .NET 2.0. Since Reporting Services require .NET 2.0, this will cause Reporting Services to not function properly.

The new website port must be set to a port number not being used by another process. 

Port 80 is typically used by Notification Server.

Port 8080 is tyically used by Deployment Console

Port 8081 is typically used by Deployment Web Console.


Solution



In environments where the Notification Server and SQL Server 2005 Reporting Services are installed on the same host, the resolution is to utilize a separate IIS website and Application Pool. It is recommended to use the Default Web Site and the DefaultAppPool for Notification Server and create a new Website and Application Pool named ReportingServices to use with the two Virtual Directories required by SQL Server 2005 Reporting Services. When a separate Website and Application Pools are used, the Notification Server will use .NET 1.1 and Reporting Services will use .NET 2.0 and each will be able to function properly. Follow the instructions below to fix this issue:
  1. Create a new folder in the c:\inetpub directory to use as the base folder for the new website. Be sure to name this folder something descriptive such as ReportingServices.
  2. Launch IIS on the server hosting NS and SQL Reporting Services.
  3. In IIS Expand the Servername node.
  4. Right click on the Web Sites node and select New>Web Site.
  5. Click next on the Web Site Creation Wizard screen.
  6. In the Description box type the name for this new web site and click next. Be sure to use something descriptive such as ReportingServices.
  7. Follow the instructions below to set the appropriate IP Address and Port Settings:
    1. In the IP Addresses dropdown list the default is generally (All Unassigned), however you can specify that this website be confined to a particular IP Address. Only change this if you know it is the appropriate setting, otherwise leave (All Unassigned) selected.
    2. For the TCP port be sure to use something that is not currently in use by another web site under IIS. You can check this by bringing up the properties window for each of the other web sites under the Web Site folder. In most cases the Default Web Site will be configured to use port 80. If that is the only web site that is currently listed than using port 8080 is a common practice.

      IMPORTANT: Make sure you choose a port that is not being used by another process. 

      Port 80 (the Default Web Site)is used by Notification Server by default.
      Port 8080 is used by the Deployment Console by default.
      Port 8081 is used by the Deployment Web Console by default.

      See which ports are being used by opening a Command window and entering:
       netstat -an 

      Identify and use a TCP  0.0.0.0: port that is not in the list.  Just use the port number, not the 0.0.0.0 ip address.
    3. Leave the Host Header box blank.
    4. Click the Next button.
  8. In the path textbox browse to the new folder that you created in step 1. Leave Allow anonymous access to this Web site checked and click next.
  9. Check the following:
    1. Read
    2. Run scripts
    3. Execute
  10. Click Finish.
  11. Launch SQL Reporting Services from Start>All Programs>Microsoft SQL Server 2005>Configuration Tools>Reporting Services Configuration
  12. Connect to the Local instance.
  13. Select the Report Server Virtual Directory item in the left frame.
  14. Click the New button and select the website that you just created. Leave the Virtual Directory as the default and click OK.
  15. Select the Report Manager Virtual Directory item in the left frame.
  16. Click the New button and select the website that you just created. Leave the Virtual Directory as the default and click OK.
  17. Click the Web Service Identity item in the left frame.
  18. Make sure that the Report Server and Report Manager dropdown lists are using an application pool that is different than the one being used for Notification Server. If you are unsure you can create new application pool from this window and use that application pool for both dropdown lists.
  19. Click Apply.
  20. Select the Database Setup item from the left frame.
  21. Ensure that the Notification Server's name appears in the Server Name box (it should be default), and then click on the Connect button.
  22. Click on the New button to create a new database. Leave the default values, and enter "ReportServer" for the Database Name. Click on the OK button to continue.
  23. You may need to change the Credentials Type. Use the same type for the other credential types already previously entered, such as Windows Credential, and then the Account Name and Password.
  24. Click the Apply button if it is enabled. This should place a green check box in the left frame for Database Setup. If not, then most likely the credential type is incorrect; try using a different type.
  25. Once the Database Setup is finished, the following items on the left frame should all have a green check box (there may be additional ones completed as well): Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity, Initialization. If any are not checked, ensure that the setting here are used, and double check the credentials for any that you have provided.
  26. Launch the Altiris Console.
  27. Navigate to Configuration > Solution Settings > IT Analytics > Connection Settings.
  28. Update the Analysis Server Name by clicking on the Verify button. This should set it to be the Notification Server's name.
  29. Update the Analysis Server Database by creating "IT Analytics".
  30. Next, under the Reporting Server, section click the edit icon (pencil) next to the Report Server Virtual Directory URL setting. Change this to add the new port number that will be used, for example: http://ns-server-name:8080/ReportServer/.
  31. Click the edit icon (pencil) next to the Report Folder Name setting.
  32. Leave the default of IT Analytics and click Save Folder Settings.
  33. Click the Report Setup task in the Left Tree of the Notification Server.
  34. Select the Available Reports tab and check any and all reports you’d like to install. To install all available reports click the Install checkbox in the Header row of the table.
  35. Click Apply. This will launch a progress window. Once the Close button is enabled click it.
  36. If either the Analysis Server or Report Server data is added incorrectly or fails to validate, errors will occur at the top of the window.  Correct these before continuing.
  37. Navigate to the IT Analytics tab and validate that you can access the dashboards and reports. If none are set up, go to Cube Setup and Report Setup to first configure these for use.

Legacy ID



40366


Article URL http://www.symantec.com/docs/TECH39077


Terms of use for this information are found in Legal Notices