Basic troubleshooting of Workflow Enterprise Management validation issues.
Article ID: 165041
Validating an environment in Workflow Enterprise Management (Manager > Workflows > Workflow Enterprise Management) fails.
Workflow Server installed on the separate Workflow server and SMP should be the same version (at least major and minor version if not the exact build). Workflow Enterprise Management uses parts of the Workflow Server installed on SMP to communicate with separate Workflow Servers and larger version differences can cause problems there.
When SMP is upgraded, the Workflow Server on it does not get automatically upgraded. Workflow Server installer should be run on SMP manually to upgrade it to matching version. Workflow Server installer can be retrieved from SMP using either of these locations:
Symantec Management Console > Manage > Workflows > Download Workflow Server and Designer
Upgrading the Workflow Server on SMP should be as simple as running the installer with user that has local administrator rights, selecting Upgrade and providing appropriate responses to the installer prompts. That installation does not have a Process Manager Portal or Process Manager Database roles so no advanced components, prerequisite or account issues.
On Workflow server, start LocalMachineInfo Editor, in Workflow Server section click '...' next to Workflow Server Configuration. Make sure 'Enable WAS Management Service' is checked in that dialog.
Validation checks for Workflow Server, Background Processing and Process Manager Portal roles, because these three are expected from a fully fledged Workflow environment. When you try validating an empty Environment, these are exactly what you see validation claims to be missing.
The only roles WF Server on SMP is expected to have is Workflow Server and Background Processing. Because of this, Local SMP Environment is pretty much expected to have validation errors, usually NotAllRolesPresent (due to Portal/DB not being installed on the WF installed on SMP) and DefaultWorkflowPersistenceTypeIsNotSQL (again, due to no DB).
Fortunately, validation errors have quite well readable descriptions. Anything with Warning Only being True can be ignored, others need to be addressed. If you can publish projects, rest of the validation errors can be ignored if you so choose.