Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Time-out.. in 2000-IIS and not XP-IIS

Status
Not open for further replies.

ivow

Programmer
Aug 6, 2002
55
CA
Hi All,


The below worked perfectly on Windows XP, and it still does, but on 2000 Server I get the errors:

I try to submit my form the form submitted, but after chugging for a few minutes it
returns the error:

Active Server Pages, ASP 0113 (0x80004005)
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
welcome.asp

After I re-attempt to do the above, then I get this error:

Microsoft JET Database Engine (0x80004005)
Could not use ''; file already in use.
/shipping/welcome.asp, line 56



TIA

Ivo

 
Hi ...
I think in the welcome.asp Page you are useing a database connection ...
can you use ODBC insted of Microsoft JET OLEDB to see if it works ...
I had the same problem on Win NT 4 And W2K...

----
TNX.
E.T.
 
Do you mean a DSN connection? Here's what my connection to the Access Database looks like:

Dim cnn
Set cnn = CreateObject("ADODB.Connection")
cnn.Provider="Microsoft.Jet.OLEDB.4.0"
dbpath = Server.MapPath("OrderTracking.mdb")
cnn.Open dbpath

TIA

Ivo
 
I'm not sure how to do that through ASP, I can do it through Access but not ASP. There's no security on that file right now.
 
The only time i used to get this error was when i was testing my code on my pc which runs as a server and i had the db open at the same time.
 
Hi ...
When you use ODBC you are not forced to use a DSN, you simply just user ODBC Drivers Like this :
Set cnn = CreateObject("ADODB.Connection")

DBConStr = "DRIVER=Microsoft Access Driver (*.mdb);UID=admin;UserCommitSync=Yes;Threads=3;SafeTransactions=0;PageTimeout=5;MaxScanRows=8;MaxBufferSize=2048;FIL=MS Access;DriverId=25;DefaultDir=C:\Inetpub\
cnn.Open DBConStr

with this code, although you are using ODBC but you don't need a DSN configured in your ODBC.

----
TNX.
E.T.
 
Wow, after banging my head for a few hours I found the following:

I had a Recordset loop without a Recordset.movenext statement in it, it misteriously worked OK in XP, but obviously choked my page in 2000.

Go figure... I'm going to do more testing to see if this common behaviour...

weird...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top