Service Unavailable after installing .NET 3.5

[jojo11]

We updated our win 2003 iis 6 servers with .NET 3.5. I was under the impression that it would only add additional class libraries to the server without making configuration changes. however after the update, users are getting errors on their web app with either one of two errors. Service Unavailable or they are getting prompted for credentials. (This is setup as windows integrated app.)

what can be the cause of this?

-------------------------------------------
Ummm, we have a bit of a problem here....

 

[Motiv]

First make sure you dont have multiple sites with the same application pool running different versions of .NET. You can't run two different versions of .NET in the same application pool so this could be the cause of service unavailable.

Getting prompted for credentials could be a permissions issue. Google FileMon from Microsoft (Sysinternals) and run this application while duplicating the permissions issue (loading the website). See where the possible hang up is (look for Access Denied Results)

 

[jojo11]

Thanks for the help. It turns out that we were using a destructer which closed the command and connection objects. Apparently that goes into unmanaged code if the object is no longer there which causes errors and causes the application pool to stop.

-------------------------------------------
Ummm, we have a bit of a problem here....