It certainly looks like a network issue - do the users report any other problems with logging into their machines, etc?
BTW, you posted the username and password here for the sql server.
>I have a application that is client server based. When the app is launched, I create a connection to the SQL Server. At one client (there are 8 seperate ones using this application), they have a problem with some workstations (not all) that connect to the Database sometimes and then don't connect other times. These clients are all in different states than me, so I don't get to sit and try things on the workstation. But I have modified the application to capture and ftp the connection error data, the data is mostly from aerror():
>
>
>Workstation: SFMC-6MDM021-OR # RICE
>Connection String: DRIVER={SQL SERVER};SERVER=sfmc-cqi-server;UID=ctore;pwd=APP19A;Network=DBMSSOCN;database=CTORE;App=CTSQL
>AERROR(1,1): 1526
>AERROR(1,2): Connectivity error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
>AERROR(1,3):ODBC Message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
>AERROR(1,4):Current ODBC State: 08001
>AERROR(1,5):ODBC Error #: 17
>AERROR(1,6):ODBC Conn. Handle: 1
>Module: ctconn.prg
>MDAC Version: 2.71.9030.9
>Windows: Windows 5.00 - Service Pack 4
>App Ver: Version: 1.3.103
>Logged At: 11/20/2003 09:02
>
>
>It happens on random workstations at random times during the day. It then will eventually let the user in. I of course don't know if they have rebooted, or logged out of the network or anything they may have done. They say they keep trying and eventually it lets them in.
>
>To me it sounds like there may be a network issue or setting going on. Any sugguestions in where I should look would be greatly appreciated.
>
>Kirk
Wayne Myers, MCSD
Senior Consultant
Forte' Incorporated
"The only things you can take to heaven are those which you give away" Author Unknown