Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

I HATE THE JOB PROCESSOR!

75 REPLIES 75
Reply
Message 1 of 76
jeff_jordan
9276 Views, 75 Replies

I HATE THE JOB PROCESSOR!

I can't get any more straight forward than that without being vulgar.  But I really can't stand how the job processor works.  And now it's NOT working.  It won't update my vault revision tables anymore and we are getting errors like "A visualization file cannot be generated for a non CAD file" when it's a bleeping .ipt!  And this all happened during a very important demonstration.

 

Vault Professional is a JOKE.

Autodesk Product Design Suite Ultimate 2015 (Inventor 2015 Pro SP1, Vault 2015 Pro Update 1)
MacbookPro OSx 10.9, Boot Camp
Windows 7, 64-bit
Intel Core i7 2.6 GHz
16GB
SSDs
NVIDIA GeForce GT 750M with 2GB of GDDR5
75 REPLIES 75
Message 41 of 76
Maarten65
in reply to: jeff_jordan

I recognize 95% of you have described. In europe we have 4 countries using one database and use 5 jobservers (1 for every country and 2 for Netherlands --> VMs) to get the work done. (+/- 50 engineers)

Our company, Parker Hannifin has a Platinum contract (global) with Autodesk. All Autodesk products can be used unlimited. So licenses are not an issue for us. BUT we still have big problems with job servers.

The message

a visualization file cannot be generated for a non cad file.

is something I am working on today. We recieve it once every 3,4 months. Till now we have no idea why.

Reregister inventor sometimes helps. Updating with a SP sometimes helps....  😞

 I asked for a priority of tasks for the job server as well. dwf should be made during the night (so time planning should be possible.)

