Along with escalating the issue to the Xerox Hotline, please verify the following FFC Services are started by the Windows User with permissions to the resources:
Finally, if you haven't done so already, create a new Workflow with a new Watermark Node using a new PDF resource as a debug measure.
The release was pulled due to a series of problems. It was not pulled due to this specific issue. Could you author a SPAR against the problem? This will ensure it is worked for the HTML5 re-release. The future release does not have a defined date.
Hello Hans. I have checked permissions on all of these locations and it still does not work. Is this issue part of why the release was pulled or is it unrelated? Also, is there an ETA when the .1 release will be available again?
I have a workflow in FFC v18.104.22.168 that uses a Watermark to apply a PDF resource to the jobs, and it is working as expected after upgrading. However, I'm using the default 'Local System' to start-up the FFC Windows Services.
Below are a couple more paths where permissions could be a factor when the FFC Windows Services are started by a Windows User:
Hello Hans. I did check permissions on the locations you listed and also tried restoring from a backup, but the issue persists.
I've seen similar issues in the past, where I was able to resolve was by restoring the FFC Exchange backup, overwriting duplicates.
Also, verify the user starting the FFC Windows Services has full permissions to the following directories:
I'm getting an error (required resource not found) on any workflow that uses a watermark component. It seems the system cannot find (or access) the underlying PDF files used in the watermark. I have tried renaming the PDF files, uploading new PDF files into the system, and deleting and re-uploading the PDF file. I have verified that the service is using the proper login account. Has anyone run into this?