ALM0007 - Workflow Failed to Execute

Expand / Collapse
 

ALM0007 - Workflow Failed to Execute


Article ID: 51349 - Last Review: November 23, 2011

DESCRIPTION

This alarm is triggered by a VWM workflow failing to execute.  This can occur for two different reasons:

  • A device referenced in the callflow no longer exists in YourSite Explorer.
  • Workgroup configuration does not allow propper access to the IVR UNC path.

SEVERITY

Error

IMPACT

The IVR call flow is not functioning.

TROUBLESHOOTING STEPS

The cause of this alarm is due to the removal of a device referenced in a callflow without updating/saving it. When the call is processed it will identify that the device it references is missing and will trigger the alarm. The best way to troubleshoot this alarm is to look in the IVRInboundService_Workflow log to identify which device it's trying to reference to.


In the case of a bad workflow, correct the configuration in YourSite Explorer so that either the missing device is re-added, or the call flow is pointed to a current device.

In the case of Workgroup configuration you should ensure the following is set correctly:
  • The IVR services need to run under a system administrator account.
  • The system administrator account needs to have the same username and password on any remote machines as it does on the server.


APPLIES TO

VWM 6.0.2.0

Keywords: ALM0007 workflow failed to execute UNC


Rate this Article:
     

Add Your Comments


Name: *
Email Address:
Web Address:
Verification Code:
*
 

Details
Last Modified:Wednesday, March 06, 2013
Last Modified By: amontpetit
Type: ERRMSG
Rated 2 stars based on 2 votes.
Article has been viewed 15,660 times.
Options