Kbase P165192: AppServer connection to MSS DataServer fails with authentication errors 6142 6179
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  5/4/2010 |
|
Status: Unverified
SYMPTOM(s):
AppServer connection to MSS DataServer fails with authentication errors 6142 6179
AppServer connection to MSS DataServer fails with authentication problems
AppServer Server log file shows multiple errors
Error <read/writing> socket, ret=<n>, errno=<n>. (778)
Error reading socket, ret=10054, errno=2. (778)
** Incomplete write when writing to the server. (735)
Application Server disconnected with connection id: <connectionid>. (8359)
Failed to connect to the <db-type> database. (6142)
Failed to connect to the MSS database. (6142)
Login was denied because of an authorization error. (6179)
28000: [Data Direct][ODBC SQL Server Driver][SQL Server]Login failed for user '<username>'
_MSSSRV.EXE process crashes
Protrace file indicates that the point-of-failure occurred in p1msss23.dll
AppServer has to be restarted for connections to the DataServer for MS SQL Server to succeed again
FACT(s) (Environment):
P1MSSS23.DLL is the OpenEdge 10.2A ODBC Wire Protocol Driver for MS SQL Server
Ret code 10054 from error 778 resolves to "Connection reset by peer"
Errno 2 from error 778 resolves to "File not found"
AppServer connects to DataServer for MS SQL Server Unified Broker at startup
AppServer and MS SQL Server are installed on the same server
DataServer for MS SQL Server uses Unified Broker configuration
Problem does not occur in version of the application running in OpenEdge 10.1
OpenEdge 10.2A
Windows
MS SQL DataServer
CHANGE:
Upgraded to OpenEdge 10.2A
CAUSE:
The exact cause is unknown at the time of this writing but symptoms would appear to indicate a bug in the OpenEdge 10.2A ODBC Wire Protocol Driver for MS SQL Server. The OpenEdge 10.2A ODBC Wire Protocol Driver for MS SQL Server crashes which in turn brings down the _MSSSRV.EXE process which connects the AppServer Agent to the MS SQL Server database.
FIX:
Use an ODBC driver installed with MS SQL Server in place of the OpenEdge 10.2A ODBC Wire Protocol Driver for MS SQL Server