Error in Job processor

[Johan_Degreef]

This morning, these message start appearing. no changes done to ADMS in the last month...

Trying to log on with these job processor credential work fine.

[ihayesjr]

Can you supply your Vault Server logs for review?

[Johan_Degreef]

Log is attached. Thx for helping

[ihayesjr]

Please share the file store and console logs.

What is the INOPSYS database? Is that a Vault? Why did it go offline in the middle of the day?

[Johan_Degreef]

INOPSYS is our Vault.

I restarted the server because I tried to solve the error. Just at restart.

Attached both logs

[ihayesjr]

When you resubmit the Jobs, do they finish successfully?

[Johan_Degreef]

Yes they did partly. Another resubmit and they were all processed. But don't know when they did and did not.

[ihayesjr]

Do your Job Processors log into the Vault Server using a Vault account?

I am concerned with what I see in your logs.

Exception: AutodeskUserNotFound [8011]

The remote server returned an error: (429) Too Many Requests.

[Johan_Degreef]

It does log in with Autodesk ID

I have a Vault user configured for job processor, but Autodesk ID is active.

[ihayesjr]

Just so I am clear, you have an account profile for the Job Processor that allows it to log in using the Vault account and Autodesk ID authentication methods?

[Johan_Degreef]

Yes.

And it has been working flawless for a few months now.

[ihayesjr]

Which Authentication is it using to log into Vault?

[Johan_Degreef]

Autodesk id 

[ihayesjr · Accepted solution]

Don't have the Job Processor log in with the Autodesk ID if it is running on a dedicated machine. 

This may be the cause of the problem.

[Johan_Degreef]

Autodesk id

[Johan_Degreef]

OK, I changed it to Vault account. Let's evaluate.

Thank you

[Johan_Degreef]

OK, It seems to be working again, but was running also fine for monts with Autodesk ID. Now on Vault Account.

Thx, Johan

[ihayesjr · Accepted solution]

Vault is licensed using the Autodesk ID refreshing it license when the Thick Client or an add-in is launched on that machine. Launching the Job Processor does not refresh the license and therefore expires after 30 days. This is what I think happened causing the error. Within the next 30 days, you will need to log into this machine and refresh the license or it may happen again.