after upgrading to FFC 6.0 I get an internal server Error when I try to access several Workflows. I can't access, modify or even delete this Workflows. In fact that this system is only for testing, I'd like to delete the Workflows, but I can't. Is there any way to delete workflows without using the FFC website? In the database for example? O is there a tool I can use fot that?
thx and kind regards,
There is a tool, called mdh.exe that could help you (use carefully). From an admin cmd prompt, go "C:\Program Files\Xerox\FreeFlow Core".
This will list all workflows:
mdh lw ( workflow name / id )
This will analyse specific workflow, searching for problems:
mdh aw ( workflow name / id )
This will try to repair workflow
mdh rw ( workflow name / id )
I have the same issue with at least one of my workflows.
thank you for the insight into the mdh.exe tool, I tried as described and when analysing and trying to repair, it is indicating there are no issues, and no issues to repair.
Any other guidance on what may be wrong? i have gone so far as to reboot the remote SQL database and the local server to no avail.
If you have a FFC Exchange Export or Clone that was created prior to the upgrade, Importing it could help. Tick 'Overwrite Conflicting Items During Import'.
I tried to solve the problem with the mdh tool, but it found no problem with the Workflows. The solution for my specific problem was to make a clean reinstall. After that I only imported the working workflows from the 5.4 clone.
I also get the 'Internal Server Error' for any workflow I've edited (there's two now) since upgrading from FFC v5.4.5 to v6.0.0. I'm not surprised as FFC upgrades always seem to cause one issue or another. grrr...
The actual v6.0.0 upgrade went well but while initially the system seemed okay, it soon became noted that some existing workflows no longer functioned as before where the final imposed file was not sent to our iGen even though other workflows did send the file.
I've tried the mdh.exe program as mentioned above but as reported by @ChrisBeech, it reports there are no problems found with both workflows, even though FFC shows 'Internal Server Error' when clicking on them.
I do have a FFC Exchange Clone created from v5.4.5 prior to the v6 upgrade which @Hans995496-XRXL says could be imported combined with enabling the 'Overwrite Conflicting Items During Import' option but I've not tried this yet as I was told by a Xerox Post Sales Analyst, who helped with this particular upgrade, that you won't be able to re-import pre-v6 clones once we've upgraded. Though having said that it seems @tflesch has done this after performing a clean reinstall.
So am I going to have to follow @tflesch and do the same?
Hi, you can delete the desired workflow with the tool called mdh.exe (use very carefully), from an admin cmd prompt, go "C:\Program Files\Xerox\FreeFlow Core":
C:\Program Files\Xerox\FreeFlow Core\mdh dw workflow_name_or_id
I thought I'd use Core Exchange to export my current V6 workflow state to file before attempting to import my previous v5.4.5 clone in to v6, but choosing 'All', regardless of enabling either 'Create Printer Destination Mapping', or 'Do Not Automatically include Files Managed By FreeFlow Core', the process errors with 'Object reference not set to an instance of an object'.
So I went ahead and imported the v5.4.5 clone and I can confirm it did import successfully.
EDIT: All seems okay now.