Beta12:
Log Name: Application
Source: Application Error
Date: 11/28/2013 10:55:52 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: lapro3039
Description:
Faulting application name: deadlinemonitor.exe, version: 6.1.0.53841, time stamp: 0x5294de20
Faulting module name: python26.DLL, version: 2.6.7150.1013, time stamp: 0x4e00e564
Exception code: 0x40000015
Fault offset: 0x00000000001233ba
Faulting process id: 0x140
Faulting application start time: 0x01ceebd91ab719d9
Faulting application path: C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
Faulting module path: C:\Program Files\Thinkbox\Deadline6\bin\python26.DLL
Report Id: b3727162-585e-11e3-9100-002590912c2b
Event Xml:
1000
2
100
0x80000000000000
103034
Application
lapro3039
deadlinemonitor.exe
6.1.0.53841
5294de20
python26.DLL
2.6.7150.1013
4e00e564
40000015
00000000001233ba
140
01ceebd91ab719d9
C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
C:\Program Files\Thinkbox\Deadline6\bin\python26.DLL
b3727162-585e-11e3-9100-002590912c2b
Anything in the Monitor log from that session?
Nope, there were some instances of starting up RV via script, but its from earlier.
2013-11-28 10:54:51: [VULCAN] WW_107_0020_v0082_tya_WayLessOars_images_render3d_FL-SimpleSpray_L_0
2013-11-28 10:54:51: Testing: \inferno2\projects\vulcan\scenes\WW_107_0020\images\render3d\FL-SimpleSpray\v0082_tya_WayLessOars\beauty_hdx_rlin\ Filmlook = False
2013-11-28 10:54:51: Testing: \inferno2\projects\vulcan\scenes\WW_107_0020\images\render3d\FL-SimpleSpray\v0082_tya_WayLessOars\beautyJPG_hdx_rlin\ Filmlook = False
2013-11-28 10:54:51: Testing: \inferno2\projects\vulcan\scenes\WW_107_0020\images\render3d\FL-SimpleSpray\v0082_tya_WayLessOars\alphaJPG_hdx_rlin\ Filmlook = False
2013-11-28 10:54:51: Testing: \inferno2\projects\vulcan\scenes\WW_107_0020\images\render3d\FL-SimpleSpray\v0082_tya_WayLessOars\Filmlook_hdx_rlin\ Filmlook = True
2013-11-28 10:54:51: Preferred pass is: \inferno2\projects\vulcan\scenes\WW_107_0020\images\render3d\FL-SimpleSpray\v0082_tya_WayLessOars\Filmlook_hdx_rlin
2013-11-28 10:54:51: Starting application
2013-11-28 10:54:51: C:/python26_64/python.exe //s2/exchange/software/managed/pythonScripts/site-packages\scl\rv\launchRV.py \inferno2\projects\vulcan\scenes\WW_107_0020\images\render3d\FL-SimpleSpray\v0082_tya_WayLessOars\Filmlook_hdx_rlin\WW_107_0020_FL-SimpleSpray_Filmlook_v0082_l.####.jpg
2013-11-28 10:54:51: done
She had another crash just now, this time two entries in the event viewer:
Log Name: Application
Source: Application Error
Date: 11/28/2013 2:19:41 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: lapro3039
Description:
Faulting application name: deadlinemonitor.exe, version: 6.1.0.53841, time stamp: 0x5294de20
Faulting module name: python26.DLL, version: 2.6.7150.1013, time stamp: 0x4e00e564
Exception code: 0xc0000005
Fault offset: 0x000000000007c05d
Faulting process id: 0x17d8
Faulting application start time: 0x01ceec6e09cc1b89
Faulting application path: C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
Faulting module path: C:\Program Files\Thinkbox\Deadline6\bin\python26.DLL
Report Id: 2c6c0a13-587b-11e3-9100-002590912c2b
Event Xml:
1000
2
100
0x80000000000000
103053
Application
lapro3039
deadlinemonitor.exe
6.1.0.53841
5294de20
python26.DLL
2.6.7150.1013
4e00e564
c0000005
000000000007c05d
17d8
01ceec6e09cc1b89
C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
C:\Program Files\Thinkbox\Deadline6\bin\python26.DLL
2c6c0a13-587b-11e3-9100-002590912c2b
Log Name: Application
Source: .NET Runtime
Date: 11/28/2013 2:19:39 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: lapro3039
Description:
Application: deadlinemonitor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Python.Runtime.Runtime.PyImport_ExecCodeModule(System.String, IntPtr)
at Python.Runtime.PythonEngine.ModuleFromString(System.String, System.String)
at FranticX.Scripting.PythonNetScriptEngine.ExecuteScript(System.String, System.String)
at DeadlineMonitor.DeadlineMonitorApp.Main(System.String[])
Event Xml:
1026
2
0
0x80000000000000
103052
Application
lapro3039
Application: deadlinemonitor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Python.Runtime.Runtime.PyImport_ExecCodeModule(System.String, IntPtr)
at Python.Runtime.PythonEngine.ModuleFromString(System.String, System.String)
at FranticX.Scripting.PythonNetScriptEngine.ExecuteScript(System.String, System.String)
at DeadlineMonitor.DeadlineMonitorApp.Main(System.String[])
ANother one, looks different from the first couple:
Log Name: Application
Source: Application Error
Date: 11/28/2013 3:31:41 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: vcpro1014.scanlinevfxla.local
Description:
Faulting application name: deadlinemonitor.exe, version: 6.1.0.53841, time stamp: 0x5294de20
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7b325
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ab2
Faulting process id: 0x10b714
Faulting application start time: 0x01ceec712697f7c7
Faulting application path: C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 3be4bae3-5885-11e3-9129-005056c00008
Event Xml:
1000
2
100
0x80000000000000
95827
Application
vcpro1014.scanlinevfxla.local
deadlinemonitor.exe
6.1.0.53841
5294de20
ntdll.dll
6.1.7600.16695
4cc7b325
c0000374
00000000000c6ab2
10b714
01ceec712697f7c7
C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
C:\Windows\SYSTEM32\ntdll.dll
3be4bae3-5885-11e3-9129-005056c00008
Thanks. Looks like there is a memory access error (System.AccessViolationException) based on one of the event logs. Those are never easy to track down… 
The ntdll.dll error in the latest report could be caused by all sorts of things. From what I’ve read, they can typically be one-time things that can go away after a reboot. Maybe try rebooting that machine and see if it happens again.
The monitor in beta12 seems generally very crashy so far. Overnight monitors usually don’t make it till the morning.
For one artist (2 of those crashlogs are hers) it crashed 5 times yesterday
Weird. We’ll start leaving our Monitors running here overnight to see if we can reproduce.