June 16, 2009 at 7:49 am
I have several users that use a custom created in-house Access application which uses a SQL2005 database. Connection is using SQL Native Client. A couple weeks ago, one user could no longer connect to the database. She has Administrative rights on her local machine, but even logged in with my domain admin account, still can't make the connection.
Error is:
Connection Failed:
SQLState: '08001'
SQL Server Error: 0
[Microsoft][SQL Native Client] Unable to complete login process due to delay in opening server connection.
In DSN Connection using:
"With SQL Server authentication using a login ID and password entered by the user" and
"Connect to SQL Server to obtain default settings for the additional configuration options"
Computer in question is running XP Pro SP3 (all current security updates)
Access 2003
The connection was working prior with the exact same configuration.
The connection works for all other users/computers on Win2K and XP machines using Access, 2000, 2003, and 2007.
We've been using this application with the same connection for over two years, trouble free.
I can't identify anything that changed to cause it.
Having difficulty sifting through search results. Nothing seems to completely identify the root cause.
SQL Server 2005 is running on Windows 2003 Enterprise Server R2 SP2 64 Bit
Server Application log Error:
Category (4)
Event ID: 18456
"Login failed for user 'Admin'. [CLIENT: 136.146.156.16]"
(oddly, I don't have a user - 'Admin')
I'm sort of at a stand still on this and she is a primary user and I need to get this working for her again ASAP. Any advice would be appreciated.
Added note. I am getting frequent SideBySide errors on the system log of the client machine in question. I am unable to determine what is causing them, and do not know if they are related.
Event ID 59
Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\MFC80.DLL. Reference error message: The operation completed successfully.
.
Mark Bowker
System Administrator
Alaron Corporation
June 16, 2009 at 8:25 am
It's possible that you have machine (OS/hardware ) issues. One quick check, swap the network cable out.
Beyond that, can she log in from another machine? Can you log in from her machine? From there, perhaps try a simple ODBC connection, or even a replacement of the Access app with another copy.
Try to figure out if it's really the machine. If it is, I'd look at a rebuild/replacement of the OS.
June 16, 2009 at 8:42 am
I'm inclined to agree that it's localized to her machine. She can log in on other computers, and I've been able to work around it that way. The login isn't an issue. It's the connection from only that one machine.
The network card is Wireless, and it is working fine. She has no problems accessing mapped drives that reside on the same Server as the SQL Server, no problems with internet, or VPN access to our parent company. No Conflicts in hardware devices.
The thing that has me puzzled is why the Failure Audit on the Enterprise server event log shows. "Admin" as the user that tried to authenticate.
Using this link
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx I've verified the Error State 4 is "Invalid userid". That's why I'm wondering why it is showing "Admin" as the user that tried to authenticate (I have a domain user "admin" but that is no longer used and hasn't been used for a couple years). My expectation is that it should be the user that's logged into her machine (i.e. her or me).
Part of my problem is I'm not a SQL Server guru. I know enough to be slightly dangerous and that's about it. But I do know enough about troubleshooting to doubt that it's hardware, or the OS. It's something to do with how it's trying to connect.
I doubt it has anything to do with it, but SQL Native Client Version being used is version 9.00.2047.00 - figured I'd include that in case it's relevant.
I have also tried the connection as a File DSN (which it was originally), as well as System, and User, all with the same result and errors.
June 16, 2009 at 8:57 am
Hello,
You could try running through this Troubleshooting guide (if you haven’t already):-
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
June 16, 2009 at 9:02 am
That's very strange. No system DSN set up in control panel?
Is this NTAuth or SQL? I'm assuming NTAuth. If you log in, and try to connect, do you see a different user on the server? I might use Profiler to trace a few login attempts and try to see what comes through.
June 16, 2009 at 9:07 am
Try this:
From the Computer in question:
goto Start-->run-->type: "cliconfg"
in the windows check to see TCP/IP and named Pipes are on the right side List. if not add them.
goto Alias Tab: if you see the server name the computer is trying to connect to remove it:
Then click on add--> Select TCP/IP (named pipes is the default selcted) and in the top Server Alias box type the name of the SQl Server you are trying to connect to: Click ok.. ok then check to see if the connection is established:
if the SQL Server is remotely located(across a WAN) use TCP/IP if same network/domain you can use Named Pipes
Maninder
www.dbanation.com
June 16, 2009 at 9:45 am
Thanks for all the suggestions guys. I'll work through all those and get back with you.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply