Skip to end of metadata
Go to start of metadata
  • The "Connection Server" will write logs to connectionserver_<SIA_Name>.ConnectionServer_trace.<number>.glf
  • The "Connection Server 32" will write logs to connectionserver_<SIA_Name>.ConnectionServer32_trace.<number>.glf

 

This page shows the following:

  1. General tips
  2. Search tips
  3. Errors you can safely ignore (they are expected)
  4. Errors you should take note of (they are not typically expected)

For log files found at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging

A 'Connection Server' Configuration file can be found at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer\cs.cfg

 

General tips

When setting the log level to 'Unspecified' the log will generate only Assert errors (|E| and some others with 'Assert' failures). These are generally not useful or helpful as you do not know what happened before it, or the workflow that lead up to that event.

Before deleting logs, stop the 'BI Platform Server Service'. Stopping the service will allow the files to be deleted as they are no longer being held open.

1972293 - Performance Issue - BI 4.1 SP02 - Connection Server trace enabled by default

1586166 - How to enable tracing for BI4.x client applications


 

Search tips

Good search strings:

|E|Failednot found

Errors you can safely ignore (they are expected)

Log entry
Description of why this is safe to ignore

 

 

Errors you should take note of (they are not typically expected)

Log entryDescription of issueAction to resolve

Data source name not found no default driver specified

Missing ODBC definition on the machine (could be the 32 bit name exists, but not the 64 bit name, or the other way around!)Define ODBC connection
   
  • No labels