Workflow Soluiton

I'm using the repository to add Integration Libararies into my projects so that I'll always have the current version of it in my projects. I've added the .dll through the Repository tab at the project level:

Under the libraries tab it shows the path to the location where it's pointing to the .dll file

However, when I try to publish the project I get this error. I've checked the permission to the folder and can confirm that they are set properly so I'm not sure why this error is popping up when trying to publish it to the server.

And I really want to use these DLL's from the repository, it makes sharing so much easier...

rob

I believe packages that are deployed get temporaily written to the Windows temp directory. I'd check permissions on that directory and verify it's writeable.

That's not it. Here is the error In the logs:

Error,Thursday, October 06, 2011 4:02:32 PM,System.UnauthorizedAccessException: Access to the path 'ADInfo_Components.dll' is denied.
   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\WF71MR2\core-tool\LogicBase.ToolShared\Deployment\DeployAction.cs:line 248
   at Symantec.Workflow.Plugins.Deploy.EntMan.EntManDeployAction.DeployProjectToServer(String userName, ApplicationProperty[] properties, String server, String vdir) in c:\build\projects\WF71MR2\plugins\Symantec.Workflow.Plugins.Deploy.EntMan\EntManDeployAction.cs:line 68
   at Symantec.Workflow.Plugins.Deploy.EntMan.DeployControl.PublishProject() in c:\build\projects\WF71MR2\plugins\Symantec.Workflow.Plugins.Deploy.EntMan\DeployControl.cs:line 406

There is no folder called C:\Build\ anyting on my comptuer. I'm going toi open a support incident and see if they have any ideas.

rob

I'm getting the same errors as well and have tried playing around with the permissions on the Temp and repository folders but still get the error. There has to be something else that is preventing this from getting deployed. reecardo, can you get it to work on your end?

Application Name : LogicBase.ToolCore.exe
Process ID : 2620
Date :10/7/2011 8:57:18 AM
Log Level :Error
Log Category :EntManDeployAction
Machine Name : DEVSRV107V
Message :
System.UnauthorizedAccessException: Access to the path 'HR Change Events.dll' is denied.
   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\WF71MR2\core-tool\LogicBase.ToolShared\Deployment\DeployAction.cs:line 248
   at Symantec.Workflow.Plugins.Deploy.EntMan.EntManDeployAction.DeployProjectToServer(String userName, ApplicationProperty[] properties, String server, String vdir) in c:\build\projects\WF71MR2\plugins\Symantec.Workflow.Plugins.Deploy.EntMan\EntManDeployAction.cs:line 68
   at Symantec.Workflow.Plugins.Deploy.EntMan.DeployControl.PublishProject() in c:\build\projects\WF71MR2\plugins\Symantec.Workflow.Plugins.Deploy.EntMan\DeployControl.cs:line 406

The C:\build path is just part of the debug message, it's definitely not expecting that on your machine. It has to do with where ADInfo_Components.dll is, when it's trying to delete it.

This error is occurring where we do cleanup after deployment. For some reason, we can't clean up this DLL which is more than likely in a nested folder. We could address this by wrapping the code in a try/catch.

As a workaround, you could always move this shared DLL manually to the target machine, and not Copy Local.

Go to \Program Files\Symantec\Workflow\Shared\repositorylib

You'll see folders representing the Guid for the shared components there. Open that and you'll see folders representing the different versions. In each are the individual DLL's. Right click on each DLL and remove the read only.

That's it, after doing that, it will publish just fine.

Not sure yet if the read only will go back on at some point, but that is the fix.

rob

Awesome thanks Rob. This will help out with development among mulitple developers.