Skip to end of metadata
Go to start of metadata

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

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

Generic Search tips

General 'generic' search strings: (for specific issues, please see the table "Errors you should take note of (they are not typically expected)" below)

 

Search stringDescription
|E|exception errors
Failed 
not found 
ERROR 
ORA-for Oracle Error messages
ctProcessInfo:VM size (Mb):This shows the amount of memory consumed by the Virtual Machine within Web Intelligence. An example is
2014/12/31 13:59:04.202|==| | |36020|25700| |||||||||||||||ctProcessInfo:VM size (Mb):363
The error message seen by the userThe error message, but not the full message. For example, just search for "30270" if the Error message was
"An internal error occurred while calling xxxxx WIS 30270"

 

Errors you can safely ignore (they are expected)

Log entry
Description of why this is safe to ignore
**ASSERT:ctResourceBundle:Message not found for id: 
**WARNING:ctResourceBundle 
**WARNING:C3_Dataprovider:Allow 
**WARNING:C3_Dataprovider:m_bAllowPercentRank: DataSource NOT loaded, using old value 
**ERROR:C3_DPManager:No DP found :DP stands for 'Data Provider' aka a query.
**ERROR:C3_BlockInstance:GetDefaultDataType:ipValue=0 
**WARNING:C3_cdbQTServer:DS-Server not present 
**ERROR:C3_cdbQTServer:Can't load LOVLOV stands for 'list of values'
**ERROR:C3_DataSourceMANAGER:No DS found [kc3dsmanager.cpp;636]DS stands for 'Data Source'
**ERROR:repeng:ERROR: wrong char in iref [kredsdocument.cpp;2290] 
**ERROR:repeng:ERROR: Wrong IREF value in page range  [kredsdocument.cpp;1336] 
*WARNING:C3_cdbQTServer:Waiting QT for new Allowed infos (AllowMissingRow) (from univers ...)QT stands for 'Query Technique'.
*WARNING:C3_cdbQTServer:HasUserOverload need to'Overload' is the universe overloads, also known as 'Universe Overrides' and 'Universe Restriction Sets'
**WARNING:C3_QTLOVIterator:LOV Not Sharable : is RefreshBeforeUseLOV stands for 'list of values'
**WARNING:C3_DPSerialization:**Load_StaticNode:Empty Domain**DP stands for 'Data Provider' aka a query.
**WARNING:C3_DPSerialization:**Load:Empty Domain**DP stands for 'Data Provider' aka a query.
**WARNING:C3_DPSerialization:**LoadNodeMember:Empty Domain**DP stands for 'Data Provider' aka a query.
**WARNING:dgDocument:Failed to get document size 
**WARNING:dgWICDZAltSwap:Null logon token [kdgWICDZAltSwap.cpp;99] 
**WARNING:DocExpress:There is anybody caching media profiles corresponding !! 
**WARNING:C3_DPSerialization:**Save:Empty Domain** [kc3cdbdpstrunit.cpp;1275]DP stands for 'Data Provider' aka a query.
**WARNING:C3_DPSerialization:**Save:Empty Domain** [kc3cdbdpstrunit.cpp;2544]DP stands for 'Data Provider' aka a query.
**WARNING:CCDZMgr:Update memory info failedCDZ stands for 'Cadenza' Server which is the internal code name for Web Intelligence.
**WARNING:WICDZ_i:ENTITY CREATED BUT NEVER INITALIZED: ENTITY STATE IS CREATED [kdgWICDZ_i.cpp;182]CDZ stands for 'Cadenza' Server which is the internal code name for Web Intelligence.
**WARNING:CCDZMgr:Max entity count reached [cecdzmgr.cpp;470]CDZ stands for 'Cadenza' Server which is the internal code name for Web Intelligence.
Error message :errno=ENOENT 
open o_read 
bo_storage::OpenReadSubPart: throw exception on open 

bo_file::is_dir :

 

