Return
-
Title
The term is not recognized as the name of a cmdlet -
Description
After changing a policy type or script function used in the workflow, sometimes the script module could not be found. Error: The term 'sbeb2c54d-b11b-4e28-8992-189f9ff72801' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again:
-
Cause
This issue occurs when script debugging is enabled for several script modules.
NOTE: This error could also be related to a policy having a script specified in its operations. Review all scoped domain policies that are custom if the default built in policy is not being used.
-
Resolution
1. Go to the properties of the scripts which are part of the workflow2. Disable debugging for all the scripts by going to the Debugging tab and disable the Enable Debugging option3. Click on Apply4. Select any one of the scripts and enable the Debugging only for that script.5. Click on Apply6. All the events will be recorded in that script Post this the workflow should work fine -
Change Request
TF00091776