Member Avatar for Saboor880

Hi to all! I am using sql server 2008 enterprise edition. My instance name is "saboor-pc/ SQLSERVERENT". I am using this server for many months and i am satisfied but today an unexpected error occured when i clicked on "connect" button in sql server management studio. The error was: "Cannot connect to
SABOOR-PC/MSSQLSERVERENT
A connection was successfully established with the server, but then an error occured during the pre-login handshake(provider: SSL Provider, error:0 The message recieved was un expected or badly formatted)(MicroSoft SQL Server)"
above is the error statement in double quots. Please guide me how can i solve this error because i have to do v important work on database which i have created in this server.

  • 5 Contributors
  • 7 Replies
  • 505 Views
  • 5 Months Discussion Span
  • Latest Post Latest Post by Alec_2

Dani AI

Generated

The error shown by — “A connection was successfully established … error occured during the pre‑login handshake (provider: SSL Provider … unexpected or badly formatted)” — means the TCP connection completes but the SSL/TLS handshake fails. Replies from , and covered basic network checks and protocol settings; since those didn’t fix it, troubleshooting should focus on TLS/certificate issues, interception by security software, and anything that changed on the machine (drivers, Windows updates, new security/IDE installs).

Practical checks (safe → more invasive)

  • Confirm the SQL service is running and find the instance’s listening port (named instances can use dynamic ports). Example quick checks:
    netstat -ano | findstr 1433
Test-NetConnection -ComputerName SABOOR-PC -Port 1433
  • Inspect the SQL Server error log and Windows System/Application logs for Schannel/SSL messages or explicit pre‑login errors (these often point to certificate problems or TLS alerts).
  • Verify whether the instance has a server certificate bound or is configured to force encryption; an expired/mismatched certificate will break the pre‑login handshake. If a certificate looks wrong, rebind a valid cert or temporarily disable forced encryption for testing (do this only in a maintenance window).
  • Rule out SSL‑interception by antivirus/proxy appliances (these replace server certs and commonly cause “badly formatted” messages). Temporarily disable such software or test from a different network.

If the above still shows handshake failures, capture the TLS exchange with a short Wireshark trace and look for TLS alerts (e.g., “unexpected_message”) and the negotiated TLS version. For older SQL Server and client stacks, a TLS version mismatch is common — either enable the required TLS on the host or install vendor updates to add newer TLS support. For escalation, gather: SQL errorlog, Windows event entries (Schannel), netstat output, and a short packet capture. Use those artifacts when seeking further help or filing a support case.

Recommended Answers

All 7 Replies

Member Avatar for rubberman

Have you tried restarting the server? Did your system crash while SqlServer was running? You also might run a disk check to see if you have disc / file system problems.

Member Avatar for Saboor880

RudyM , I have tried "netsh Winsock reset" but my problem is not solved . But i have installed Eclipse as new software in my system.

Rubber Man I have tried to restarted my problem but my server does not restared and again that error message displayed which I showed above. My system did not crash ever using SQl server.

Member Avatar for Saboor880

Sorry , restarted my server not problem.

Member Avatar for Saboor880

Hello! actually i wrote above statement ("sorry, restarted my server not problem ") to correct my sentence in previous reply. My server connection problem is not solved yet. if any person have any technique to solve this then please reply.

Member Avatar for Oleg_3

Have you visited msdn? maybe there you can find the solution..

Member Avatar for Alec_2

In some installations of SQL Server, connecting to the Database Engine from another computer is not enabled unless an administrator uses Configuration Manager to enable it. To enable connections from another computer:
Open SQL Server Configuration Manager, as described earlier.
Using Configuration Manager, in the left pane expand SQL Server Network Configuration, and then select the instance of SQL Server that you want to connect to. The right-pane lists the connection protocols available. Shared Memory is normally enabled. It can only be used from the same computer, so most installations leave Shared Memory enabled. To connect to SQL Server from another computer you will normally use TCP/IP. If TCP/IP is not enabled, right-click TCP/IP, and then click Enable.
If you changed the enabled setting for any protocol you must restart the Database Engine. In the left pane select SQL Server Services. In the right-pane, right-click the instance of the Database Engine, and then click Restart.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.