Freakish
05-07-2003, 03:20 AM
ASP/IIS is close enough to PHP/Apache... :p
So, I'm working on this little series of asp pages to mess with info from a database at work. This is just a little (local) project to make things easier, so it's not an option to go installing php or anything - I'm stuck with ASP and ADO.
I must be missing something very basic, because I'm getting the strangest intermittent error. Everything will work fine for awhile after I get started and then all of a sudden the page will not load and it'll give me an "Unspecified error" from the line where it connects to the database. If I wait a few minutes, the page will load once or twice before pooping out again.
The machine is Win2k, and everything's up to date.
From what I dug up, I thought it was my leaving out the un/pw string (db is unprotected - don't need it as this a local thing), but adding that to the connect didn't help.
My guess is that this has something to do with Win2k's hard-coded connection limit of 10? Maybe somehow earlier connections from my testing aren't getting dropped fast enough so I get denied as the server sees 10 connections in progress? I've tried decreasing the session times down to 5 seconds or so but this still hasn't helped.
Has anyone had this problem before? Any ideas on what I'm missing? I have a feeling it's right in front of me and I'm just not seeing it... I'm such a n00b at this...
So, I'm working on this little series of asp pages to mess with info from a database at work. This is just a little (local) project to make things easier, so it's not an option to go installing php or anything - I'm stuck with ASP and ADO.
I must be missing something very basic, because I'm getting the strangest intermittent error. Everything will work fine for awhile after I get started and then all of a sudden the page will not load and it'll give me an "Unspecified error" from the line where it connects to the database. If I wait a few minutes, the page will load once or twice before pooping out again.
The machine is Win2k, and everything's up to date.
From what I dug up, I thought it was my leaving out the un/pw string (db is unprotected - don't need it as this a local thing), but adding that to the connect didn't help.
My guess is that this has something to do with Win2k's hard-coded connection limit of 10? Maybe somehow earlier connections from my testing aren't getting dropped fast enough so I get denied as the server sees 10 connections in progress? I've tried decreasing the session times down to 5 seconds or so but this still hasn't helped.
Has anyone had this problem before? Any ideas on what I'm missing? I have a feeling it's right in front of me and I'm just not seeing it... I'm such a n00b at this...