psexec and AGFA ConfigManager

Clive Andrews · Post by **Clive Andrews** » Fri Dec 09, 2011 11:15 am

Tough one here, I'm trying to launch AGFA's ConfigManager from our Switch machine with PSExec.

(bear with me)

So from a command prompt I'm sending:

C:psexec Xserver -u Username -p Password c:ConfigurationManager.exe -a P:ApogeeCustomer99999 /all

I'm getting "ConfigManager.exe eited on Xserver with error code 2"

Anyone know what "Error code 2" is...?

If I launch psexec to a command prompt with:

C:psexec Xserver -u Username -p Password cmd

then manually put c:ConfigurationManager.exe -a P:ApogeeCustomer99999 /all

...all is fine. So I'm guessing there's something in the full command line that ConfigManager doesn't like - do I need to enclose in quotes, am I missing a switch....?

It's a tough ask - but could be a major scripting breakthrough for me! If any of you have ideas I welcome your suggestions!

TIA

dkelly · Post by **dkelly** » Fri Dec 09, 2011 3:18 pm

error code 2 is ERROR_FILE_NOT_FOUND

Clive Andrews · Post by **Clive Andrews** » Sat Dec 10, 2011 6:13 am

dkelly wrote: error code 2 is ERROR_FILE_NOT_FOUND

Excellent, just what I needed. I'll have a look at how the archives are mapped on client and slave!

Clive Andrews · Post by **Clive Andrews** » Mon Dec 12, 2011 11:26 am

Clive Andrews wrote: [quote=dkelly]error code 2 is ERROR_FILE_NOT_FOUND

Excellent, just what I needed. I'll have a look at how the archives are mapped on client and slave!

Hmmm, so I tried the UNC path, no good, nor the IP address...

Will have to read more on psexec, see if I can or need to put in a logon with the unc path....