ASP.NET Database pages have died

[lorena]

I am working on an application that was functioning properly until we re-located the database to a different share on the web server.

We had permissions problems right away with the new share and so I kept changing the connectionstring information on my form from the working location to the new location.

The databases are Access 97 (ugh)

My question is this - the forms (three of them) have totally ceased functioning. They no longer send the email message they did before, nor do they update the database (either database) and there is no error message.

Has anyone else ever encountered this problem? I put tons of work into creating these pages and it is very frustrating.

We rebooted the web server and it made no difference. I am programming remotely to a network share on the web server so I cannot do any debugging.

[lorena]

This seems to be somehow related to caching on the web server. The new code is not replacing the old code.

Any suggestions would be appreciated.

[MrPaul]

Similar problem

 

This is not really a solution, but I experienced the same or similar problem with newer code not overwriting old code. Since I use FTP I've now got into the habit of deleting the files which are to be replaced before uploading the new versions. As this works fine, and is not such a tedious task, I haven't given it much thought since, but would be interested to know if you find any proper solution - or even just an explanation. As with you this problem seemed to start more or less out of the blue, so I had assumed it was something wrong with the FTP server (and that may still be the case).

 

Anyway, good luck :)

[lorena]

I will let you know what I find out as I am determined to figure out what the heck the problem is!

I am not a network person but it seems to be some kind of issue with IIS since my basic code (other than the database location) has not changed. We have cleared the cache, rebooted the server, set up DisableLazyContentPropagation for each type of ASP, ASP.Net page and now we are back to the proverbial drawing board.

I would appreciate any help in this -