Most Common Errors User Encounter While working on PPS

While working with the various components of PPS, there are certain scenarios when the user encounters some errors, two such scenarios are mentioned below

SCENARIO 1

• Error message 1
  When you use the PerformancePoint Add-in for Excel to connect to PerformancePoint Server, you receive the following error message:
  The request failed with HTTP status 503: Service Unavailable.
• Error message 2
  When you use Planning Business Modeler to connect to Performance Point Server, you receive the following error message:
  The attempt to connect to the server (http:// ServerName:46787/) failed. Verify that the URL is correct and that the server is available.
• Error message 3
  When you use the Planning Administrator Console to connect to PerformancePoint Server, you receive the following error message: Service Unavailable

Possible Cause of the Errors
These errors are flashed on screen because the password of the specific service identity is expired or is invalid. The specific service identity is the service identity of the application pools that are used by PerformancePoint Server.

To resolve the mentioned errors, follow the below mentioned steps:

1. Click Start, click Run, type Inetmgr, and then click OK.
2. In the Internet Information Services (IIS) Manager dialog box, expand ServerName (local computer), expand Application Pools, right-click PPSPlanningAdminConsoleAppPool, and then click Properties.
3. In the PPSPlanningAdminConsoleAppPool Properties dialog box, click the Identity tab.
4. In the Password box, type the correct password, and then click Apply.Note Use the password for the user whose name appears in the User name box.
5. In the Confirm Password dialog box, type the password again, and then click OK.
6. Click OK to close the PPSPlanningAdminConsoleAppPool Properties dialog box.
7. Repeat steps 2 through 6 for the PPSPlanningWebServicesAppPool application pool.
8. Close the Internet Information Services (IIS) Manager dialog box.
9. Click Start, click Run, type IISReset, and then click OK. This step will restart the IIS and the fresh settings done will be reflected.

SCENARIO 2

Error message in Planning Business Modeler when you connect to a server that is running Planning Server: "You cannot access this server because you do not have the appropriate permissions"

Possible Cause
This problem occurs because the user has not been assigned to one of the following administrative roles:

1. User Administrator
2. Data Administrator
3. Modeler (This role is Mandatory. You need not be the User Administrator or Data Administrator to access the Model from Business Modeler. all the three roles are required for a Stand Alone Installation)

To resolve this problem, add the user to the appropriate administrative role. To do this, follow these steps:

1. Open the PerformancePoint Planning Administration Console and follow below mentioned steps:
   a. Log on to the computer by using a user account that has been assigned the User Administrator role.
   b. Start a Web browser.
   c. In the address bar, type http://Server_Name:46788, and then press ENTER.Note The Server_Name placeholder is a placeholder for the name of the server that is running Planning Server.
2. On the Connection page, type http://Server_Name:46787 , and then click Connect.If you successfully connect to the server that is running Planning Server, you receive the following message in green text:
   Connected to the computer running Planning Server.
3. Add the user who receives the error message that is mentioned in the "Symptoms" section to one of the following administrative roles:

• User Administrator
• Data Administrator
• Modeler

Notes:

1. If you add a user to the User Administrator role for an application, the user has administrative permissions in all the model sites in the application.
2. If you add a user to the User Administrator role for a model site, the user has administrative permissions in the model site only.
3. To open a model site and to use Planning Business Modeler, members of the Global Administrator role must also belong to another administrative role.

Hope this will help you to get going :)