Most of the various error codes can be found in winerror.h. The 0xc part of the error code indicates it is a non-recoverable error.
Error codes are generally broken down like this: // // Values are 32 bit values layed out as follows: // // 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 // 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 // +---+-+-+-----------------------+-------------------------------+ // |Sev|C|R| Facility | Code | // +---+-+-+-----------------------+-------------------------------+ // // where // // Sev - is the severity code // // 00 - Success // 01 - Informational // 10 - Warning // 11 - Error // // C - is the Customer code flag // // R - is a reserved bit // // Facility - is the facility code // // Code - is the facility's status code -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Haselgrove Sent: Thursday, August 09, 2012 1:18 PM To: Eric J Korpela Cc: [email protected]; [email protected] Subject: Re: [boinc_dev] Error Messages There are plenty of lists (and plenty of errors to list) in the smaller numeric ranges, but I haven't found a list for the 0xc0000xxx range yet. In the meantime, we always have http://boincfaq.mundayweb.com/index.php?language=1&viewCat=3 I've edited the Wiki. >________________________________ >From: Eric J Korpela <[email protected]> >To: Richard Haselgrove <[email protected]> >Cc: "[email protected]" <[email protected]>; >"[email protected]" <[email protected]> >Sent: Thursday, 9 August 2012, 17:19 >Subject: Re: [boinc_dev] Error Messages > >An "error codes" forum where the thread ids are the absolute value of >the error number would probably be easy to implement, use a lot of >existing PHP code, and be easy to populate and respond to. > >On Thu, Aug 9, 2012 at 9:14 AM, Richard Haselgrove < >[email protected]> wrote: > >> The particular problem with 0xc0000135 - "The application failed to >> initialize properly" - is that most references found via Google >> assert that the problem can be solved by installing the Microsoft >> .NET framework, but I think that's highly unlikely to be the platform >> a BOINC science app is built on. >> >> It could be caused by a permissions problem, but under the >> circumstances described my money would be on a missing DLL. I've been >> trying to look through CElliott's 11,600 or thereabouts errored tasks >> at SETI Beta, but I haven't found this error yet (a result ID would help). >> >> I would also draw readers' attention to >> http://einstein.phys.uwm.edu/forum_thread.php?id=9489 - we seem to >> have gone through everything from conflicting OpenCL device drivers, >> to "a problem with the latest BOINC version". A suspiciously high >> proportion of the reported cases have been reported 'solved' after >> reverting to BOINC >> v6.12.34 (like today's installment, at >> http://einstein.phys.uwm.edu/forum_thread.php?id=9592) >> >> Going back to the problem of error messages, is there any way we >> could link the numeric code to the one-line text summary, as we do >> with BOINC's own error codes? We could do that on web result pages, >> even if we don't want to bloat the client download with all possible >> error codes. I'll look for a list. >> >> >> *From:* "[email protected]" <[email protected]> >> *To:* Eric J Korpela <[email protected]> >> *Cc:* [email protected]; [email protected] >> *Sent:* Thursday, 9 August 2012, 16:43 >> *Subject:* Re: [boinc_dev] Error Messages >> >> OK, an indication that it was a windows error code would go a ways to >> diagnosing it. The meaning of exit codes are defined by the >> application that exited. If we are using OS error codes for the exit >> codes, we should say so. >> >> jm7 >> >> >> |------------> >> | From: | >> |------------> >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |Eric J Korpela <[email protected]> >> >>| >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |------------> >> | To: | >> |------------> >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |<[email protected]> >> >> | >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |------------> >> | Cc: | >> |------------> >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |<[email protected]>, <[email protected]> >> >> | >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |------------> >> | Date: | >> |------------> >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |08/09/2012 11:36 AM >> >>| >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |------------> >> | Subject: | >> |------------> >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |Re: [boinc_dev] Error Messages >> >>| >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |------------> >> | Sent by: | >> |------------> >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> |<[email protected]> >> >> | >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> >> >> >> >> The problem is that 0xc0000135 implies windows has at least 0x135 >> (309) other error codes that we'd need to build web pages for. Now >> start building web pages for the linux error codes and osx error codes. >> >> The page for 0xc0000135 would say "The application didn't start or >> failed shortly afterward. we can't tell you why because windows >> didn't tell us why. If you've installed your own application >> binaries there could be a problem in your app_info.xml, or you could >> have a buggy system library, or a necessary device driver might not >> be installed, or you could be trying to run a binary for an >> architecture that is unsupported by your version of windows. If >> you're using standard project binaries, reset the project and try again." >> >> On Thu, Aug 9, 2012 at 8:25 AM, <[email protected]> wrote: >> >> > Even if there is limited space in the error message itself, a URL >> > could >> be >> > put in the error message so that someone could find a web page >> > discussing the message. These could be compressed by tinyurl or similar. >> > >> > jm7 >> > >> > >> > |------------> >> > | From: | >> > |------------> >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |Charles Elliott <[email protected]> >> > >> | >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |------------> >> > | To: | >> > |------------> >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |<[email protected]> >> > >> | >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |------------> >> > | Date: | >> > |------------> >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |08/09/2012 11:09 AM >> > >> | >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |------------> >> > | Subject: | >> > |------------> >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |[boinc_dev] Error Messages >> > >> | >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |------------> >> > | Sent by: | >> > |------------> >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > |<[email protected]> >> > >> | >> > >> > >> >> >--------------------------------------------------------------------------------------------------------------------------------------------------| >> >> > >> > >> > >> > >> > >> > On July 9, 2012 Eric Korpela promulgated this edit: >> > >> > >> > >> > " >> > < >> > mailto:SETI@home >> > %20Beta%20Test:%20Stop%20using%20anonymous%20platform%20in% >> > 20Seti@home%20beta.> SETI@home Beta Test: Stop using anonymous >> > platform >> in >> > Seti@home beta." >> > >> > >> > >> > Then on August 8, 2012 he promulgated: >> > >> > >> > >> > "SETI@home Beta Test: You may resume using anonymous platform >> applications >> > is SETI beta." >> > >> > >> > >> > >> > >> > So, returned the app_info.xml file that had been in the >> > .\projects\setiweb.ssl.berkeley.edu_beta to that folder, made sure >> > every file mentioned in the app_info.xml file was in the >> > setiweb.ssl.berkeley.edu_beta directory, and restarted Boinc. >> > Boinc >> erased >> > all (hundreds) of Astropulse work units and printed this message >> > dozens >> of >> > times in the Event Log: >> > >> > >> > >> > 09-Aug-2012 10:06:42 [SETI@home Beta Test] [sched_op] Reason: >> > Unrecoverable >> > error for task 05oc11al.8626.23417.12.14.170_1 ( - exit code >> > -1073741515 >> > (0xc0000135)) >> > >> > >> > >> > Two questions: >> > >> > >> > >> > 1. Virtually every textbook ever written in Computer Science >> > says that error messages should tell the user exactly what is wrong >> > and how to fix it. >> > All the above error message tells is how to convert -1073741515 >> > decimal >> to >> > hexadecimal. Thanks, but I already knew that. What is the source >> > of the error exit code -1073741515 (0xc0000135) is referring to and >> > how do I fix it? >> > >> > 2. Where is the documentation for app_info.xml? All a search >> > on "app_info.xml" returns is tens of thousands of questions about the file. >> > >> > >> > >> > Charles Elliott >> > >> > >> > >> > _______________________________________________ >> > boinc_dev mailing list >> > [email protected] >> > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> > To unsubscribe, visit the above URL and (near bottom of page) enter >> > your email address. >> > >> > >> > >> > _______________________________________________ >> > boinc_dev mailing list >> > [email protected] >> > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> > To unsubscribe, visit the above URL and (near bottom of page) enter >> > your email address. >> > >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and (near bottom of page) enter >> your email address. >> >> >> >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and (near bottom of page) enter >> your email address. >> >> >> >_______________________________________________ >boinc_dev mailing list >[email protected] >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >To unsubscribe, visit the above URL and (near bottom of page) enter >your email address. > > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
