x
login Signup

Step error [AgentFailedMapDrive]: unable to run the command on the agent

Hi, We have a scheduled workflow that runs each day. However, for the past 6 days, whenever the workflow is run, the Step just says "Waiting For Resource" and when we looked at the log, it says:

Step error [AgentFailedMapDrive]: unable to run the command on the agent The agent was unable to map the unc workspace to a drive letter: Couldn't map drive P: to share path "\\usdm2112\CTETEST\commander-workspace-ut": WNetAddConnection2W: Access is denied. (5)

We are not sure which account it is using to map the drive (since it says Access is denied). We were able to logon to the Resource machine and map the network drive as P:\ manually. However, it did no good. Appreciate your help on this.

Thanks, KT

avatar image By kishore thota 15 asked Mar 03, 2015 at 01:49 PM
more ▼
(comments are locked)
10|750 characters needed characters left

2 answers: sort voted first

It would run that command as the agent user. Is that a domain account? a local account would not have access to the network features.

avatar image By lrochette 5.8k answered Mar 03, 2015 at 02:19 PM
more ▼
(comments are locked)
avatar image kishore thota Mar 03, 2015 at 02:31 PM

I dont know where to look for that account to confirm if its domain or local. How do I find it out? I logged on with a Network account manually and mapped the drive (this account is a service account we use for admin tasks).

avatar image lrochette Mar 03, 2015 at 02:39 PM

if you look at the commanderAgent service, and check the logon credentials, a network account with be of the form DOMAIN\username whereas a local account it typically simply username

avatar image kishore thota Mar 03, 2015 at 03:55 PM

Thank you. Its a Local System Account and I cant change it to Domain account since the Agent is Dynamically provisioned in Amazon Cloud and it is in Workgroup and not in our Domain. However, this procedure was working fine until last week and I dont think anything has changed since then.

avatar image lrochette Mar 03, 2015 at 04:15 PM

Without more details (it may be a good idea to open a ticket with support and provide some logs), you could work around this Windows issue by using a local workspace.

10|750 characters needed characters left

I had to change the Local System account to a local account (already existing with the name similar to the domain account that has access to network shares). I guess whoever created the project was aware of this. Once the change is made, the step continued to run with no other issues. Now, I will have to add a step to the procedure to run the service with that account, so we dont have to deal with it each time.

Thank you for your advice.

avatar image By kishore thota 15 answered Mar 04, 2015 at 09:34 AM
more ▼
(comments are locked)
10|750 characters needed characters left
Your answer
toggle preview:

Up to 8 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.