Mapping with Job Processor when file is released

[Martin-Winkler-Consulting]

I work with Vault Workgroup 2018 and Inventor 2018 (with all updates)
I've set up some synchronizations including the fields Status (History) <> User Status and Revision -> Revisionnumber. To sync, I enabled the JobProcessor. Everything works, except when the file in Vault has got the status Released. Then the JobProcessor does not perform the synchronization and I get the error: Job could not be made ..... File locked.
I have created an extra user for the JobProcessor with all rights. If I understand and read it correctly, the JobProcessor is usually the only way to sync files that have the status Released.
What am I doing wrong?
My mistake also corresponds with this Autodesk article:

 https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

In my case, however, no fields are disabled.

Regards Martin

[JamesMcMullen]

Hello Martin,

I would suggest creating a specific Job Processor user.  This is needed since you will have to give that user read/write/modify permission to your released states.  At this point, the Job Processor will update your properties for you when the Job Processor user is logged into the Job Processor.

Thanks,

Jim

[cbenner]

@JamesMcMullen

According to his first post, it looks like he has already done that.

[JamesMcMullen]

Hi Chris,

I agree.  But, I would like to see the category assigned to "Bauteil B_Standard A.ipt".  Once we have that, we need to see what Lifecycle is associated to that category and that the created user does indeed have the proper permissions to the the "released" state.

-Jim

[Martin-Winkler-Consulting]

@JamesMcMullen @cbenner

thanks for your answers. I made some Screenshots for better understanding my configuration

Here they are:

Regards

Martin

[JamesMcMullen · Accepted solution]

Hi Martin,

Thanks for the detailed pictures.  On your very last picture, you want to select the "Freigegeben" state.  The reason being is that is the state that is having the problem.  Just make sure the "JobServer" user has "Lesen"/"Andern"/"Loschen" permissions in that state.

-Jim

[Martin-Winkler-Consulting]

@JamesMcMullen

Thanks a lot James, now it works. I added the user JobServer a shown below:

Regards Martin