Turns out in ASP site's automated deployment process we should have added a step to restart the application after deployment as it doesn't restart the app pool. And, therefore, app was still utilizing what was already loaded (in cache?).
Deploying to ASP site doesn't update connection
Today, I spent 2.5 hours after production deployment of an old ASP application, trying to find out why the site was not connecting to the new database and still hitting the old one as old database was taken offline.
Subscribe to:
Posts (Atom)