52458

Error 503 Service Unavailable when launching Weblink or Vision

Error occurs when launching Weblink or Vision:

503:  Service Unavailable

This happens regardless of which machine it is launched from, or which user is logged in. 

Cause: 

The error occurs because the Application Pool is not running, or because a SQL service is stopped. This can happen if the service account running the service has an invalid password or inadequate rights.

Resolution:

1. On the Web server for Vision: 
   • Launch Administrative Tools > Internet Information Service Manager. 
   • Navigate to the Application Pools.   
   • Determine the account that is running the DeltekVisionAppPool. This is the service account for Vision.  
     Note: If there are various tiers of Vision installed on multiple servers (SQL Server, Report Server, Process Server, Print server) this account will need to be a Domain account accessible on all of the servers. If all Vision tiers are on the same server, the service account can be a local account. In either case, Deltek recommends that this service account should have a strong, complex, static password.
2. On the Web server, under Tools > Computer Management > Local Users and Groups, verify that the service account exists.  
   This account must be a Member of the following groups:
   •     Administrators
   •     IIS_IUSRS
3. On the Web server, under Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment, make sure that the account has the following rights:
   •     Log on as batch job
   •     Log on as a service
4. If any changes were made above, restart IIS. Make sure that the DeltekVisionAppPool stays running.
5. On the server where the DeltekProcessServer service is installed, (which is typically the Web Server), open Services. 
   Make sure that the service is running using the same service account.  
6. On the SQL Server where the Vision database resides, open the SQL Server Management Studio and connect to the appropriate instance for Vision.
   Under Security > Logins, make sure that this account exists and has the Server Role of sysadmin. 
7. On this server, under Services, make sure that the SQL instance is running.
8. On the server where SQL Reporting Service is installed, under Services, make sure that the SQL Reporting Service is running. 
   (It may be using the same service account, or it may be using the Network Service or Local System account.)
9. Browse to the SQL Report Service page, in the format http(s)://ServerName(_InstanceName)/Reports.  
   If that page does not open, there may be an issue with the SQL Report Server bindings, with DNS name resolution, or with the port being used for SQL Server Reporting Service. Further troubleshooting may be required.
10. When the SQL Report Server page opens successfully, click on Folder Settings > New Role Assignment.  
    If the service account is not listed, add it here.  
    • Select Content Manager, and apply.
11. Click on Site Settings > Security > New Role Assignment.  
    If the service account is not listed, add it here.  
    • Select System Administrator and apply.
12. If any changes were made, restart the SQL services. Make sure that they stay running.
13. On the Web server, open Weblink and log in.
14. On the General page, select the appropriate Vision database.  
    • Select the Report Server tab.   
      • Make sure that the Report Server is specified correctly.  
      • Make sure that the service account and password are specified correctly.  
      • Test the Report Server configuration.   
      • If successful, save.   
      • Repeat these steps for any additional Vision databases.
15. Log into Vision to test.  

If the problem persists, contact Vision Customer Care for further troubleshooting.