When I try to publish workflows I am receiving the following error message:
Where is it saying the file already exists? This is a brand new workflow.
Can you check the TEMP and TMP environment variable folder paths on the Workflow Server computer for both the system variables as well as the user variables based on the service account that's running the Workflow Server?
If that's not the issue either, then please contact your Laserfiche reseller to open a support case. We would need to investigate your Workflow database as well as the Workflow volume (by default stored in C:\ProgramData\Laserfiche\WF\ServerData\$)
The error could be caused by having a full Windows temp directory. Try clearing out the contents from C:\Users\[Username]\AppData\Local\Temp and C:\Windows\Temp
On the Workflow server there were 65,835 items (783 MB) in the C:\Windows\temp directory. After deleting most of the files, I was able to publish the workflow successfully. Thank you for your help!
Wow, this was a nightmare. Good thing I found this post. When workflow fails to publish it locks the database, so even simple queries timeout making it appear to be a SQL server issue. Temporary files are meant to be cleaned up by the application that creates them, not sure how these servers are reaching 64k files, you can see files that go back every month for years. Windows should at least put up a warning if it will block access to a critical folder.
Both folders are only a little over 1MB.
I would still suggest clearing out the contents of that folder.
Another possibility is that the paths being used for the TEMP and TMP environment variables are not using default values. In that case, you may want to confirm the paths for those environment variables and then try clearing out those locations.
Please click on the Help button, select "Copy Diagnostics Data" from the menu and paste the data here?
Failed to publish workflow 'SS - Physician Referrals': The file exists. [0411-WF0] The file exists. ---Stack Trace--- Client trace at Laserfiche.Workflow.Objects.WorkflowObject.Create(Stream activityStream, WorkflowPublishingOptions options) at Laserfiche.Workflow.Designer.PublishWorkflowAction.PublishWorkflowToServer(TempFileStream designerWriter) at Laserfiche.Workflow.Designer.PublishWorkflowAction.InnerPublish() at Laserfiche.Workflow.Designer.PublishWorkflowAction.InnerPublishWithProgress() at Laserfiche.Workflow.Designer.PublishWorkflowAction.Execute() *** The file exists. ---Stack Trace--- Server trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Path.InternalGetTempFileName(Boolean checkHost) at Laserfiche.Workflow.Runtime.WorkflowDbHelper.Compile81(WorkflowPublisherContext context) at Laserfiche.Workflow.Runtime.WorkflowDbHelper.PublishWorkflow81(String designerSourcePath, CultureInfo culture, WcfOperationContext wcfContext, WorkflowPublisherData data) at Laserfiche.Workflow.Operations.Workflow.PublishWorkflowOperation.PublishWorkflow(PublishWorkflowOperation operation, WcfOperationContext context) at Laserfiche.Workflow.Operations.Workflow.PublishWorkflowOperation.AuditedExecute(WcfOperationContext context) at Laserfiche.Workflow.Operations.AuditedOperation.Execute(WcfOperationContext context) at Laserfiche.Workflow.Operations.OperationExecutor.Execute(Object options, SubsystemContextBase statusContext) System.IO.IOException: The file exists. at Laserfiche.Workflow.Runtime.LongRunningOperationContext.GetResult() at Laserfiche.Workflow.Runtime.Systems.SubsystemCommandHandler.ProcessAsyncOperationCommand(AsyncOperationCommand command) at Laserfiche.Workflow.Runtime.WcfSubsystem.ExecuteOperation(OperationCommand operation) Client trace at Laserfiche.Workflow.Internal.WorkflowServerClient.ExecuteCommand(OperationCommand data) at Laserfiche.Workflow.Connection.Client.WorkflowServerAPIExtensions.CompleteOperation(IWorkflowServerApi serverApi, String operationId) at Laserfiche.Workflow.Objects.WorkflowObject.Publish(Stream designerSource, Boolean isTemplate, Nullable`1 workflowId, String workflowName, WorkflowPublishingOptions options) at Laserfiche.Workflow.Objects.WorkflowObject.Create(Stream activityStream, WorkflowPublishingOptions options) ***
Can you check how many entries reside underneath C:\Users\[Username]\AppData\Local\Temp and C:\Windows\Temp? You may also want to confirm the path that's used for the TEMP and TMP environment variables. While the physical size may be little, you could run into problems if there are many entries under those locations, i.e. more than 65,534.
There were around 100 items. I deleted all but 2 in each location. I shutdown the Workflow Designer. Ended the Workflow process in Task Manager. Restarted Workflow Designer. Tried to publish and received the same error message.
Can you attach a screenshot of the environment variables window showing the values for the TEMP and TMP variables (both user and system)?
Also, are you using the Designer from the same computer where the Workflow Server is installed?
I had not tried publishing it from the Workflow Server so I gave it a shot. I receive the same error message as I do on my local machine. Attached is the Assembly Information.
I should also note that this was not happening until we applied Workflow 9.1.1 Hotfix 1013512.
Can you check the TEMP and TMP environment variable folder paths on the Workflow Server computer for both the system variables as well as the user variables based on the service account that's running the Workflow Server?
If that's not the issue either, then please contact your Laserfiche reseller to open a support case. We would need to investigate your Workflow database as well as the Workflow volume (by default stored in C:\ProgramData\Laserfiche\WF\ServerData\$)
I cleaned out the C:\Windows\temp folder on the workflow server and that solved it for me too.