Classic ASP connection problem
-
I have run into a slight problem in some VB6 code called from 'classic' asp page. The VB6 code does a bit of processing and then proceeds to insert a series of rows into a DB table within a loop, e.g.
do 'call generic insert function to DB, connection opened and closed 'increment counter loopAnd this has been working fine for many years. One client has found a problem - I debug in here and when the counter gets to around 3950 rows (changes each time), i get the following error when performing the insert: DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Anybody any ideas as to why this would be happening? -
I have run into a slight problem in some VB6 code called from 'classic' asp page. The VB6 code does a bit of processing and then proceeds to insert a series of rows into a DB table within a loop, e.g.
do 'call generic insert function to DB, connection opened and closed 'increment counter loopAnd this has been working fine for many years. One client has found a problem - I debug in here and when the counter gets to around 3950 rows (changes each time), i get the following error when performing the insert: DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Anybody any ideas as to why this would be happening?Take a look at the event log on the server where SQL Server sits to see if any events have been raised (such as the database shutting down).
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before. -
Take a look at the event log on the server where SQL Server sits to see if any events have been raised (such as the database shutting down).
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.It's a development machine i'm testing it on, with a local sql server - nothing of note in the event logs.
-
It's a development machine i'm testing it on, with a local sql server - nothing of note in the event logs.
In that case - connect Query Analyser to this instance and take a look at all of the messages that it fires when the connection *closes". Just a thought there - you are closing the connection between saves aren't you?
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before. -
In that case - connect Query Analyser to this instance and take a look at all of the messages that it fires when the connection *closes". Just a thought there - you are closing the connection between saves aren't you?
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.I'll give that a go. And yes, they should all be closed...
-
In that case - connect Query Analyser to this instance and take a look at all of the messages that it fires when the connection *closes". Just a thought there - you are closing the connection between saves aren't you?
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.Ok. Just got back to this now. We are using a single connection object that is opened at the start and then closed after performing all the inserts... My trace just shows many Audit Logon messages rather than connection open messages.