Ralph,  I find that when jobs go into hold or Idle immediately after they go into run status there is a problem with the submit file. Jobs that move to the hold status can mean other things, but for me it usually means I made an error in my submit file.  My first guess would be  the submit user does not have this  drive (D:\) mapped on the client. Are you using load_profile? If not then use UNC paths for everything. If the submit user (depending on how your pool is set up this might be a couple things) does have a mapped drive on the client, then check if the executable will run outside of Condor on your local machine. If the above two tests are vetted, then possibly there is a problem with the central manager communication.  Hope this helps, mike  From: htcondor-users-bounces@xxxxxxxxxxx [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Ralph Finch Sent: Friday, January 11, 2013 12:26 PMTo: Condor-Users Mail ListSubject: [HTCondor-users] Don't understand HoldReason msg  $CondorVersion: 7.9.1 Oct 15 2012 BuildID: 70216$$CondorPlatform: x86_64_winnt_6.1$I'm submitting jobs to the pool and they're all being Held, the reason given is: HoldReason = "Failed to initialize user log to d:\delta\models\Historical_v81_Beta_Release\201X-Calibration\PEST\MTZ_Boundary_EC\condor\dsm2-15-8.log or " I don't understand this because the log files are in fact created in the above directory, with size 0, which I think is normal when nothing is written.Ralph Finch Calif. Dept. of Water Resources