You are viewing limited content. For full access, please sign in.

Question

Question

Workflow Designer crash on choosing list item in condition

Workflow
Updated December 18, 2018
asked on April 5, 2017 • Show version history

I have been dealing with Workflow Designer crashes when trying to choose a list item in a condition in any window for a year now ONLY in my developer environment and I work around it.

Now it is starting to happen in live customer environments running Windows Server 2016. I think we we need to find a way to prevent this.

0 0

Replies

replied on August 24, 2017

I just faced this issue exactly Today.

Isn't there any solutions yet for it ?

 

 

1 0
replied on April 12, 2018

I am getting this issue in a production environment now. The operating system is Windows Server 2016 Datacenter. The faulting module is comctl32.dll. The reason is Access Violation.

What access is being violated?

Must we shut down the entire workflow designer application just because of an access issue?

0 0
replied on April 12, 2018

My production environment (Windows Server 2012) don't have this issue, but I am facing it from a long time on my test environment (Windows 10) if this helps.

0 0
replied on April 12, 2018

I have had the problem in my Windows 10 dev environment for years, but Windows 2016 is the same operating system, just with the server components like Active Directory, etc.

I wish we could get more information other than access violation. What are we violating? Error codes have gotten so brief they almost could all say just "error" and be as of much help.

0 0
replied on April 5, 2017

Me too!  Any time there is a pick list in a conditional I have to manually type it.  If I select from the list it crashes.

0 0
replied on April 5, 2017

Any list of any size?

0 0
View 1 previous reply
replied on April 6, 2017 • Show version history

I tested with lists of varying sizes (1-5) and it doesn't seem to make any difference.  It also doesn't matter if "Add blank to the list" is checked or not.

I get these errors in the event log:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-04-06T16:54:05.734803900Z" /> 
  <EventRecordID>12984</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>REDACTED</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Laserfiche.Workflow.Designer.exe</Data> 
  <Data>10.0.0.249</Data> 
  <Data>5644b414</Data> 
  <Data>comctl32.dll</Data> 
  <Data>6.10.14393.953</Data> 
  <Data>58ba594d</Data> 
  <Data>c0000005</Data> 
  <Data>000000000004057c</Data> 
  <Data>6e4</Data> 
  <Data>01d2aef639d9f4df</Data> 
  <Data>C:\Program Files\Laserfiche\Laserfiche Workflow 10\Laserfiche.Workflow.Designer.exe</Data> 
  <Data>C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_42151e83c686086b\comctl32.dll</Data> 
  <Data>53ec1012-a782-4610-8b97-167ccf1bf7f1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name=".NET Runtime" /> 
  <EventID Qualifiers="0">1026</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-04-06T16:54:05.625419700Z" /> 
  <EventRecordID>12983</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>REDACTED</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Application: Laserfiche.Workflow.Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr) at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control.WmCommand(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.ComboBox.WndProc(System.Windows.Forms.Message ByRef) at Laserfiche.UI.ComboBoxEx.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef) at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32) at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window) at Laserfiche.Workflow.UI.ConditionExEditControl.ShowConditionEditor() at Laserfiche.Workflow.UI.Conditions.ConditionExViewer.OnViewerClicked(System.Windows.Forms.MouseEventArgs) at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32) at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef) at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32) at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun() at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel() at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[]) at Laserfiche.Workflow.Designer.SingleInstanceDesigner.Run() at Laserfiche.Workflow.Designer.Program.SafeMain() at Laserfiche.Workflow.Designer.Program.Main(System.String[])</Data> 
  </EventData>
  </Event>

 

0 0
replied on April 6, 2017

Thanks, Eric, that's very useful. Unfortunately, the crash is in a Windows library. We've added some code to Workflow 10 to try to protect against the crash and it has helped in some cases, but, obviously, not in your case.

I can reproduce it on Windows 2016 with some fields, but not all. And I can't reproduce it on older versions of Windows.

The library is part of .NET, so it's unlikely we can fix it. But we'll look into it some more.

2 0
replied on April 6, 2017

Every size I have ever used, usually my lists contain vendor names or the words Approve / Deny, etc etc. It works about 10% of the time but with the same exact selection that crashes it the other 90%. If I keep trying it will eventually go through or sometimes I get lucky on the first try. In my Dev environment I just got used to typing it out but didn't know it was going to start doing it on me in live environments. I figured it was because my Dev environment is just running on a Windows Home OS which is not supported.

0 0
replied on April 7, 2017

I think .net 4.6 includes the 4.5 libraries. Can we re-direct it to use those so that it works like it would on previous versions of windows?

1 0
replied on July 6, 2018

I am experiencing this issue often on Windows 10 as well.  I find it is more prone to happen when setting multiple conditions or changing the value of a condition.  While it may be a Windows library that is crashing, it is Laserfiche's misuse of that library that is causing the problem or every other program that uses the library would have the same issue of crashing. I rarely have the issue setting a single condition on a new condition element with no code assigned to the branches yet,

0 0
replied on July 6, 2018

Now that Server 2016 is the most popular OS for our clients to use I train from the start to type out all list values. It's just not worth the risk to save 2 seconds, but it does cause more typos. Before I started typing out all values it used to happen ~70% of the time when setting a condition inside the workflow or in the starting conditions.

Microsoft stated that they did not remove the 4.5 version of the framework. We should be able to target 4.5 inside of 4.6 but I don't know where or how.

0 0
replied on December 18, 2018 • Show version history

Hi,

 

Our organization just upgraded to windows 10 environment and this crash is happening to me when I'm using the dropdown in the workflow designer. Has this issue been resolved? Hot fixes? I don't see any recent posts regarding this. Any help would be much appreciated.

 

Thanks,

Kasey

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...