When publishing Workflows, an error occurs indicating that publishing the Workflow failed because the directory is not empty. This occurs regularly, but not everytime when trying to publish.
Application Name : LogicBase.ToolCore.exe Process ID : 9088 Date :7/10/2015 4:05:55 PM Log Level :Error Log Category :EntManDeployAction Machine Name : MHP160SRVC01 Message : System.IO.IOException: The directory is not empty. at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive) at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive) at LogicBase.Tool.Deployment.DeployAction.CreateDeploymentImage(ApplicationProperty deployedProperties, String baseUrl, Boolean showPropertyEditor) in c:\build\projects\WF75_SDSP1_Apollo\core-tool\LogicBase.ToolShared\Deployment\DeployAction.cs:line 245 at Symantec.Workflow.Plugins.Deploy.EntMan.EntManDeployAction.DeployProjectToServer(ApplicationProperty properties, String server, String vdir) in c:\build\projects\WF75_SDSP1_Apollo\plugins\Symantec.Workflow.Plugins.Deploy.EntMan\EntManDeployAction.cs:line 77 at Symantec.Workflow.Plugins.Deploy.EntMan.DeployControl.PublishProject() in c:\build\projects\WF75_SDSP1_Apollo\plugins\Symantec.Workflow.Plugins.Deploy.EntMan\DeployControl.cs:line 470
An external service was monitoring files that publishing was creating and deleting. The monitoring service seems to have put file locks on some files as Workflow tried removing this, preventing publishing from occurring. The monitoring service was scanning all files, but specifically the temp files that get created under the users directory caused the problem.
Disable all monitoring services, or prevent monitoring services from monitoring the local users tmp directories as well as all other Workflow directories. Monitoring Services that lock files used by Workflow can cause problems in many areas.
Subscribing will provide email updates when this Article is updated. Login is required.