ODBC Error(-1): #08S02 - [Microsoft][SQL Server Native Client 11.0]SMux Provider: Physical connection is not usable

Question

Hi i am getting this error while client try to connect to DB. User has correct permission and user can connect manually from SSMS.  But when connect from  ODBC this will through the error.

version :Microsoft SQL Server 2016 (SP2-CU3)  EM edition 

Any one have idea. 

Thanks 

 

Answer 1

Hello,

See this thread SQLSTATE = 08S02, SMux Provider Physical connection is not usable especially the tips from SQL Server Team.

---

Olaf Helper

[ Blog] [ Xing] [ MVP]

Answer 2

Hi Olaf Many thanks for the quick update. How ever Its seams need to change password of the use or SNP features disabled. Why this sudden happen  which worked previously. Will that impact of windows update ?

SQLLog found after reboot instance 

19-07-17 22:50:49.62 spid11s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-07-17 22:50:49.62 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-07-17 22:50:49.69 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ internal ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-07-17 22:50:49.69 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ internal:1433 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-07-17 22:50:50.05 spid5s      Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.

Many thanks 

Answer 3

Hi ashwan,

According your SQL error log, for SQL server could not register SPN automatically, you can give the account permission to register SPN automatically or you can register the SPN manually. Please refer to SQL SERVER – Could Not Register Service Principal Name Persists.

Run cmd:
Setspn –A MSSQLSvc/ Server Name: FQDN or Netbios. Port number/Instance name <Account>

Best regards,
Cathy Ji

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact [e-mail]