It looks like an access rights problem. the Condor daemons run as
SYSTEM so if any of the files or sub-directories of the execute
deny delete access to SYSTEM, condor might be unable to cleanup
after your job, this message seems to indicate that that is the
ERROR: C:\Condor\execute\dir_3180 still
exists after trying to add Full control to ACLs for
There is code in the starter to try and change the ACLs on files in
the execute directory after the jobs exits, but that code doesn't
if the total pathname length of any file exceeds 260 characters.
There is a special program called condor_rmdir that ships with
condor (in the bin directory) that can handle deleting long paths
with SYSTEM deny ACLs, but I suspect that that program is not
enabled in your condor_config file.
search for WINDOWS_RMDIR in your config file. you should see
something like this...
# On Windows, the built-in rmdir command will not
# or files that have Discretionary Access Control (DACLs) that
# access to the SYSTEM account. This binary will take ownership
# files and directories and remove DACLs if needed to delete a
# directory. Elevated priveleges are needed for it to operate
# set this only if Condor runs as SYSTEM. (i.e. as a service)
#WINDOWS_RMDIR = $(SBIN)\condor_rmdir.exe
#WINDOWS_RMDIR_OPTIONS = /s /c
try un-commenting the last two lines.