Planning Server log files
Updated: 2009-04-09
Planning Server generates two types of log files. The installation log files are created when Planning Server software is installed. Once installed, Planning Server produces the trace and audit log files.
Installation log files
Planning Server creates the following two installation log files in the %temp% directory:
PlanningStatus%date%.log
PlanningVerbose%date%.log
Server trace log files
After installation is finished, based on the Planning Server configuration setting, Planning Server creates one or more server log file. The log files are created in the following directory:
<drive>:\Microsoft Office PerformancePoint Server\3.0\Trace Log
As per default configurations, Planning Server retains the 10 most recent log files prior to overwriting them. The sequence of these files is based on a sequence number embedded in the file name with Server.Log.<SequenceNumber>.
See the Planning Administration Console Help file for information on changing the default settings for trace log files.
Audit log files
Planning Server tracks all the changes made within the system in the audit log files: The audit log file is created in the following directory:
<drive>:\Microsoft Office PerformancePoint Server\3.0\Audit Log
The audit log file tracks all metadata and data change events within Planning Server.
Note
The actual metadata and data changes are not logged in the Audit logs due to security concerns.
Windows event logs
The Windows operating system automatically generates Event Log entries for the Planning Web Service start and stop operation using the event source "PPSPlanningService".
In addition to the system-generated Event Log entries, Planning Server creates one or more Windows Event Log entries for each business and system and process during the operation of the server using the event source "PerformancePoint".
All PerformancePoint Event Log entries are generated in the Application event logs. Planning Server records three types of events for the server: Information, Warning, and Error.
Information: Records any internal Planning Server configuration changes.
Warning: Records any internal component errors or failures associated with system or business processes. These issues can be resolved by a PerformancePoint Server administrator.
Errors: Records any invalid access to the Planning Server components and connectivity issues that prevent Planning Server from being operational. These issues can be resolved by a System administrator.
Note
In version 1, security events are considered Application events.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for PerformancePoint Monitoring Server.