Scheduler Usage

Hi,

We experience OSCOMPSTAT 32 on cyclic jobs lately.
The jobs just does nothing and a rerun goes fine ?
We schedule in a Windows 2003/2008 environment.
Has anyone come across this ?


Greetz,

Windows error codes can actually mean anything - it's one of the "really bad" things about Windows.

However, 32 as a standard often means that the file you want to use is being used by another process.

I found out the following with tracing

0627 21:38:16:394 CTMRJOBWIN2K:OS_FILE_create_tmp_filename: making tmp name at ''
0627 21:38:16:394 CTMRJOBWIN2K:OS_FILE_create_tmp_filename: output fullname='.\TEMP\TMP1340163401', memname='TMP1340163401'
0627 21:38:16:394 CTMRJOBWIN2K:Temp script name is:<TEMP>
0627 21:38:16:394 CTMRJOBWIN2K:OS_FILE_fopen started : .\TEMP\TMP1340163401.cmd. mode=6
0627 21:38:16:394 CTMRJOBWIN2K:OS_FILE_is_reg_file looking in registry for: '.\TEMP\TMP1340163401.cmd'
0627 21:38:16:394 CTMRJOBWIN2K:OS_FILE_close started 00000000006B8400
0627 21:38:16:550 CTMRJOBWIN2K:OS_FILE_close ended
0627 21:38:16:550 CTMRJOBWIN2K:<<<saveCmdLineInTempFile>>> CreateUserProcess enter
0627 21:38:16:550 CTMRJOBWIN2K: CreateProcessAsUser failed with error: 32 - The process cannot access the file because it is being used by another process.

Now these are the temp files that reside in the agent installed folder that the agent uses to work with.
Any idea why they are in use because these generate the OSCOMP 32

There is a user right problem.
Seems that the user that run the process cannot write a file in the temp directory:have you check "log on as user" in the agent configuration?