HELP!!!

I dont know if this is the appropriate forum, so if this is incorrectly assigned please let me know where this should be posted.

I am getting the following error messages in the Application Event Log when attempting to access a couple web pages within a web app. The rest of the web pages in teh web app run without error. Anyway here are the errors:

"aspnet_wp.exe (PID: 2664)stopped unexpectedly."

and

"The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: .NET Runtime version 1.0.3705.0- aspnet_wp.exe - Common Language Runtime Debugging Services: Application has encountered a user-defined breakpoint.

Process id=0xa68 (2664), Thread id=0x3ac (940).

Click ABORT to terminate the application.
Click RETRY to debug the application.
Click IGNORE to ignore the breakpoint.."

There are several other ASP.Net web app running on this box and do so without error. The failover box for this one also experinces the exact same errors. Our Test/Q&A box also has the exact same problem

These pages run without error on my development server, as well as a second development server we have running.

All 5 servers are build exactly the same; Win2k, .Net 1.0.

Evidence on the production boxes would suggest that there is a problem with the application, but evidence from the development boxes suggest it is a problem with the production boxes.

We have rebuilt the development boxes to see if there was a configurate difference, but the app still continues to run properly. We are not able to rebuild the production boxes at this time, but we are considering doing this when we are able.

Does anyone have any insite into this, or have any suggestions for how to proceed? We have been unable to find anything on support.microsoft.com that has helped yet.

Thanks
Craig

Craig
-----------------------
there is no place like 127.0.0.1

__________________
Craig
-----------------------
there is no place like 127.0.0.1

"Common Language Runtime Debugging Services: Application has encountered a user-defined breakpoint."

Was one left in the app that could be doing this?

How are these applications being deployed? Are you doing a final release build of these before you send them off to the production/QA servers?

Peter
------------------------------------------------------
Work smarter, not harder.

Well I found the problem. For the first time ever when debugging these pages that were erroring out it broke on a line i had used to break out of an if statement improperly. I removed the line and everything is working fine once again..

Craig
-----------------------
there is no place like 127.0.0.1

Final Release build?? Not sure what you are talking about. We just build the app then copy over. I have read this is not the best way to do it, but it works..

Craig
-----------------------
there is no place like 127.0.0.1

Oh dear dear dear.

Yes, surely it does work (well, you are finding that up till recently it worked). But if you notice that when you build in visual studio under normal development conditions you get not only DLLs but PDB files. These are databases of "symbols" that the debugger uses to map the executing machine code with your lines of source code. You should at the very MINIMUM do a Build -> Rebuild Solution command in the release configuration to get a clean and optimized build of the application before you cut it loose.

Right click on your solution file, then click on "Properties".
Click on the "Configuration Properties".
Notice at the top of the dialog box there is a dropdown which will most likely be showing "Active(Debug)". Click this drop down and choose "Release".
Ok out of everything.
Goto the "Build" menu, then click "Rebuild Solution".

This will rebuild all your projects in Release configuration which is what you need to do. You should NEVER send off code that was compiled in debug configuration unless you are trying to do some advanced debugging on the production server(s).

Something that is a bit easier is to open up a command prompt, and go to the location of your solution file and enter this command:
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv" mySolution.sln /rebuild release

You may need to change the directory to apply to your installation and version of visual studio, but you see what I'm getting at. This will save the headache of having to change settings in the solution within the dev environment.

Peter
------------------------------------------------------
Work smarter, not harder.

I totally forgot about the Debug/Release build feature of VS.Net. It has been a very long time since I have used VS.Net to build apps. I will do this before we go live and in the future. Thanks.

Craig
-----------------------
there is no place like 127.0.0.1