aspnet_wp.exe - Application Error

  • Thread starter Thread starter Chris Marsh
  • Start date Start date
C

Chris Marsh

I am continually getting this error and my VS.Net interface somewhat
locks-up. The addresses are both 0x000000000. I find myself resetting
IIS frequently, closing VS.Net and a few reboots a day.

Any ideas why this is?

Thanks,

Chris
 
Hi Chris,

From your description, when you use VS.NET to run your asp.net
application(F5 debug?), there'll occur unexpected application error which
cause the VS.NET IDE crash, yes?

As for this problem, I'd like to confirm some further questions:
1. What's the machine's enviroment? OS and IIS or VS.NET version.

2. What about the detailed error/exception information?

3. If you don't use VS.NET to debug it, just run the web application
outside in IE, will it all faiedl(crash)?

4. If it also failed outside via IE, doest the problem occurs at a certain
page in the web application or can you repro it via a serial accurate steps?

Please check out the above steps. If you have any further findings or
questions, please feel free to post here. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
 
Thanks for the reply,

1 - I am running XP with all the latest and greatest services packs
including running the MS Baseline Security tools. IIS is version 5.1
and VS.Net is 2003 7.1.3088.

2 - The errors vary somewhat, basically it just hangs, when it
ultimately dies I need to run iisreset and/or reload VS.Net. Originally
rebooting appeared to be a requirement but I think just resetting stops
cures some of the problems. Strangly, one of the problems is the
keyboard will no longer allow backspacing, I can only type new but not
edit the existing text.

3 - I've tried to see if the problem(s) would go away if I didn't use
the F5 rather if I used just IE from the desktop and it doesn't. I
appears that when it's not running from IE I must do the IISReset.

4 - The problem will appear on just about any page, however the opening
page for most of the project is the login page connecting to a SQL
database.

Any info is helpful:)
 
Hi Chris,

Since you mentioned that this problem remains if you visit the pages in IE
and occured on most pages of the certain web application. I think you can
try creating a new simple web application to see whether it has the same
problem. If not, we can isolate the problem to the certain web application.

Also, you mentioned that the most pages with the problem is the login page
connecting to a SQL
database. I think you can also try separate the code that connect to the
SQL database to see whether it's the cause of the problem. Or add some
breakpoint to see whether the app will crash at a certain line of code.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
 
Back
Top