I am trying to decide if we want to purchase this software, and on my first testing we try to add a loop.

It's crashed the client every time... Sometimes we get this output:



See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at VisualCronAPI.Permissions.AICBOOHJKFLAPOGHNLBCDCDAKOHILCFNIPHE(PermissionT , ActionT , String )
at VisualCronAPI.Permissions.Check(PermissionT permissionType, ActionT requiredPermission, String specificObject)
at ODNKNCFDHHPJPCMOFFIIHIOEPAPDAKPENFKF.KBKLGNBLHHBMHCHBFICHENDBNBKDHBOFPGOE.FFACNHPOOOJPMGLEIIFNPKGIEOGKHPAPLOCN(PermissionT , ActionT , Boolean , String )
at DialogAPI.KJDEMNCIJEGGGBBEMPFCGPFOPBPIIBMCMGPB(String , String , JobClass& , TaskClass )
at ODNKNCFDHHPJPCMOFFIIHIOEPAPDAKPENFKF.CBLMHJCADOCIMABABGNEFAABMKJGDLNCFAAK.GEEIAGPOOECMFFKLKFNIEHMHBDOMCAKNLLFJ()
at ODNKNCFDHHPJPCMOFFIIHIOEPAPDAKPENFKF.CBLMHJCADOCIMABABGNEFAABMKJGDLNCFAAK.COIBBFGIECMCNHONAAKMPHBAMMJKJNCHMEHK(Object , ToolClickEventArgs )
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
at Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.DoClickProcessing(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
at Infragistics.Win.UltraControlBase.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

---

VisualCronClient
Assembly Version: 6.1.4.12932
Win32 Version: 6.1.4.12932
CodeBase: file:///C:/Program%20Files%20(x86)/VisualCron/VisualCronClient.exe

---

System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

---

System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

System.Drawing
Assembly Version: 2.0.0.0

Thank you for the report. We can probably fix this within a day if we can reproduce this. From the output it looks like you are clicking on the Add or Edit loop button in the Job window (in Tasks tab). It is not clear if it is an existing loop that you already have created or if you try to create a new loop.

Can you reproduce this every time?

If you can reproduce this based on your specific settings please send the settings to support@visualcron.com and we will have a solution for tomorrow.

---

We found how to reproduce this issue. This happens if you try to create a loop before Job is saved. If you save the Job between and then open it and add a loop it works. We will publish a fix within an hour.

---

Thanks again for the report. The fixed version can be downloaded here:

http://www.visualcron.co....aspx?g=posts&t=2743 

---

Thanks again for the report. The fixed version can be downloaded here:

http://www.visualcron.co...g=postmessage&t=2743 

Have I mentioned how much I love the quick support you provide? 🙂 I can't comment on whether the fix works, but I love quick version updates such as this.

Brian