Ever got that error when running/debugging an ASP .NET application?
Try one of these methods:
- Check if ASP .NET 2.0 is correctly installed (aspnet_regiis -lv)
- See if the aspnet user has proper (read & execute) permissions over the application's directory - if he hasn't, the error won't be logged to the Event Log.
- See if the application pool for the virtual directory is correct (this problem produces a log entry identifiable in the Event Viewer)