JOB Server API

[joerituijn]

Hi, I'm trying to create a custom job processor, but it doesn't register properly. I've downloaded the VB sample, but it won't work. This is what I've done;

- Create a folder here: C:\Program Files\Autodesk\Vault Professional 2011\Explorer\Extensions\FolderPublishJobHandler

- Add the dll's to that same folder

- Add the vcet.config file to that folder

- update the C:\Program Files\Autodesk\Vault Professional 2011\Explorer\JobProcessor.exe.config file with:

<jobHandler class="MyCompany.File.Publish" handler="FolderPublishJobHandler.FolderPublishJobHandler, FolderPublishJobHandler"/>

But it won't load. The log file says:

Value cannot be null.Parameter name: key Exception: System.ArgumentNullException: Value cannot be null.Parameter name: key   at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)   at JobProcessor.HandlerManager.LoadHandlerTypes()

[Redmond.D]

In Vault 2011, Job Processor handlers do not go in an Extensions folder.  You put for DLLs in the same folder as JobProcessor.exe.  In your case the folder is C:\Program Files\Autodesk\Vault Professional 2011\Explorer

[Anonymous]

im copying the sample dll into the explorer folder and have added the entry indicated in the code into the handler section of the config. but im getting the same error indicated above.

Value cannot be null.Parameter name: key Exception: System.ArgumentNullException: Value cannot be null.Parameter name: key   at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)   at JobProcessor.HandlerManager.LoadHandlerTypes()

[Redmond.D]

Which version of Vault are you using?

[Anonymous]

same issue VP2012

> mscorlib.dll!System.Collections.Generic.Dictionary<System.Type,Autodesk.Connectivity.JobProcessor.Extensibility.IJobHandler>.FindEntry(System.Type key = null) + 0x14b bytes 

What can be wrong?

[Anonymous]

Found it:

The class "ClassName" at:

  <jobHandler class="ClassName" ...>

doesn't exists.

A little more exception information would be helpful.

But why is this class needed?

The JobServer call the JobHandler.Execute function. So the class "ClassName" is not really needed.

Its really necessary to check if this class exists?