ODBC/Access error "Could not start session"

[DSect]

I've inherited a website and some of the Access 97-driven ASP pages on the site seem to spunk out after about 4 days of a server reset (see below).

The specific error is:
Database Error: [Microsoft][ODBC Microsoft Access Driver] Could not start session

A server reset returns it to normal, but that is not my idea of a fix.

The fun part is.. when I do web searches for that specific error, I get pages from our site and no others. doh!

I've searched high and low for information on this specific (Could not start session) error and have found nothing useful.

System info:
NT4.0/IIS 4/MDAC 2.6/JET 4.0 (or latest)/Using SYSTEM DSN to an Access 97 .MDB file

Any help would be appreciated and thanks in advance!

*D*

 

[DSect]

* BuMp! *

 

[tlbroadbent]

Is there any additional text in the error message? Terry L. Broadbent
Life would be easier if I had the source code. -Anonymous

 

[DSect]

Thank you for your response.
Unfortunately, there is no more text with the error. Here is a GOOGLE snapshot of the page when it is down:

http://www.google.com/search?q=cach...Access+Driver]+Could+not+start+session"&hl=en

Like I said above, when I search for that specific error, it only gives me my own site. I've found nothing on MSDN, Microsoft, techNet , etc.. Ack.. Not even one instance anywhere, except for another persons website that had the same problem.

I am looking to redo the sites' section w/out the FrontPage extension crap in there, but I am also learning this as we go. In the meantime, I've set the "Threads" and "MaxBufferSize" in the ODBC DS configuration to 8132 and 20 respectively (this was suggested by an M$ page on ASp and Access 97)

I dunno.. I've been looking for a while and I appreciate any and all help!

Thanks!

*D*

 

[DSect]

Ok - Here's something interesting:

Here's an e-mail I have received from Microsoft:
-----------------------------------------------------------
I may have found some information that could come in handy in resolving your problem in the link below. One thing maybe you should make sure of is that you are using the Provider of “Microsoft Jet4.0 OLEDB Provider” in your connection object if you are using ADO. The other options available are the PPI over the phone at $245.00 or over the web at $195.00 (from the

http://www.support.microsoft.com

web site). You could also use Visual Studio Product Support if available or self help via newsgroups or

http://www.support.microsoft.com

knowledge base. I hope this can help you resolve your issue.



Q222135 ACC97: Using Microsoft Jet with IIS

http://support.microsoft.com/support/kb/articles/q222/1/35.asp

Glenn Perkins
<mailtoa-glennp@microsoft.com>
___________________________________________________________
End Mail..

If you look at the KB article Q22135 it basically say's that if you run a server and expect 24/7 uptime, DO NOT USE an Access database..

heh - big thanks M$!