Last updated on JUNE 07, 2017
Applies to:COREid Access - Version: 10.1.4.2
Information in this document applies to any platform.
The Access server hangs on an obxerces-c21.dll error. At the same time the Access Server log contains errors on connecting to the Directory servers.
The Windows Event Log shows that the webgates and ASDK are not able to contact the Access Servers.
Access Servers are unreachable. Similar message can be seen in WebGate Oblog:
.NET Runtime 2.0 Error
Faulting Application: aaa_server.exe, version 0.0.0.0, stamp 4750690
Faulting module: obxerces-c21.dll, version 0.0.0.0, stamp ...
debug ? 0, fault address 0x0058a83
From the WebGate Oblog :
2008/10/12@00:50:02.295000 1180 1896 ACCESS_GATE FATAL 0x00001520 \Oblix\coreid1014\palantir\webgate2\src\iisentry_web_gate.cpp:183 "Exception thrown during WebGate initialization"
2008/10/12@00:50:02.295000 1180 1896 ACCESS_GATE FATAL 0x0000182C \Oblix\coreid1014\palantir\webgate2\src\iisentry_web_gate.cpp:184 "The AccessGate is unable to contact any Access Servers." raw_code^301
From the Access Server Oblog :
2008/10/11@22:51:14.597000 1584 1744 DB_RUNTIME WARNING 0x0000000A ldap_connection_mngr.cpp:435 "Directory is unreachable, down, or incorrect connection parameters were specified" function^LDAPAsyncSimpleBind() userid^cn=oas101ld101,ou=ServiceAccounts,cn=users,dc=oamprod,dc=local
2008/10/11@22:51:14.597000 1584 1744 DB_RUNTIME ERROR 0x000008C1 ldap_connection_mngr.cpp:442 "Failed to connect to directory server" lpszHost^oamldsrv101.tdk.dk port^636
2008/10/11@22:51:14.613000 1584 1744 DB_RUNTIME WARNING 0x00000504 ldap_connection_mngr.cpp:488 "Exception during DB runtime code" function^ObLDAPConnctionManager::CreateAndOpenConnection
When the error occurs (both obxerces-c21.dll and ldap connection errors), It occurs first on one Access
Server which will then hang (but not terminate). This means that no requests are sent to that
server by the frontends. A few hours later the same thing happens to the second Access Server (both
obxerces-c21.dll and ldap connection errors). This causes the second access server process to hang
and the frontend-servers can no longer connect to any Access Servers.
This happens under load when resources were protected using the Anonymous Authentication scheme with "Deny on not protected" set and the user store is Microsoft Active Directory.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms