>TBH, at this point I don't see how you can progress this without more information as to what is actually happening and, AFAICS, that means either logging as above or monitoring running processes and/or file access using something like Sysinternals.....

Can we assume that this cannot be related to a query in progress with SQL Server? Because, everyone is within the same situation. Web sites process hits against a database. In our case, we are targeting at SQL Server. So, if others do not have this situation, then, it has to be related to something else.

Also, when it happened once today, I killed the wp3p.exe process and it went ok. The Web site started to respond immediately. I mean, right in the next fraction of a second that is. So, this means the new DLL is loaded in memory. But, the Web site cannot deliver a respond to the request. In the last two times this has happening, I have been able to make it go by killing the wp3p.exe process.