Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 ODBC General Network Error

Author  Topic 

1dmf
Starting Member

5 Posts

Posted - 2010-04-28 : 11:39:48
I'm starting to get a lot of members complaining they are receiving the following error...
quote:
DBI connect('FILEDSN=my_file.dsn','myUID',...) failed: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation. (SQL-08001) [err was 1 now 1] [state was 08001 now 01000][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake()). (SQL-01000) [err was 1 now 1] [state was 01000 now 01S00][Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (SQL-01S00) at


I've tried upping commandTimeout / connectionTimeout etc.. disabling pooling, i've addded the reg key hack to stop Sync Flood cutting the connection.

Nothing so far is making a difference, it only seems to happen outside normal office hours and there is no specific time when anything else might be running.

Can anyone advise what might be causing this error or how I could track down the cause of this error.

Cheers,
1DMF

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2010-04-28 : 12:03:13
Anything in the SQL logs or server logs? Any known network issues going on? Anything new introduced lately (network or otherwise)?

Terry

-- The problem with socialism is that you eventually run out of other people’s money. -- Margaret Thatcher
Go to Top of Page

1dmf
Starting Member

5 Posts

Posted - 2010-04-29 : 04:47:05
nope.

Nothing in logs, no known network issues, the only 'new' thing is we put ESET NOD32 Anti-Virus on the web server a few months back, howerver it's the inhouse SQL that is causing the issue which sits at the end of a VPN tunnel.
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2010-05-03 : 09:47:41
Is the AV running at the time(s) in question? Maybe it's more resource intensive than you thought? It appears that the error is at the application level, timing out during a call to SQL. What else runs on that box?

Terry

-- The problem with socialism is that you eventually run out of other people’s money. -- Margaret Thatcher
Go to Top of Page

1dmf
Starting Member

5 Posts

Posted - 2010-05-04 : 05:31:22
Nope no AV, but I think it is to do with a timeout.

I've upped connection and command timeouts even more and so far so good, but need to give it another week or so to be sure, if I get no more complaints then I think we can safely say it's fixed.

Otherwise it's back to the drawing board!
Go to Top of Page

1dmf
Starting Member

5 Posts

Posted - 2010-05-11 : 05:02:34
Back to the drawing board, setting connectiontimeout and commandtimeout to 99999 has not fixed the problem!

I've been recomended on another forum to run a profiler trace, so i'll give that a go, but i'm not sure what i'm looking for.

Can anyone advise on the correct setting for the profiler trace to potentially capture what might be causing the problem?
Go to Top of Page

mine01
Starting Member

1 Post

Posted - 2010-08-16 : 02:21:35
hello.I think that your antivirus gives you false errors.I recommend you to visit top ten best antiviruses http://www.best-antivirus.co/ in order to find review of nod 32 which is in the sixth place
good luck
Go to Top of Page

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2010-08-16 : 03:29:28
What does the connection string look like? Have you changed it lately...? -> "Invalid connection string attribute (SQL-01S00)"

- Lumbago

My blog (yes, I have a blog now! just not that much content yet)
-> www.thefirstsql.com
Go to Top of Page

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2010-08-16 : 03:31:01
Crap...some bloody spam brought an old topic to the surface. Morons!!

- Lumbago

My blog (yes, I have a blog now! just not that much content yet)
-> www.thefirstsql.com
Go to Top of Page
   

- Advertisement -