Symptom
After a server restart or Failover of SQL Server to another Node, connections from SAP application servers to SQL Server fails. This affects SAP NetWeaver products.
In the dev_disp file you can see many errors like:
*** ERROR => DpHdlDeadWp: Wx (pid xxxx) died (severity=0, status=0) [dpxxwp.c 1744]
If you open the relevant developer trace (dev_wX file), you'll see the following errors:
C ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2551]
C [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: The target principal name is incorrect.
C
C ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2551]
C [Microsoft][SQL Server Native Client 10.0]Cannot generate SSPI context
C ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2551]
C [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: The target principal name is incorrect.
...
B ***LOG BY2=> sql error -21468 performing CON [dbsh 1246]
B ***LOG BY0=> SQL Server Network Interfaces: The target principal name is incorrect. [dbsh 1246]
B ***LOG BY2=> sql error -21468 performing CON [dblink 544]
B ***LOG BY0=> SQL Server Network Interfaces: The target principal name is incorrect. [dblink 544]
Read more...
Environment
- SAP NetWeaver based systems;
- Windows Server 2008 (R2);
- Microsoft SQL Server 2008 (R2);
- The SAP NetWeaver is installed as High-Availability (Cluster) or Distributed System;
- SQL Server is running under a Domain Account;
Product
Keywords
WFCS, HA, high_availability, AD, Active Directory, mssql, msql_sever, msql, mssqlserver, mssql_server, after server restart, after server reboot, after failover , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , BC-OP-NT , Windows , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.