<span style="font-size:11pt;font-family:'Calibri','sans-serif'">If an application that is being run by the Job Manager throws an unhandled exception, the job will continue to keep running indefinitely. If the application running in a task generates an unhandled exception the just-in-time debugger dialog comes up on the node where the task was running and the job remains in a running state.  The only way to get the job to fail is to login to the nodes and close the dialog box, which in turn causes the job to fail.  Is there any way to make the jobs fail without interaction with the node if an exception is thrown?</span>© 2009 Microsoft Corporation. All rights reserved.Tue, 11 Aug 2009 01:14:31 Z163d5d0a-b6be-4422-860d-e915d5c9c622http://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#163d5d0a-b6be-4422-860d-e915d5c9c622http://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#163d5d0a-b6be-4422-860d-e915d5c9c622rmaghttp://social.microsoft.com/Profile/en-US/?user=rmag<span style="font-size:11pt;font-family:'Calibri','sans-serif'">If an application that is being run by the Job Manager throws an unhandled exception, the job will continue to keep running indefinitely. If the application running in a task generates an unhandled exception the just-in-time debugger dialog comes up on the node where the task was running and the job remains in a running state.  The only way to get the job to fail is to login to the nodes and close the dialog box, which in turn causes the job to fail.  Is there any way to make the jobs fail without interaction with the node if an exception is thrown?</span>Tue, 16 Jun 2009 12:30:18 Z2009-06-16T12:30:18Zhttp://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#55f74104-9c26-4080-835a-7d73cbd37d1chttp://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#55f74104-9c26-4080-835a-7d73cbd37d1cColin Watsonhttp://social.microsoft.com/Profile/en-US/?user=Colin%20Watson<p>The JIT debugger should be disabled for a production cluster. See <a href="http://msdn.microsoft.com/en-us/library/k8kf6y2a.aspx">http://msdn.microsoft.com/en-us/library/k8kf6y2a.aspx</a><br/><br/>Thanks, Colin</p><hr class="sig">-Colin Microsoft HPCFri, 19 Jun 2009 01:16:09 Z2009-06-19T01:16:09Zhttp://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#f9c34bbb-d1ce-4abb-996d-cf53e3d5d5fdhttp://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#f9c34bbb-d1ce-4abb-996d-cf53e3d5d5fdrmaghttp://social.microsoft.com/Profile/en-US/?user=rmag<p>The only option I have available with regards to Visual Studio is the Visual Studio 2005 remote Debugger which doesn't give you the option to turn off.  Should this be removed?</p>Mon, 22 Jun 2009 17:34:40 Z2009-06-22T17:34:40Zhttp://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#a9897c17-bde3-43dc-bc6c-ca6da7deb949http://social.microsoft.com/Forums/en-US/windowshpcsched/thread/163d5d0a-b6be-4422-860d-e915d5c9c622#a9897c17-bde3-43dc-bc6c-ca6da7deb949robert.palmerhttp://social.microsoft.com/Profile/en-US/?user=robert.palmerYou could also try setting the registry key directly on your compute nodes.  See <a href="http://msdn.microsoft.com/en-us/library/5hs4b7a6(VS.80).aspx">http://msdn.microsoft.com/en-us/library/5hs4b7a6(VS.80).aspx</a> for the details. <br/><br/>Regards,<br/><br/>RobertThu, 30 Jul 2009 18:55:43 Z2009-07-30T18:55:43Z