SAP Knowledge Base Article - Preview

1667117 - Database access error. Reason loading shared object failed.

Symptom

  • SIA could not be started. The CMS.exe crashes in the task manager.
  • When go to the 'Configuration' tab of SIA properties and specify the CMS database.
  • Click on 'Apply' and the following error message is shown:

    "Database access error. Reason loading shared object failed.
    First tried to load library libsybcs and failed because of error: [The specified module could not be found].
    Second tried to load library libsybcs.dll and failed because of error: [The specified module could not be found]"
  • When enable trace on CCM, following is the output in the SvcMgr file:

    Install_Directory:\titan_sp_rel\src\framework\dbutilities\dbutils_lib\subsysmgrhelper.h:170: TraceLog message 1
    2011/11/29 16:51:03.401|>>|A| | 2112|2272| |||||||||||||||assert failure: (Install_Directory:\titan_sp_rel\src\framework\dbutilities\dbutils_lib\subsysmgrhelper.h:170).
    (false : DBUtils::Subsystem Init: Failed to init subsystem manager. Reason: Error initializing database wrapper environment for DatabaseSubsystem.).


Read more...

Environment

  • Windows 2003 64bits
  • Windows 2008 64bits
  • BusinessObjects Enterprise XI 3.1 (BOE)
  • Sybase ASE version 15.X as CMS database.

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

Database, access error, Failed to load library. , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.