“Specified database file already in use” Error when try to connect local Database

Problem: Specified database file already in use

When you check the log file If you see the error below, that means ODBC Connection setting of Local Database should be changed.

GenericLog    GenericError    1    000000024ccd0e30:0    2010-10-31 14:12:58
08001: [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use

GenericLog    GenericError    1    000000024ccd0e30:0    2010-10-31 14:12:58    (wraprmtcmn.cpp (63) err=1114276 sys=540) SBL-DCK-00164: Error connecting to datasource SEAW Local Db default instance (ERSINERSOY).

GenericLog    GenericError    1    000000024ccd0e30:0    2010-10-31 14:12:58    Error connecting to datasource %1 (%2).
Solution: Set as empty Start line and Server Name properties on Local ODBC Connection

GenericLog        GenericError        1        000000024ccd0e30:0        2010-10-31 14:12:58

08001: [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use

 

GenericLog        GenericError        1        000000024ccd0e30:0        2010-10-31 14:12:58        (wraprmtcmn.cpp (63) err=1114276 sys=540) SBL-DCK-00164: Error connecting to datasource SEAW Local Db default instance (ERSINERSOY).

 

GenericLog        GenericError        1        000000024ccd0e30:0        2010-10-31 14:12:58        Error connecting to datasource %1 (%2).

Database Extract Job Failed with Unable to find node in database(SBL-SMI-00077) Error

Problem: “SBL-SMI-00077″ Database Extract Job Error.

If your database extract job failed with SBL-SMI-00077 error, first you should check the log file because SBL-SMI-00077 Error is a generic error. If you see “Unable to find node in database” error in the log file then you can be sure it is related missing Mobile Web Clients settings.

Solution: Siebel Bookshelf – Remote and Replication Manager Administration Guide > Setting Up Mobile Web Clients > “Registering a Mobile Web Client” steps should be applied.