Pause Execution Workflow component not functioning properly in a published Workflow project
Last Updated January 09, 2010
The customer has used the Pause Execution Workflow component in order to delay a process for a certain amount of time. In their testing, they are seeing the project hang up on this component and never complete the process.
The Pause Execution Workflow depends on proper access to webservice files in the published project. These are AutoInvokeDelegateService.asmx and WorkflowManagementService.asmx.
If the entire project directory is set to anonymous everything will work fine. However, if the directory enables Windows authentication, it will cause problems once the project is published. The project will attempt to use the application identity for the application pool and will not have rights to access the .asmx files. These files control the process that makes the pause function.
There are two possible solutions to this issue:
1) Set up HTTP authentication in the Workflow Server Extensions configuration. This will tell the Server Extensions to authenticate using different credentials. This option is found here:
Start > All Programs > Altiris > Workflow Designer > Tools > Server Extensions Configurator
Find the section called "Webservice Auto Invoke", click HTTP Authentication, and put in the username and password that will have the required rights to the .asmx files.
2) Select the AutoInvokeDelegateService.asmx and WorkflowManagementService.asmx files in IIS Manager and set their authentication to Enable Anonymous access. Also make sure that Integrated Windows Authentication is not selected.
Applies To Altiris Workflow Solution 6.5
Imported Document ID: TECH41447
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe