Troubleshoot PerformancePoint Planning Server

Updated: 2009-04-09

The following procedures list information that you can use to resolve problems with Planning Server and its associated components. The procedures are not listed in chronological order and you can perform them as required.

The following list describes general troubleshooting:

• During setup, the Planning Server Configuration Manager might not return all existing Windows SharePoint Services Web sites. Only SharePoint site collections show in the Planning Server Configuration Manager. This is expected behavior.

• Always use a domain user account for the SQL Server service account when installing Microsoft SQL Server for use with Planning Server. If you use a local account, the Planning Process service fails after setup.

• If you use a file share to store forms and reports for Planning Server, you must ensure that proper access permissions are enabled for the file system folder and the entire file share.

• After PerformancePoint server Service Pack 1 has upgraded the PerformancePoint Server binary files, the system, service, and application databases must be upgraded before the PerformancePoint Server services are re-enabled. If the PerformancePoint Planning server asynchronous service is started before all application databases have been upgraded an error will be displayed in the system event log. This is expected behavior.

SQL Server stopped while PerformancePoint Planning Server is initializing If you log on to the Administration Console and then click Connect you may receive the following error message:

There was a failure connecting to server {Error Code: PerformancePoint_100000000} Unhandled exception. Look in the server log or contact your system administrator for more information.

If this occurs, the cause may be that the SQL Server is unavailable. You need to reset the PPS Planning Web Server when the database connection is restored.

Download this book