BIZWEAVER

All

Workflow failing but no step obviously failing.

Error text “800700a4 No more threads can be created in the system”

An issue with a problem in a DI Server Mapper step can cause the workflow to “hang” at that step and never complete.  This results in an instance of the “Bizweaver Commander” application remaining open.  If the workflow is set on a schedule, more and more “hung” processes will accumulate, causing the “no more threads” issue.

<p>Bizweaver Commander is used to execute scheduled jobs.&nbsp; It is normal to see an instance of the application be displayed in Windows Task Manager when a new job is started.&nbsp; However, the instance should close as soon as the job is completed.&nbsp; If “hung” instances are identified, use the following steps to clear the system.</p><p>1)&nbsp; Stop the Bizweaver Service.&nbsp; This will prevent scheduled jobs from starting while the issue is resolved;<br />2)&nbsp; Terminate all instances of “BizweaverCommander.exe” found under Processes in Windows Task Manager;<br />3)&nbsp; Check the SAP Mapper step in any workflow that may be causing the issue.&nbsp; This may take some trial and error to find;<br />4)&nbsp; Delete and recreate the Mapper step.&nbsp; It should allow you to set the mapping normally.&nbsp; Deactivate the workflow if necessary to allow other processes to continue;<br />5)&nbsp; Restart the Bizweaver Service;<br />6)&nbsp; Monitor Windows Task Manager to be sure there are not instances of “BizweaverCommander.exe” are not closing in a timely fashion.</p><p><br /></p>

Solution

07 Dec 2018