We have the following problematic behaviour on our production server (.NET 4.0, Windows Server 2003, IIS 6.0): Almost every morning, the users will complain that the sitemap used for navigating has disappeared. We use the standard SiteMapPath control, with a static XML file that contains the site structure. Reycling the application pool resolves the problem.I was unable to find any obviously related error messages in the event logs. The sitemap did not disappear when we used .NET 3.5, now we use .NET 4.0. The users most often access reports using ReportViewer 2010 in local mode (loading rdlc files)As of now,we are unable to reproduce the behaviour on our test system, but since we don't have dedicated test users, the test server is idle most of the time. If it has to do with recycling the app pool, maybe it only happens under load, I don't know.Can anyone suggest an approach on how to get to the source of the problem? Reverting to 3.5 would take a lot of effort since we already depend on 4.0 in some places.
View Complete Post