|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
.NET Runtime errorI'm facing an unidentified problem related to .NET framework. On event viewer, the following message is logged: Source: .NET Runtime 2.0 Error Reporting Category: None Type: Error EventID: 5000 Description: EventType clr20r3, P1 pos.exe, P2 3.3.2636.21715, P3 4600f8b6, P4 system, P5 2.0.0.0, P6 4333ae87, P7 3246, P8 273, P9 system.formatexception, P10 NIL. This problem seems to be happened in ramdom during the execution of application. When this problem occurrs, my application have to quit and restart again. My application is compiled by VB.NET 2005. I have no idea the cause of this problem. The runtime environment is: * Intel P4 2.0G with 512MB * Windows XP Professional with SP2 and latest pathces * SQL Server 2000 Desktop edition with latest patches * .NET Framework 2.0 with latest patches Thanks a lot for your attention and kindly advice! Regards, James Wong Hi James,
Regarding on this problem, the error message in the eventlog indicate that System.FormatException is throwed from the application (pos.exe?), is this the same application you mentioned in your previous thread? For this exception, it is quite general and hard to determine the exact cause. For example, functions like string.Format, Console.Write that take a string format template will probably raise this exception when the template syntax is incorrect. Or the ADO.NET SqlCommand will also raise this error during executing of command. So far for this kind of problem, if you want to troubleshoot it, there are two common approaches: 1. check all those code will potential raise this problem and add exception handle there(such as console output, string.Format , SqlCommand execute....) 2. Use some advanced debugging tools to perform live debugging against the application and capture the exact type of the exception. This is a bit too complex and generally it is done by the product support team's engineer when troubleshooting. Here is a blog article mentioned this: #ASP.NET 2.0 Crash case study: Unhandled exceptions http://blogs.msdn.com/tess/archive/2006/04/27/584927.aspx Hope this helps. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. 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. Hi Steven,
Thanks for your reply! Yes, this error is occurred on the same application as I mentioned in another thread. I'm still struggling with these "unmanged" problems. In fact, my previous version is compiled by VB.NET 2003 and works fine. In this version, the basic logic of printing and other functions don't change much. So I wonder whether some behavior of .NET framework 2.0 changes from ver 1.1. Anyway, I'll trying to add some codes to get error details. Regards, James Wong Show quote "Steven Cheng[MSFT]" <stch***@online.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D:UIKtjq3bHHA.***@TK2MSFTNGHUB02.phx.gbl... > Hi James, > > Regarding on this problem, the error message in the eventlog indicate that > System.FormatException is throwed from the application (pos.exe?), is this > the same application you mentioned in your previous thread? > > For this exception, it is quite general and hard to determine the exact > cause. For example, functions like string.Format, Console.Write that take > a > string format template will probably raise this exception when the > template > syntax is incorrect. Or the ADO.NET SqlCommand will also raise this error > during executing of command. > > So far for this kind of problem, if you want to troubleshoot it, there are > two common approaches: > > 1. check all those code will potential raise this problem and add > exception > handle there(such as console output, string.Format , SqlCommand > execute....) > > 2. Use some advanced debugging tools to perform live debugging against the > application and capture the exact type of the exception. This is a bit too > complex and generally it is done by the product support team's engineer > when troubleshooting. > > Here is a blog article mentioned this: > > #ASP.NET 2.0 Crash case study: Unhandled exceptions > http://blogs.msdn.com/tess/archive/2006/04/27/584927.aspx > > Hope this helps. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > > > 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. > > > > > > > > > > Thanks for your reply James,
Such general exception does be hard to troubleshoot, that's why we commonly use debugging tools to perform live debug or dump analysis for these cases. Anyway, if you have got any progress or if there is anything we can help, please feel free to post here. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.  |
|||||||||||||||||||||||
Other interesting topics