Do these hit different executables? or run with different processes?
I've found that if I have an issue with a DWF published via jobprocessor it usually updates fine with the update view in Vault Explorer client
I can't answer your question regarding exactly how the JobProcessor runs, but there are known issues with publishing DWFs using the Job Processor.
Unfortunately this means "just waiting for it to be fixed."
Gavin Bath
MFG / CAM Technical Specialist
Design and Motion Blog
Facebook | Twitter | LinkedIn | YouTube
I think the main issue we have with JP is that fact that it uses TrueView rather than the flavor of
CAD that the design files were produced with. We use Civil3d, Autocad Vanilla, Mechanical and Architecture-
each have their slight nuances so I have encouraged users to create a vis file upon checkin as a way to insure
that the DWF is consisent with the state they have left the file.
Express tools, uninitialized layouts, missing plotters and other factors can cause the JP to create an inaccurate
DWF or error out with an 'Unknown error during publish'. I am hopeful they will look at allowing the specific
CAD prog to do the DWF creation in the future but for run of the mill jobs it does work a mjaority of the time once
you understand the limitations.
Interesting. I should have asked but I was just assuming you were having issues with Inventor files as those are the files that I have seen issues in, with JP generated dwfs.
I haven't seen similar issues with AutoCAD files myself.
Gavin Bath
MFG / CAM Technical Specialist
Design and Motion Blog
Facebook | Twitter | LinkedIn | YouTube
I'm having issues with Inventor files not publishing consitently. I'd actually like it if JobProcessor ran the viewer to publish instead of requiring a full license