Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Logon Failure - Failed to copy directory to target

Casey Curtiss

May 25, 2012 15:42

Comments : Deployment system, target system, and file server are all on the same domain, credentials used are those of a domain admin. Admin Repair run on target reports all good.

E-Mail <name withheld>
Error : Logon Failure - Failed to copy directory to target
Error Type : AdminArsenal.Runner.FileAuthenticationException
License Mode : Free
Memory : 2 GB (196 MB free)
Product : PDQ Deploy
Subject : PDQ Deploy Diagnose Report
Version : 1.5.3.0
Windows : Microsoft Windows XP Professional (5.1.2600.196608)

Logon Failure - Failed to copy directory to target
File Path: <path withheld>\Applications\Installs\DB2\DB2-9.7-x86
Computer Name: <computer name withheld>
User Name: <domain\user>
Installer: DB2 9.7 x86
AdminArsenal.Runner.FileAuthenticationException
at AdminArsenal.Runner.RemoteRunner.CountDirectoryBytesToCopy(String directory)
at AdminArsenal.Runner.RemoteRunner.ApplyFileCopy()
at AdminArsenal.Runner.RemoteRunner.Process()

Originally from ticket 10976

Comments

2 comments

Shane Corellian
May 25, 2012 15:49

Are you using the same credentials to run the Background Service (go to File > Preferences - Background Service panel) as you are to deploy?

If you are running different credentials, please verify that the user account running the Background Service has appropriate rights on <path withheld>\Applications\Installs\DB2\DB2-9.7-x86. In this case your Background Service credentials are the creds being used to grab the install file(s) from your file server and the Deploy credentials are being used to perform the installation. Make sure your Background Service credentials have appropriate access to the file server storing the installer files.

Also, will you restart the Background Service? It is possible that the service has a corrupt token which would explain why the Remote Admin Repair is not failing but the service credentials are.

0
Shane Corellian
May 25, 2012 15:50

From Casey

"Looks like that is it, wasn't aware how important that background account was, I skimmed through the install of this version upgrading from a much older one without it. The error message and online help didin't mention any credentials other than the ones I supplied specificly for the deployment being a factor.

I purposfully entered in a local account during installation that doens't have access to anything else because honestly, I'm just not that comfortable having domain admin credentials saved inside any program. In the prior version of PDQ Deploy I just entered fresh DA credentials everytime I did a deployment. Guess I'll just have come up with a PDQ specific domain workstation admin account now.

Thanks for the quick assistances."

0