August 14, 2005 at 10:08 pm
I am trying to connect to SQL Server 2000 and I am getting the following error.
" A connect could not be established to (Local).
Reason: SSL security error
Connectopen(SecdoClientHandshake())..
Please verify sql server is running and check your sql server registration properties (by right-clicking on the (local) node) and try again"
I am using Windows 2003 Server Standard Edition,
How can I solve this problem?
August 17, 2005 at 8:00 am
This was removed by the editor as SPAM
August 17, 2005 at 9:53 am
Haven't done any work with SSL here, but I suspect that there is some certificate problem. Do you need SSL connectivity?
August 17, 2005 at 12:20 pm
Well, I do not need SSL Connectivity but seems that my SQL Server is not accepting a connection unless it was an SSL Connectivity.
I just need to connect to my Database
August 17, 2005 at 2:39 pm
You are going to need to talk to your network guys apparently someone applied a strong security template GPO to your server if what you said is the case and either remove it or set up the clients with the necessary Certificates to connect
Cheers!
* Noel
August 17, 2005 at 5:26 pm
Check the SQL Server Network Utility and make certain that Force Protocol Encryption is UNCHECKED.
September 4, 2005 at 9:41 pm
i have the same error here,, but i only got it after i used microsoft SelfSSL to create a SSL certificate for my web site,, i cant figure out how to get around it either .. i even removed the certificate, but no luck..
ill be hanging for replies to this post too..
jd.
September 16, 2005 at 3:08 am
Well I had the same problem and got rid of it by changing the account that runs the MSSQLServer Service.
Everything was running just fine.
I then tried to create a certificate with the SelfSSL tool (which doesn't mean it has anything to do with the problem).
I then changed the MSSQLServer service to run under the local SYSTEM account.
Bingo it works.
Regards
hot2use
__________________________________
Searching the KB articles is like
picking your nose. You never know
what you'll find.
September 25, 2007 at 8:07 pm
I think this error is due to the SSL certificates installed on your computer. Read this MS KB http://support.microsoft.com/kb/309398, take backup and remove your SSLs. If this fixes then you know the problem
Regards
October 9, 2007 at 2:29 pm
Well I did just that (deleted the user and local server certs.) and everything is working again.
I'll post back if this broke anything else on my computer.
I suppose the next question is 'where did the cert come from?'
November 6, 2008 at 3:30 pm
hot2use (9/16/2005)
I then changed the MSSQLServer service to run under the local SYSTEM account.
Bingo it works.
Regards
hot2use
That worked for me too! Thank You
March 11, 2009 at 2:47 pm
how do you delete the server and local certs?
April 27, 2009 at 4:34 pm
ensigncd (3/11/2009)
how do you delete the server and local certs?
This is from the MS Website (as Matloob said earlier):
======================
1. Click Start, and then click Run. In the Run dialog box, type the following then click OK:
mmc
-or-
At a command prompt, type the following, and then press ENTER:
mmc
2. On the Console menu, click Add/Remove Snap-in. (From the File Menu if you're using Windows XP).
3. Click the Standalone tab.
4. Click Add.
5. On the Add Standalone Snap-ins: under Dialog, select Certificates, and then click Add.
6. Select My User Account.
7. Click Finish.
8. Select Certificates, and then click Add.
9. Click to select Computer Account.
10. Click Next.
11. Click to select Local Computer.
12. Click Finish.
13. On the Add Standalone Snap-ins: under Dialog, click Close.
14. In the Add/Remove Snap-In dialog box, click OK.
=====================
-So if you got that far you should be able to browse
Local Computer-Personal Certificates
and
Current User-Personal Certificates
WARNING! Do not delete anything here unless you are sure you know what to do..And export each cert before you delete it in case you need it later.
In my case the problems (Win2k SQL2000 sp4) were
1.A certificate called "Thawte Freemail Member" which was in:
Certificates-Current User ->Other People>Certificates.
I highlighted this certificate, right-clicked and clicked delete.
2.A Certificate called 'My Computername'\'My Login Name' (Cant't give the real detail here, use you imagination..) which was in:
Certificates-Current User>Personal Certificates
- which I exported to a file and then deleted.
Stopping and restarting the MSSQLServer the allowed me to re-connect to my local data.
- I had this problem before a few years ago and could not remember which cert had caused the problem so I hope this is of some use to others having this problem. MS are extremely vague about what cert can cause this except to say that it will be in one of these stores.
June 5, 2012 at 2:37 pm
Hi Folks,
I got this same error this morning and could solve it by removing the certificates that were having the same name as my server. That solved my problem.
Maybe, your problem is not by just having the certificates with same name as the server, but think about it, almost always, your SSL issues will be linked to Certificates.
Regards,
Best Regards,
Marcos Rosa / marcosfac@gmail.com
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy