Can you please forward the ASP page, or a fragment of it
containing the surfer call?
Also, where is the trap occurring--in the ASP side, or
If Screensurfer side, an you please "uncheck" the Catch
Exceptions checkbox in the Admin console settings page?
This way the trap will go all the way and while it will kill
Screensurfer, at least we can get a Dr. Watson log that you
can send-in (\winnt\drwtsn32.log).