After creating a new version by the jobserver, the remarks placed by the engineer in the field comment are 'lost'. (We place the text 'To be checked by xxx" when the state = For Review. A user can search on this in order to know what he has to check this day. But an update of teh title block by the jobserver creates a new version and we can not search on this info anymore. 😞

 

 

 

Maarten Weers
Technical Specialist CAD - EMEA
Parker Hannifin
Oldenzaal - The Netherlands
-------------------------------------------------------------------------------------------
Inventor Pro 2019 - Vault Professional 2019 - Windows 10 64 bit -
Message 42 of 76
sbenedum
in reply to: Maarten65

Has anyone set up the Job Processor to run on a Virtual Machine?

 

We have two job processors running, one on an old XP CAD workstation and another on a VM in our server cluster. Aside from the usual (and frequent) issues with the job processor the VM one hangs up on several times a day and the only way to get it going again is to kill the Inventor process. This requires someone to constantly monitor this VM which is not something we enjoy doing.

It appears that Inventor (apprenticeserver) max's out the memory which is what is causing Inventor to hang up, not surprisingly. 

 

So I'm wondering if anyone else has successfully set up the Job Processor on a VM, and if so how did they configure it? 

 

Thanks,

Sailin Benedum
Message 43 of 76
adeburie
in reply to: sbenedum

sbenedum,

What release of Vault are you using?

 

If 2013 Professional, the following work-around may help. You could use the JobProcessor.exe command line arguments, in combination with a scheduled task+powershell, to restart JobProcessor.exe every few hours on the VM.

 

# === powershell.ps1 script ===

& "C:\Program Files\Autodesk\Vault Professional 2013\Explorer\JobProcessor.exe" /stop
Wait-Process JobProcessor
& "C:\Program Files\Autodesk\Vault Professional 2013\Explorer\JobProcessor.exe"

# === powershell.ps1 script ===

 

The /stop command will finish the current job then exit the JobProcessor (releasing Inventor's resources).

 

If you are using a different verison of Inventor, let me know; there may be other options to try.

 

-- Alex

 

 

Tags (2)
Message 44 of 76
VinceBalge
in reply to: jeff_jordan

We use Job Processor to handle DWF creation for 15 users. sometimes more than a 1000 files a day. Yes it has been problematic at times.

The error "a visualization file cannot be generated for a non cad file" had me frustated until I tracked it down to our anti-virus software (ESET). Since adding all Autodesk software to the Excluded applications list that error has stopped.

 

Vince B

Inventor Pro 2013 / Vault Pro 2013

Message 45 of 76
Mark_Wigan
in reply to: jeff_jordan

thanks jeff (& others) for your post. i aggree with your ideas and comments.

 

we are just implementing vault collaboration in the past few months and having some of these issues.

 

i have had some serious crashing of inventor while running JP on my workstation & trying to work at the same time in inventor. these were not just a normal inventor crash though, as i later discovered that all my addins were broken, had to try to repair / reinstall inventor and so on. (that is another story).

 

during the process though i posted some thoughts on the (vault and inventor) ideas forum about having some improved functionality of the job processor. i just wanted to note it again here for the ability of Autodesk to consolidate everyone's feedback while they "hopefully" put the resources into this thing to get it working properly.

 

maybe it wouldn't be as bad if we were all using a free program and trying to develop a new piece of software together but this is an expensive piece of software that a massive organisation has developed, (pitched as something great) that our buisinesses rely on it to run efficiently, but this JP runs like it came out of a breakfast serial packet.

 

very dissapointing.

 

 

best regards,
- Mark

(Kudo or Tag if helpful - in case it also helps others)

PDSU 2020 Windows 10, 64bit.

Message 46 of 76
jddrinkwater
in reply to: Mark_Wigan

I have had my own issues with JP (hanging and crashing).  I am using physical PCs, I don't have experience with VMs.  

 

In my troubles I've discovered 2 tricks:

 

#1 - if you have 2 (or more) PCs available to run the JP, configure them so that one machine does only dwfs for IDW/DWG and the other machine does all other tasks.  What i've discovered is that at least 80% of the hangs can be eliminated when it isn't switching between drawings and assemblies/sync properties/etc.

 

#2 - the job processor (inventor) seems to operate single threaded, but you can trick it into utilizing multiple cores on your PC by logging in under multiple user names.  Each windows account can run it's own copy of the JP.  I recently had to generate several thousand DWFs.  By having all the engineers log in to our CFD/rendering computer, we utilized al 8 cores and cranked the DWFs out in under a day.

 

#3 - I don't like that these hacks were necessary to make the program run smoothly.  It is also an annoyance that the JP consumes a license.  If the JP gets backed up i have 2 options: have the engineers wait for files to get slowly processed, or ask engineers to log off vault so that i can start more JPs and process the excess files.

Message 47 of 76
mbodnar
in reply to: jeff_jordan

I was hoping that the JP processor improvements in 2014 were here to help but not so sure

I would appreciate any feedback/help on this

 

I left JP with default settings. Submitted approx 100 for DWF update

 

After about 20, Job Queue is showing processing. An hour later still processing on that object

 

It's not file specific as I kill the JP and restart it and it does 2 more files tha it hangs again

 

I also noticed a new error to add to the others that JP likes to throw

"The new job processor is not responding" 

 

The JP log does not help much, it shows it's still executing

 

General 23/05/2013 3:03:21 PM
-------Job 557 Autodesk.Vault.DWF.Create.idw : DWF Create: 3172_BARREL ASSEMBLY.idw-------
            
General 23/05/2013 3:03:21 PM
Started executing

 

I am trying to like the JP but it's not liking me. Maybe it's personal

 

Max Bodnar

Message 48 of 76
VinceBalge
in reply to: jeff_jordan

Look at your anti virus program. We were getting the same error message. Our ESET anti Virus was the culprit. When I excluded Autodesk products in Protocol filtering the problem stopped. Some days I'll see more than a 1000 files processed. Large assembly drawings that are not resolved properly can be a problem.

 

Vince Balge

ATCOEM

Vault Pro 2013

Tags (2)
Message 49 of 76
mbodnar
in reply to: VinceBalge

Hi Vince

Thanks for the reply. I had suspected that the antivirus might be the issue (running TrendMicro) as it has already blocked some of the installs.

I tested on machine without antivirus and JP still hung after about 10 files. Will double check again

Cheers
Max Bodnar
Message 50 of 76
mbodnar
in reply to: VinceBalge

One more question please did you exclude any particular *.exe processes or all Autodesk products/programs?

Max
Message 51 of 76
VinceBalge
in reply to: VinceBalge

Hi Max;

Try updating the problem file locally from Vault. If it's a problem with the file its self you'll get an error message.
[cid:image001.png@01CE5793.F55795D0]

Vince Balge
Supervisor Design Drafting
ATCO Emissions Management
260 Holiday Inn Dr. Unit #1 Cambridge, ON N3C 4E8

T: 519-220-0600 Ext 239 | C: 519-212-8098
E-mail: vince.balge@atcoem.com
www.atcoem.com

The information transmitted is intended only for the addressee and may contain confidential, proprietary and/or privileged material. Any unauthorized review, distribution or other use or the taking of any action in reliance upon this information is prohibited. If you receive this in error, please contact the sender and delete or destroy this message and any copies.
Message 52 of 76
mbodnar
in reply to: VinceBalge

No issue updating the local file using Vault update

 

I keep getting this message in the Job Processor log file, though

 

General 24/05/2013 11:02:26 AM
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
            
General 24/05/2013 11:02:26 AM
The JobProcessor.Delegate process is not responding.
            
General 24/05/2013 11:02:26 AM
Reset Connectivity.JobProcessor.Delegate.Host
            
General 24/05/2013 11:05:42 AM
Job Processor exited
            
General 24/05/2013 11:05:42 AM
--------------------------------

 

Antivirus is turned off but issue still continues. Will try with exceptions added

 

Regards

Max Bodnar

Message 53 of 76
sbenedum
in reply to: adeburie


@adeburie wrote:

sbenedum,

What release of Vault are you using?

 

If 2013 Professional, the following work-around may help. You could use the JobProcessor.exe command line arguments, in combination with a scheduled task+powershell, to restart JobProcessor.exe every few hours on the VM.

 

# === powershell.ps1 script ===

& "C:\Program Files\Autodesk\Vault Professional 2013\Explorer\JobProcessor.exe" /stop
Wait-Process JobProcessor
& "C:\Program Files\Autodesk\Vault Professional 2013\Explorer\JobProcessor.exe"

# === powershell.ps1 script ===

 

The /stop command will finish the current job then exit the JobProcessor (releasing Inventor's resources).

 

If you are using a different verison of Inventor, let me know; there may be other options to try.

 

-- Alex

 

 


Alex,

This is a good idea but unfortunately doesn't work.

If you try to run the JP from the command line with that arg it compalines that it is allready running.

Unless you were able to get this to work another way???

 

Thanks,

Sailin Benedum
Message 54 of 76
sbenedum
in reply to: sbenedum

I'm trying to do this with 2011...

 

Sailin Benedum
Message 55 of 76
adeburie
in reply to: mbodnar

Max,

This error indicates that the new, second part of the job processor (the executable Connectivity.JobProcessor.Delegate.Host.exe) is either not responding or not currently running. Here's some things to look for:

 

1. Try shutting down Connectivity.JobProcessor.Delegate.Host.exe and the JobProcessor.exe applications. You can do this via Windows Task Manager.

 

2. Restart the JobProcessor.exe - this should automatically start the Connectivity.JobProcessor.Delegate.Host.exe. (If not, it's possible there is a configuration issue. Take a look for the most recent {GUID}JobProcessor.log file in C:\Program Files\Autodesk\Vault Professional 2014\Explorer\ - you will see files like "00e5b402-068c-4173-9dcc-178e10a7e663JobProcessor.log", or "36dd3297-b435-4901-89a5-8fe8405cd211JobProcessor.log". The one with the newest date/time will be the one you want to look at.

 

3. Please remember, if ever manually shutting down the JobProcessor.exe, to also shut down Connectivity.JobProcessor.Delegate.Host.exe.

 

-- Alex

 

Message 56 of 76
adeburie
in reply to: sbenedum

Sailin,

The command line switches I was referring to are only available in Vault 2013 and greater.

 

-- Alex

 

Message 57 of 76
mbodnar
in reply to: VinceBalge

Hi Alex

 

Thanks for the info. Autodesk identified the issue as a potential bug and has provided me with a custom job handler in the meantime as a workaround. Apparently this will be resolved in the service pack. Seems to be working OK for the time being

 

 

Thanks

Max Bodnar

Message 58 of 76
adeburie
in reply to: mbodnar

Max,

Please note the new version of the JobProcessor is actually two applications: JobProcessor.exe and Connectivity.JobProcessor.Delegate.Host.exe. The message indicates that the main processor (JobProcessor.exe) is unable to communicate with the child process (Connectivity.JobProcessor.Delegate.Host.exe).

 

You may want to try shutting down both processes and restarting the JobProcessor.exe (which will auto-start the Connectivity.JobProcessor.Delegate.Host.exe application by itself).

 

If the Connectivity.JobProcessor.Delegate.Host.exe fails to start, you may need to refer to it's log files, which are located in the same folder as JobProcessor.log, but have filenames that look like this: "11c741f9-d5f7-4595-b343-9e29bbbcd62dJobProcessor.log" - the one with the newest date will be the one you want to check out.

 

-- Alex

 

Message 59 of 76
cmclean
in reply to: jeff_jordan

To Jeff and all other contributers to this post.

 

This post brought me close to tears as I too have been suffering from the curse of the JP following an upgrade from 2012 to 2013. However, I must say a HUGE thank you to each and everyone of you who have so expertly described the problems you have encountered but more importantly how you overcame these issues. They have enabled me to reduce the number of errors from 10 down to 2 (to which I am awaiting feedback from Autodesk) in the space of a week.

 

The biggest issue I had encountered was a file hanging/freezing during the processing (this was one I couldn't see an answer for within the post). Autodesk contacted me last week (8th Nov) to talk me through how to clear the frozen file which is very handy as I've now unfrozen & deleted 2 files this morning!

 

To unfreeze the file so that you can remove it from the job queue you will need to launch the Task Manager and right click on the Inventor.exe file and then select the 'End Process Tree' command. This will kill Inventor and thus end the process fo rth efile that is frozen. You then go back to your job queue and remove the offending file.

 

By the way, Autodesk did not offer up a reason as to why this occurs so I'm at a loss on how it can be prevented.

 

The JP is running on my workstation and logged in as Job Server, two other system administrators have JP but until I have resolved all the erros they have been de-activated.

 

Thank you all once again

 

Colin

 

Product Design Suite Premium, Ultimate & Factory Design Suite Premium plus Vault Workgroup

Windows 7 64-bit

Intel(R) Xeon(R) CPU 3.05GHz

24GB RAM

NVIDIA Quadro 4000 graphics card

Message 60 of 76
cbenner
in reply to: cmclean

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report