HELP! IIS 5.0 dies

[seanbrown93]

I have a pretty heavy duty Web App that gets hit very hard throughout the day. The App is an ASP with and ODBC connection to an Access 2000 database on Windows 2000 server. About once every other day the ODBC connection to the database dies and I have to restart IIS to get the App back up and running.

Would IIS5RECYCLE help fix this issue before it starts? I was unfamiliar with it until I did some research and found it on Microsoft's site.

Would going to SQL Server fix this as well? I am going to convert and upgrade to SQL Server soon, but wanted to work out the bugs in the App first since Access is easy to use.

Any insight on this would be appreciated.

 

[sohigh2000]

I think it is a good idea to go to SQL server. Before that you may install office 2000 the access component on the server to fix the problem, maybe you should should provide more error messages and explain the problem clearly.

 

[seanbrown93]

Thanks for the reply.

The error is as follows:

Unable to establish connection to database

Error information:
Microsoft OLE DB Provider for ODBC Drivers (0x8007000E)
[Microsoft][ODBC Microsoft Access Driver] Not enough space on temporary disk.

I get this error on any PC trying to access any ASP pages about once every other day (HTML pages are fine). The only way to fix this issue is to restart IIS. The page refreshes (queries) also take way too long when there are lots of people logged on (server speed could be the issue for that).

My question is can IIS5RECYCLE fix this issue before the error occurs? In other words, could IIS5RECYCLE predict that this is going to happen and purge the necessary resources to prevent this without interrupt?

I hope this clears things up.

Sean

 

[FredWagner]

Since the last error message is about 'Not enough space on temporary disk' -take a look at your Access database setup - it may be expecting to be accessed from a workstation-based access client, and a temp file, drive letter or folder it uses on a workstation may not be present on the box where the ASP code is executing. I had a problem were a complex SQL client wouldn't install - until I finally realized that one drive letter it wanted to use for temp files wasn't mapped on the station I was trying to install it on. Substituted C:\temp for the problem letter and it ran fine!

Fred Wagner
KQ6Q@arrl.net

 

[JFBouchard]

Hi, try to delete the content of your TEMP folders as well as *.tmp in c:\winnt (or windows) directory.

I saw this before on IIS, a temp file corruption.

Also ensure that you close your connections in your application (dbclose)

Hope this helps. Please let know if this resolve your issue

Jeff