SAP Knowledge Base Article - Preview

1254141 - (FALSE : DB connect string not found in registry nor command line) Error message when attempting to start CMS

Symptom

CMS does not start and the CMS logs gives the following error:

Timestamp        ProcessID         ThreadID           Message[Mon Sep 22 11:10:46 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1332). (FALSE : DB connect string not found in registry nor command line).[Mon Sep 22 11:10:47 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1332). (FALSE : DB connect string not found in registry nor command line).[Mon Sep 22 11:10:47 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1071). (GetAuditConnectString(SrcCS) : no message).[Mon Sep 22 11:10:47 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1363). (FALSE : DB driver not found in registry nor command line).[Mon Sep 22 11:10:47 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1072). (GetAuditDBDriver(szSrcDbDriver) : no message).[Mon Sep 22 11:10:47 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1332). (FALSE : DB connect string not found in registry nor command line).[Mon Sep 22 11:10:56 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1332). (FALSE : DB connect string not found in registry nor command line).[Mon Sep 22 11:10:57 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1332). (FALSE : DB connect string not found in registry nor command line).[Mon Sep 22 11:10:57 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1071). (GetAuditConnectString(SrcCS) : no message).[Mon Sep 22 11:10:57 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1363). (FALSE : DB driver not found in registry nor command line).

[Mon Sep 22 11:10:57 2008]      1740     1084     assert failure: (.\ServerInfo.cpp:1072). (GetAuditDBDriver(szSrcDbDriver) : no message).

The Event Viewer gives this error:

The root server reported an error Initialization Failure. (Reason: The database subsystem could not be loaded. Make sure that the database client is installed. The message returned was The library named
OracleDatabaseSubSystem could not be loaded. The system error message is Loading shared object failed. First tried to load library OracleDatabaseSubSystem and failed because of error: [The specified
module could not be found. ].

Second tried to load library OracleDatabaseSubSystem.dll and failed because of error: [The operation completed successfully ].

 


Read more...

Product

SAP BusinessObjects Business Intelligence platform R2

Keywords

OracleDatabaseSubSystem.dllUnable to start CMS , KBA , BI , Business intelligence solutions , 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.