Vault Professional 2017 Job Processor - VaultLicenseMismatchException

[Anonymous]

I am unable to execute any tasks on my 2017 job processor due to a VaultLicenseMismatchException error.

The JobProcessor.log states:

General 21/04/2016 09:31:02
Job 1291297 : Autodesk.Vault.DWF.Create.iam

General 21/04/2016 09:31:02
Exception of type 'Autodesk.Connectivity.WebServices.VaultLicenseMismatchException' was thrown.

General 21/04/2016 09:31:02
The license obtained is incompatible with the server.

General 21/04/2016 09:31:02
DWF Create: Front Loader.iam | Failure

General 21/04/2016 09:31:02
Completed executing

General 21/04/2016 09:31:02

I am running Vault Professional 2017 server build 22.0.56.0. The Job Processor reports the save build number.

I have no customisation, so just running update dwf job.

Server and client are both installed on a Windows 10 workstation. Vault Pro 2017 was upgraded from Vault Pro 2016

The Vault 2017 Client runs fine, so the network license is working and I have available spare licences.

Anyone else having issues with 2017 Job Processor?

Paul Thurgood

vlt systems ltd

[smithmat · Accepted solution]

Would you check if the following registry string value is present and what its value is? 

HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\PLM\Autodesk Vault 22.0\Edition

Once Vault Explorer Professional is installed on the machine, I would expect the registry value to be present and set to Professional.

Thanks,

- Matt

[Anonymous]

Hi Matt,

The Edition in the registry was 'Basic'. Changinng to 'Professional' seems to have resolved the issue.

Many thanks,

Paul

[smithmat]

Ok, good. The way it is supposed to work is that when you install a particular edition of the Client, this registry setting gets set appropriately. I'd only expect 'Basic' to show up if you had installed the Job Processor from the Basic installer.

Regardless, glad you are up and running.

[smithmat]

A colleague of mine pointed out that Job Processor is not included with Vault Basic.  However, if you install Vaul Basic client after having installed Vault Professional (including Job Processor), then this scenario will still occur.  Basically, the last installed client determines what this registry setting is set to and subsequently, what license will be pulled by the Job Processor client.

- Matt