bo_file::modify_time :

 
bo_file::chmodW : failed, 
bo_file::filenames( 
bo_file::size 
bo_file::rename() 

Error message :The system cannot find the file specified.

 
getValue called on null property 
in SessionFacade::extractSessionInfo at SessionFacade.cpp:504: get_PreferredViewingLocale failed-2147210707 
**WARNING:C3_ParamServer:Parameter isn't in ParamServer [kc3cdbparamserver.cpp;1614] 
**WARNING:C3_cdbQTServer:Can't find object of : :  [kc3qtds.cpp;7515]QT stands for 'Query Technique'.
**WARNING:C3_cdbQTServer:Can't find object  :  in Dict. [kc3qtds.cpp;7490]QT stands for 'Query Technique'.
**WARNING:C3_cdbQTServer:Can't find object  :  in Dict. [kc3qtds.cpp;7472]QT stands for 'Query Technique'.
**WARNING:C3_Calculator:Cross-branch shortcut detected [kc3cdbCtxt.cpp;1190] 
**WARNING:C3_cdbQTServer:Can't find object of : :  [kc3qtds.cpp;7533]QT stands for 'Query Technique'.
**WARNING:C3_cdbQTServer:Can't find object  :  in Dict. [kc3qtds.cpp;7490]QT stands for 'Query Technique'.
OSCASimpleFactory::isDisabled() 1This means the Web Intelligence server is disabled. If you view the 'server' within the Central Management Console, the server will show as 'disabled'. For Web Intelligence, this means it will still process existing document requests, but new 'connections' (documents) will not be allowed to be opened within it. Instead another Web Intelligence server will need to process new requests (assuming there is one available)
OSCASimpleFactory::isDisabled() 0This means the Web Intelligence server is enabled. If you view the 'server' within the Central Management Console, the server will show as 'enabled'. It generally means it will accept requests to process documents (however the server may be enabled, but still not accept new requests for document actions, if it has entered a state whereby it needs to re-cycle itself. Re-cycling will occur after a number of actions, or if memory limits have been reached)

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

Log entryDescription of issueAction to resolve

2014/12/08 13:39:37.552|>>|E| |36720|11704| |||||||||||||||***ERROR:ctBlobManager:Unsupported protocol : TMP*178*1 [kctblobmanager.cpp;671]

This shows the Web Intelligence server is generating a 'blob' on either an explicit user request (export to PDF for example) or to temporarily render the page. A blob can be anything: a chart, html, csv, pdf, xls etc. These blobs are temporary (their names start with TMP) and they can only be used once. These errors are not expected, as it means the Web Intelligence server needs to re-generate the blob. Something went wrong.   

You'll need to see the 'full' logs to gain an insight into why the same blob is called repeatedly. Its just fine to see the same blob ID (TMP*178*1in this example) across different users/sessions/threads, since the IDs are generated using the same algorithm. The thread ID in this example is 11704 for process ID 36720.

If you see one of these errors, then it suggests a 'server side' error, if you see multiple of these errors within the same Session ID, then it suggests a client side issue (client side could include the 'Web Application Server')

Uncaught Exception in SilentScope: CDZServerFactory::newService

The Web Intelligence server has rejected the connection. A connection in this case is akin to a document being opened (by a user or a scheduled job). The connection has been refused for a number of possible reasons: 1) the maximum number of connections has been reached (a property of the Web Intelligence Server), 2) the server has reached its maximum memory threshold and is rejecting connections to prevent its memory consumption from further increasing.

Increase the number of connections on the Web Intelligence server (in general the number of connections should be set the same across ALL Web Intelligence servers).

(1) Increase the number of Web Intelligence servers within the cluster. Increasing the number will mean load is distributed across more Web Intelligence servers meaning the memory consumption and number of connections on any one individual server will be less.

(2) If using XI3 upgrade to BI4 to change from a 32 bit product to 64 bit. This will enable more memory to be used.

(3) Related links on SCN http://scn.sap.com/thread/3371454 and http://scn.sap.com/community/businessobjects-web-intelligence/blog/2011/04/06/performance-tips-getting-the-most-out-of-your-web-intelligence-processing-servers

**ERROR:C3_dacs:CS::Error (in cancel): (DBD) "ORA-01013: user requested cancel of current operationThe database query was cancelled. This could be the user asking to cancel the query, but it can also be the Web Intelligence server. The Web Intelligence server will cancel the query if the memory consumption is too high.As above marked (1) (2) and (3).
**ERROR:C3_ALLOCATOR:No memory left during allocation class:Web Intelligence has no more memory available.There are many parameters that enable internal algorithms to trigger to then recover memory. The main parameters are "idle document timeout", "idle connection timeout", "maximum documents per user", "maximum binary stream size", "maximum character stream size". The default values for all these, really are great values. Increasing any of them will mean less memory is recovered less often. If you get memory issues you are best to keep to the default values, but increase the number of Web Intelligence Processing Servers overall in the cluster. This will mean each server has less load and less memory consumption. Also inspect your audit database for large documents (so they can be redesigned) or user activity that is inappropriately putting too much load on the system.
  • No labels