Local Client Crashes/Errors Out During Database Synchronization After Uninstalling The Old Local Client
Last updated on JUNE 01, 2018
Applies to:Siebel CRM - Version 220.127.116.11.9 [IP2014] and later
Information in this document applies to any platform.
On : 18.104.22.168.9 [IP2014] version, Remote / Replication / Anywhere
During database synchronization dbeng9.exe unexpectedly exits and Siebel hangs up.
First synchronization goes well but the second it fails.
Re-extracting the clients does not help.
Machine 1 logs:
Detailed errors from logs:
Filename : Event_Siebel_Application.txt
See the following error:
sslcsc +0x30bb2 = WriteDockDetail() +0x1352
sslcsc +0x2f235 = WriteEventLog() +0x15
sslcdock +0x261ea = CSSDockPtrArray::ElementAt() +0x646a
sslcdb +0x1117d = DbErrorCheck() +0x22d
sslcdb +0x115cd = UTLOdbcDriverConnect() +0xdd
Line 49: DBCLog DBCLogError 1 0000000958471be8:0 2016-12-07 09:14:21 Specified driver could not be loaded due to system error 126: The specified module could not be found. (Siebel Database, C:\Siebel\8.1\Client_1\bin\dbodbc9.dll).
Machine 2 logs:
There is no crash file on this machine.
Trace TracingInfo 3 00000005584a07b0:0 2016-12-09 11:28:19 Initializing ... (connecting to SEAW Local Db default instance as GSMTMETEST)
SecAdptLog API Trace 4 00000005584a07b0:0 2016-12-09 11:28:19 Security DB user connect to DB C:\Siebel\8.1\Client_2\Local\sse_data.dbf -q -m -x TCPIP -gp 4096 -c15p -ch25p -n C__Siebel_8_1_Client_2_Local_sse_data_dbf with username=XXXXXX returns err 0 and connection 1cf9300.
DBCLog DBCLogError 1 00000005584a07b0:0 2016-12-09 11:28:19 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Even so the same steps were applied (installing the new local client followed by uninstalling the old one) the behavior was different on these machines but related.
On the first machine the the datasource was in placed but the driver was referenced from the old client location that was uninstalled and on the second the ODBC datasource has been removed from the OS when the old client was uninstalled and for this reason the new client was invoking an inexistent datasource.
The new Local Client (22.214.171.124) was installed on a machine were the old one (126.96.36.199) was still in place.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms