IIS dll problem

[ferrethouse]

We recently moved a website to a new web server with IIS 6.0 (old one had IIS 5.0). Since the move I have found that the dlls become unresponsive on a fairly regular basis (at least once per day). The website itself still works because I can land on the login page but I am unable to login - communication with the dll seems unresponsive. If I recycle the application pool it works again.

Anyone know what I can do to fix this?

Thanks.

[randem]

A dll.... Hummmmmmm, I gues we are supposed to guess at which one????

[ferrethouse]

A dll.... Hummmmmmm, I gues we are supposed to guess at which one????

It is a custom dll. If you want the name here you go...

EarthServerProd.dll

The dll worked fine on the old server with IIS.

Let me know if you need anything else clarified.

[randem]

If it is a custom dll, is it compatible with IIS 6.0? That would be the first question to resolve.

[ferrethouse]

If it is a custom dll, is it compatible with IIS 6.0? That would be the first question to resolve.

Please forgive my lack of knowledge. How do I find out if it is compatible?

[randem]

Check with the person or company who made the dll.

[bgmacaw]

Is this DLL running from COM+ or standalone?

Also look for activity spike that might be coincidentally happening. One place I worked had an automated process that kicked off in the mid-afternoon that killed DB access. Some web configuration and page changes that went out the same week it was originally deployed were blamed at first but later the real resource pig was discovered.

[DSimmon]

Have you tried setting the application pool to automatically recycle once or twice a day (preferably in non-active times)? That might help.

If not...

If you are not running anything else on IIS 6.0, or using 6.0 for the advantages of 6.0, there is the possiblity to run IIS 6.0 in IIS 5.0 Isolation mode and see if that corrects your problem.

http://www.microsoft.com/technet/pro....mspx?mfr=true

Ofcourse, that makes the whole server run in 5.0 isolation mode, and you loose all the benefits of v6, but if that's an acceptable loss for you/co-workers/whatever to get the app up and running, it might work.

[ferrethouse]

Thanks for the help everyone.

It turns out that the problem was not with my custom dll. There is a dll that is not included in Windows 2003 that is included in XP and 2000. It is called...

MSCHRT20.dll

I just copied that dll to the server and registered it and the problem is solved.

Thanks.

[randem]

Well, If you made a proper installation package that would not have happened...