By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,921 Members | 1,949 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,921 IT Pros & Developers. It's quick & easy.

Need help with Strange IIS / TCP lockup problem.

P: n/a
My Asp application is calling a generic logging assembly that acquires the
current process as part of its logging process. The managed C++ assembly
makes a call to Process::GetCurrentProcess()->ProcessName. I noticed that
when this command is executed, the IIS web server will no longer respond
after I close my current browser connection and re-open it. In fact, once I
close my browser, all TCP/IP communication seems to be dead until I restart
IIS. Does anyone have any Idea why this happens? Also, it only seems to
happen when I browse locally on the same machine that IIS is installed on.
If I browse from a separate client machine, then it does not happen.

Ken Varn
Senior Software Engineer
Diebold Inc.

EmailID = varnk
Domain =
Nov 18 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.