SQL Authentication/SSL Issue
I am having a problem getting authenticated so that I can manage my databases in the Microsoft SQL Server manager. A while back (< 3 months)we had to setup a new password policy and change everyone's passwords and since then we haven't been able to access the account. We've tried taking the policy back and changing the administrator password back to what it was, but to no avail. To get the programs working temporarily I was able to changed the login setting of the SQL services in microsoft management console so they would run and that side is working fine. The databases are functioning correctly and everything is peachy there. The issue is, I need to login so that I can backup the database and I can authenticate. When the login screen pops up for the SQL Server Manager the authentication is set to SQL Server Authentication. SA is the username and the password is saved, we're not sure what it is. I can't find that account in active directory. I've also tried swtiching to Windows authentication, but that also fails. Here's the error message I recieve:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
The System running the database is a Dell PoweEdge T110
Intel Xeon X3430 @2.4 GHz 2.39 GHz
4 GB of RAM
587 GB of free space
Running Microsoft Server 2003 Standard R2 SP2
Please advise, SQL is not one of my strong suits.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
The System running the database is a Dell PoweEdge T110
Intel Xeon X3430 @2.4 GHz 2.39 GHz
4 GB of RAM
587 GB of free space
Running Microsoft Server 2003 Standard R2 SP2
Please advise, SQL is not one of my strong suits.
ASKER
I will have to give this a shot. Thank you for your response, I will let you know how this goes.
ASKER
Does this still apply on a network where another server is Enterprise CA? This file server states that Certificate Services isn't installed on this machine. The DC has a valid cert that expires in 2013 and everything was working fine until the domain administrator
ASKER
Does this still apply on a network where another server is Enterprise CA? This file server states that Certificate Services isn't installed on this machine. The DC has a valid cert that expires in 2013 and everything was working fine until the domain administrator password changed. OWA still works for the users so the SSL cert is still good right?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Okay so I will need to get one specifically for SQL. Now why would that all of the sudden change when the domain admin password changed or is that a coincidence?
It does look like a coincidence to me.
You can, in addition to fixing the certificate issue, try to reset the sa's password as described here:
http://www.mssqlcity.com/FAQ/Admin/forgot_sa_password.htm
Don't forget to change authentication back to Mixed once you are done.
You can, in addition to fixing the certificate issue, try to reset the sa's password as described here:
http://www.mssqlcity.com/FAQ/Admin/forgot_sa_password.htm
Don't forget to change authentication back to Mixed once you are done.
ASKER
Thank you mustaccio! I will hopefully be at that location this week to give this a shot. I will let you know the outcome.
ASKER
While I'm getting approval to obtain a new cert, I started thinking about something: how did the SQL authenticate before? I searched the server for certificates and I found some in the mysql folder. I tried installing them to their default locations and I'm still getting the same error message.
I guess I'm just not understanding why all of the sudden I started having this problem. That server was just deployed in January, so it's not like the 1 year cert would have expired. It must have gotten lost or corrupted, would it be better to try to find/fix the old one or obtain a new one? All of this happened right at the time we changed the administrator password if that helps.....
I guess I'm just not understanding why all of the sudden I started having this problem. That server was just deployed in January, so it's not like the 1 year cert would have expired. It must have gotten lost or corrupted, would it be better to try to find/fix the old one or obtain a new one? All of this happened right at the time we changed the administrator password if that helps.....
See if anything on this page helps: http://msdn.microsoft.com/en-us/library/ms191192.aspx
For example, you could try disabling the connection encryption, at least temporarily. I'm assuming that you are connecting to a remote SQL Server instance, not local.
For example, you could try disabling the connection encryption, at least temporarily. I'm assuming that you are connecting to a remote SQL Server instance, not local.
ASKER
actually I'm connecting to a local instance...that's why this whole thing doesn't make sense to me...but then again I'm no SQL guru.
ASKER
It was a great solution. I'm not sure why this lost its cert, but a new one fixed the issue, and it's running like it did originally. Thanks!
http://blogs.msdn.com/b/sql_protocols/archive/2007/06/27/install-a-self-signed-test-certificate-that-can-be-loaded-by-sql-server-automatically.aspx
As for "sa", it is a SQL Server login and it's not supposed to exist in AD.