Well, yes, perhaps, but more actively. You will need to connect to the IIS workflow with the website (w3wp.exe). I have not done this very often, and I usually try to avoid it, because as long as you are attached, no one can access the website.
Here is an article explaining the process.
http://www.codeproject.com/KB/aspnet/ProcessAttache.aspx
The article is based on 2.0, but not 1.1, but it should still give you an idea of ββhow to do this. I suppose you have to have a visual studio on a production server.
If this is not possible and you have access to the code, you can also try registering in a text file at specific points in the application. I did this very effectively to find problems that allow you to start the site as usual and just check the log file after you know that the problem has occurred.
You can check log4net, which is a free logging application.
Good luck.
user69889
source share