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.
Jeff
Same set up here, domain users for log in and JP user account is vault username not domain, with full admin rights
Client is using Vault 2012 Collaboration + SP1 and Inventor 2011 SP2
From what I can observe JP cannot start up the Inventor session, Inventor.exe doesnt come up
Starting Inventor manually works but very slow. I wonder if there is a timeout value or something.
I might try a re-install of Inventor
Max
Are there any previous versions of Inventor or Inventor view installed on this machine? 2010 and previous? Try uninstalling all old versions of these and repair your installation of 2011. Remember to restart between uninstalls and installs. There may be some sort of registry conflict and you need to clear that out (reset it).
Hello Jeff/Autodesk,
We have the same problems for our JP. We would like to have information from Autodesk.
The only one problem we have is the error "Unknown error during publish" all the time and we are obliged to generate manually the DWF. Not good because as Jeff said, we are Eng. IT for our company and not Eng, troubleshooter or beta tester of Autodesk!
Best regards,
Sylvain
Hello Jeff,
I would like to state that I am in agreement with the statements made. These items need to be made a priority.
thanks,
Just a quick update (after troubleshooting with Autodesk):
1) It seems that if the job processor runs for a continuous amount of time without restarting, the likelyhood of these errors is greater. Restarting the job processor(s) frequently seems to reduce the errors.
2) It may be possible to setup a windows task schedular to handle restarting the job processor automatically. Autodesk is working on more documentation regarding this.
Until Autodesk releases the information, hopefully this will help some of you limp along for a bit. I think this is a bandaid fix to a much larger problem, but for now we can at least get some work done. At this point, it seems as if Autodesk is only addressing the errors and not the lack of performance.
Thank you to those of you who have also posted your concerns.
Helle Jeff,
Thank you for this explanation but I restart the job processor every day (2 times minimum per day). Sometimes it can be done 10 times.
Very annoying to do it even if it takes few minutes.
Sylvain
Just to be clear, I'm talking about a full shutdown of the job processor...not a pause and restart. The close button on the processor window won't shut down the processor, only File>Exit. Why are you restarting the JP 10 times/day? Either way, I agree...having to restart the JP is annoying.
Hi,
I speak about a full shutdown of the computer (virtual machine). Today I did it 3 times for example.
When I see that the JP is blocked on a task, I am obliged to do a remote desktop on the VM, stop the process, restart the computer. Few minutes later, I am obliged to reconnect on it (log in), and at this time, when Windows is loaded, the JP is starting too automatically.
Sylvain
Wow! That's annoying. I wonder if it may be something else, a stability issue with the vm.
I also had problems with a dedicated JP (physical computer on the network). It seemed to work great in the beginning but eventually the performance degraded enough that the JP was barely working.
I've come to the conclusion that all of my problems with JP are processor oriented, and could be solved very easily by Vaule and JP supporting multi threading. As far as I know, this was passed up to the development team through a service ticked logged for me, based on posts here. So it should be taken care of real soon,.... or about the time I retire.
Chris Benner
Inventor Tube & Pipe, Vault Professional
Cad Tips Tricks & Workarounds | Twitter | LinkedIn
Autodesk University Classes:
Going With The Flow with Inventor Tube and Pipe | Increasing The Volume with Inventor Tube and Pipe | Power of the Autodesk Community | Getting to Know You | Inventor Styles & Standards |Managing Properties with Vault Professional | Vault Configuration | Vault - What is it & Why Do I Need It? | A Little Less Talk - Tube & Pipe Demo | Change Orders & Revisions - Vault, Inventor & AutoCAD | Authoring & Publishing Custom Content
All,
We just posted hotfixes for the 2012 and 2013 Vault releases that provide a fix for Job Processor.
A similar hotfix for 2011 is in progress. While these do not address all of the Job Processor issues, it should help to alleviate some of the errors encountered.
Regards,
Hi John
Thanks for the info, will try the hotfix and will post back comments in the coming weeks
Regards
Max Bodnar
Since I have installed VP 2013 (Server and Cleint) locally on my PC all seems to have been working quite well, but I seem to not be able to login to the Job Processor? I know my login credentials are good and I can't really see anything odd that should not make this work.
When I try login to the JP, I get the message 'Unable to Connect to the Job Server. Verify your account settings... etc'. See attachement.
Everything else seems to be working fine with my Vault. I have tried restoring a backup of a blank vault, enabling the job processor and then tried logging in as administrator again, but it still won't let me login to the JP.
I thought I would ask if anyone had any ideas before I resort to doing a full reinstall.
Thanks in advance
Hi Chris,
In the server field, type the name of the ADMS server (instead of the vault name).
Regards,
The Job Processor update for Vault 2011 is now posted.
Regards,
The job processor fixes do not solve the need to restart the job processor nor do they address many of the other concerns in this post.
Jeff,
The hotfix was created to quickly help alleviate some of the errors encountered and was not intended to address all Job Processor issues.
The application is currently being reviewed for a potential, future update.
Regards,
Can't find what you're looking for? Ask the community or share your knowledge.