Siebel components not starting on Windows server and ADSI object manager connection problem (Doc ID 1466799.1)

Last updated on JANUARY 03, 2023

Applies to:

Symptoms

The customer was using a Siebel enterprise with two Siebel Servers on the Windows platform.  The first server was co-located with the Siebel Gateway Server.  The second server was on a seperate host.

Two issues were encountered:

(Issue 1)

The Siebel Services were starting, but the components were failing to start properly.  The components were starting and not responding, or failing to start but showing no errors in the log files.

(Issue 2)

When Issue 1 was resolved (see Solution below), the object manager using Database authentication was accepting connections.  However, the ADSI authenticated object manager was failing to accept connections.  For the ADSI authentication object manager, the user login page was not rendering, displaying the error:

"The server you are trying to access is either busy or experiencing difficulties ..."

The object manager session log (when event logging was increased) was showing the following sequence of messages and errors ...

 
SecAdptLog 3rdpartyTrace 3 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 (IADs*)c255a00->Get('physicalDeliveryOfficeName') returns 0.

SecAdptLog API Trace 4 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 SecurityGetCredentials() return 0.

SecAdptLog Memory Mgmt Trace 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 SecurityFreeCredentials(a6b2460)

CchMgrLog CchMgrStatsInfo 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Cache statistics b384710 set for cache Data Cursor.

CchMgrLog CchMgrStatsInfo 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Cache statistics b3847a8 set for cache SQL Cursor.

ObjMgrDBConnLog Create 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 DataBase Connection Object was created at b384660; DB User: 'LDAPUSER'

ObjMgrDBConnLog Create 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Opening DB Connection: b384660

ObjMgrDBConnLog Multiplex 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Set shared session DB connection b384660 (sessionRefCount=-1, idle=1, long-locked=0) for PhysModel ee04400

ObjMgrSessionLog ObjMgrLogin 3 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Shared Connection Id:

ObjMgrSqlObjLog Execute 4 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Begin: Execute SqlObj 'Database Version' at adb0100

ObjMgrSqlObjLog NamedSearch 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Begin: SetNamedSearch for SqlObj 'Database Version' at adb0100, Named Search: 'VisibilitySearch' - ''

ObjMgrSqlObjLog NamedSearch 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 End: SetNamedSearch for SqlObject at adb0100

ObjMgrSqlObjLog NamedSearch 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Begin: SetNamedSearch for SqlObj 'Database Version' at adb0100, Named Search: 'Auxiliary Id Named Search' - ''

ObjMgrSqlObjLog NamedSearch 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 End: SetNamedSearch for SqlObject at adb0100

ObjMgrSqlObjLog Sort 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Begin: SetSortSpec for SqlObj 'Database Version' at adb0100, Sort Spec: ''

ObjMgrSqlObjLog Sort 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 End: SetSortSpec for SqlObject at adb0100

ObjMgrQueryLog Cache 5 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 Using Cached Query: Database Version:REMOTE

...
...

ObjMgrLog Error 1 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 (odbccon.cpp (2097)) SBL-DBC-00105: An error has occurred executing a Sql statement.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

DBCLog DBCLogError 1 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 SQLError: [S0002],[Microsoft][SQL Native Client][SQL Server]Invalid object name 'dbo.S_APP_VER'.

DBCLog DBCLogError 1 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 SQLError: [37000],[Microsoft][SQL Native Client][SQL Server]Statement(s) could not be prepared.

ObjMgrLog Error 1 0000f4ec4fd50ab0:0 2012-06-11 16:12:01 (sqlmisc.cpp (5663)) SBL-DBC-00105: An error has occurred executing a Sql statement.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

Changes

The customer worked with their network and server infrastructure group and determined that Symantec anti-virus software had recently been installed on all of the Windows servers. 

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.