

ALL: Besides the error exceptions, all information messages (including SEND and RETRIEVE events) are caught in the table. In the LoggingFlag window the following check-box are available : In BPC 10 MS, in order to get more verbose information and/or MDX and SQL queries directly stored in the table you can turn on the log switch via the BPC Server Manager:Ĭlick Set Logging Flag available when clicking the drop-down button Options : BPC exceptions in tblLogs SQL tableīy default, only the BPC exception errors are written into the SQL table tblLogs of the database AppServer. Note: When enabled, the traces are active for all the Environments (Application-sets). The tracing logs can be enabled to all users, a group of users or to a specific user. Note: In BPC 10, the logging levels Info and Warning have been removed Error - only error activities are written to the trace log.

Warning - warning and error activities are written to the trace log.Info - information, warning, and error activities are written to the trace log.Path (in the Microsoft version) - path, info, warning, and error activities are written to the trace log.Debug - all activities are written to the trace log.These can be used for troubleshooting or monitoring purposes. When enabled, these logs are located in the sub-directory T ra ce. Note: In BPC 10, the logging levels have been narrowed down to Error (and None). Fatal - only fatal messages are added to the log.Error - error and fatal messages are added to the log.Warning - warning, error, and fatal messages are added to the log.Info - all information, warning, error, and fatal messages are added to the log.In the 7.5 version here are the possible logging levels:

These logs will track the events on the back-end perspective. If enabled, the message log-files are located within the sub-directory Log. The management of these logs is done via the BPC Administration Client in the "Manage Logging" task: The system can capture various categories of message logging and activity tracing for specified BPC users of for all users. BPC Server traces BPC message loggingīy default, the log files are stored in /PC_MS/Logging/ located on the BPC server ( "drive" is where the BPC binary files are installed on). Overviewĭepending on the kind of problem to investigate, the BPC modules involved or the symptoms resulting of the issue, BPC built-in logs can be really useful to figure out the root cause of the problem.īesides, there are in BPC some default logs whose partterns can be manually modified to make them more verboses. The aim of this WIKI page is to centralize in one place the different logs that can be enabled to help the troubleshooting BPC for Microsoft.
