At work, we have a Windows NT 4 Server with Service Pack 6a installed. We're running our web site (internal) from it.
The .asp pages run perfect on there until I incorporate ADO to connect to our Access 97 database. When I include that, I'll be lucky to get the page to come up one time. If I go a second time, or any other computer tries to hit it after that initial time after boot-up, the page sits in transition....it never hit's the destination (or at least never appears to) and you wait indefinately.
I am curious if anyone else has ever come across this problem, and if so, how did you work around it...what would you recommend to try to fix this problem. We want to run most of our work from the site, and this is holding us up. The script works on another Windows 2000 server, so it's not the code.
Can anyone help? -Ovatvvon :-Q
The .asp pages run perfect on there until I incorporate ADO to connect to our Access 97 database. When I include that, I'll be lucky to get the page to come up one time. If I go a second time, or any other computer tries to hit it after that initial time after boot-up, the page sits in transition....it never hit's the destination (or at least never appears to) and you wait indefinately.
I am curious if anyone else has ever come across this problem, and if so, how did you work around it...what would you recommend to try to fix this problem. We want to run most of our work from the site, and this is holding us up. The script works on another Windows 2000 server, so it's not the code.
Can anyone help? -Ovatvvon :-Q