Virus Scanner induced bug with ASP.NET webservice application
Today I came across a weird, annoying bug. It was an asp.net webservice application that uses MapXtreme 2004, what would happen was the application would restart and cause MapXtreme to crash. The application would crash at different times, each time IIS would need to be restarted to bring the MapXtreme app back up. The problem turned out to be the virus scanner, I think it was locking the temp files that get created by the application in the asp.net temp folder. Once this was turned off the application performed flawlessly. Something to keep in mind, ASP.NET webservices create a code file which contains a custom XML writer for serialization and a reader for deserialization, if these get locked (or permissions are denied, which was my first thoughts) the application will fail.
Today I came across a weird, annoying bug. It was an asp.net webservice application that uses MapXtreme 2004, what would happen was the application would restart and cause MapXtreme to crash. The application would crash at different times, each time IIS would need to be restarted to bring the MapXtreme app back up. The problem turned out to be the virus scanner, I think it was locking the temp files that get created by the application in the asp.net temp folder. Once this was turned off the application performed flawlessly. Something to keep in mind, ASP.NET webservices create a code file which contains a custom XML writer for serialization and a reader for deserialization, if these get locked (or permissions are denied, which was my first thoughts) the application will fail.