win 2003 sp1 with sql 2005 enterprise.
Tried SA.. Tried AD Admin, tried local administrator. Set up in mixed mode so i tried windows and sql authen... I can log in normally with SA and the password and the windows admin account.
Nothing works, tried services off and on. Tried clearing everything
Reinstalled completely...
Only the SQL Server part fails because it requires authentication. All the other parts succeed.
I don't get a log since it just thinks im typing things wrong. Just this
06/06/2006 21:24:59.641 Authenticating user using Windows Authentication
06/06/2006 21:24:59.641 SQL Service MSSQLServer was previously running, ready for authentication
06/06/2006 21:24:59.641 SQL Agent Service SQLSERVERAGENT was not previously running
06/06/2006 21:24:59.782 User authentication failed. Please check to see if the password provided is correct or check to see if the SQL Server Instance is set to Mixed Authentication
06/06/2006 21:25:07.860 Hotfix package closed
basically this is what I get and i am forced to cancel...
Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790
another log, and yes its set to mixed authentication.
06/07/2006 10:08:25.416
06/07/2006 10:09:48.447 Authenticating user using Windows Authentication
06/07/2006 10:09:48.447 SQL Service MSSQLServer was previously running, ready for authentication
06/07/2006 10:09:48.447 SQL Agent Service SQLSERVERAGENT was previously running
06/07/2006 10:09:48.540 User authentication failed. Please check to see if the password provided is correct or check to see if the SQL Server Instance is set to Mixed Authentication
06/07/2006 10:09:55.572 Authenticating user using SAPWD
06/07/2006 10:09:55.572 SQL Service MSSQLServer was previously running, ready for authentication
06/07/2006 10:09:55.572 SQL Agent Service SQLSERVERAGENT was previously running
06/07/2006 10:09:55.650 User authentication failed. Please check to see if the password provided is correct or check to see if the SQL Server Instance is set to Mixed Authentication
06/07/2006 10:09:59.103 Hotfix package closed
and another
06/07/2006 09:09:47.704 Authenticating user using Windows Authentication
06/07/2006 09:09:47.704 SQL Service MSSQLServer was not previously running, started for authentication
06/07/2006 09:09:47.704 Attempting to start service: MSSQLServer
06/07/2006 09:09:51.579 Successfully started service: MSSQLServer
06/07/2006 09:09:51.579 SQL Agent Service SQLSERVERAGENT was not previously running
06/07/2006 09:09:51.688 User authentication failed. Please check to see if the password provided is correct or check to see if the SQL Server Instance is set to Mixed Authentication
06/07/2006 09:09:51.688 Attempting to stop service: MSSQLServer
06/07/2006 09:09:53.688 Successfully stopped service: MSSQLServer
06/07/2006 09:10:19.470 Hotfix package closed
This was a an upgrade that blew up btw and i removed everything and resinstalled.
I'm not a fan of trying to upgrade... but
I've spent many hours searching and tried profiling and I find I can't connect remotely to the server...
So profiler cannot connect and its set to allow remote connections.
I get...
'===================================
Cannot connect to SERVERNAME.
===================================
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(pfutil90)
Program Location:
at CProfilerSqlDbConnection.Open()
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
and this error also
===================================
Cannot connect to SERVERNAME.
===================================
Unknown error. (pfutil90)
Program Location:
at CProfilerSqlDbConnection.Open()
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
Update:
Set the trace to use TCPIP and i can connect... The default protocol isnt working for some reason... and of course i can't specify HOW to connect to apply the patch so thats why its failing.
Update:
Can connect fully to DB's from remote PC's Profiler also. So were down the "default" server protocol selection is the trouble... now im trying to find out where I set that. I
still can't get connected...
played around with all the protocols. Shared memory on and off, named pipes, ip etc etc
Still no authorization.
I did get the authorization to "hang" by starting the service manually while the patch tried to authorize.
|||I'm moving your thread to the Data Access forum. Hopefully those folks will be able to help you debug this problem.
Paul
|||Can you clarify what is your problem now?
1) remote or local connection?
2) connection string?
3) protocols enabled on the server?
4) firewall issue? put your port number to exception if needed.
Thanks,
|||Fixed. This actually was the native client.
I had to adjust the registry values for the native client.
|||What did you adjust? I have the same problem.. or at least the sympoms are the same.
-jr
No comments:
Post a Comment