Hi steph,
From your post, I understand that you're experiencing high cpu usage in
your ASP.NET 1.1 32-bit web app on a Windows 2003 x64. I've searched in our
internal database and found some similar cases, however, most of them will
require live debugging or dump analysis, performance monitoring to
troubleshoot. Based on each case's specific configuration and usage
scenario, there're different workarounds or even cannot be solved without
reinstalling some components.
For such scenario, I suggest you contact Microsoft Customer Support Service
for further help. We're sorry for the inconvenience caused.
Sincerely,
Walter Wang (
[email protected], remove 'online.')
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
