I loaded several jobs in the Queue this last week and expected them to be completed. Upon checking this morning apparently they all failed. Is there a place I can view why they failed?
I loaded several jobs in the Queue this last week and expected them to be completed. Upon checking this morning apparently they all failed. Is there a place I can view why they failed?
Are you running Windows 10 or Windows 7 Chris? One thing I do that helped reduce the same problem for me, but not stop it completely though, was to suspend Windows 10 updates.
At the tab to manage updates in Windows 10, under advanced, there is a spot where you can suspend updates for up to 20 days. Before I fire off the queue that I know is going to run for days, I suspend the updates so they won't do something to interfere with the PC's processing.
If I were running Windows 7, I would turn off auto updates during a time I would need to run the queue for days.
Like I said, doing that has helped but not completely eliminated that issue for me.
Thanks for the comment, will try that out!
I restarted my computer and the render Queue gave this reason.
Solution Id:S-074366
Question:When using the Queue with SOLIDWORKS® Visualize, why do I see the following error? ‘Unable to connect to local queue. Make sure the service is running and try again.’
This issue can occur if a system failure interrupts the SOLIDWORKS® Visualize Queue. Any subsequent renders will try to restore previous sessions, which could have been corrupted by the crash.
Answer:
To clear any previous sessions and restart the Queue, follow these steps:
1. Stop the Queue service.
a. Go to 'Control Panel' > 'Administrative Tools' > 'View local services'.
b. Right-click on the ‘SWVisualize[version].QueueServer’ service > ‘Stop’.
2. Delete the following files:
• %PROGRAMDATA%\SOLIDWORKS\SOLIDWORKS Visualize [version]\Queue\admin\processorscheduler.state
• %PROGRAMDATA%\SOLIDWORKS\SOLIDWORKS Visualize [version]\Queue\admin\queue.state
3. Restart the Queue service.
a. Go to 'Control Panel' > 'Administrative Tools' > 'View local services'
b. Right-click on the ‘SWVisualize[version].QueueServer’ service > ‘Start’.
Ok had an idea. I think the render Queue is timing out because of the large file. I think if I change the render Queue timeout to a much larger number I should be fine. How do I stop the queue in order to do that? The queue is not open, I have tried several times to stop and close it but I keep getting an error message. Thoughts?
As I PM'd you, we'll need to see the logs. Please pass them on through PM.
To stop the queue, in your start menu, type "services" to launch the Windows Services tool.
Something like the following. You can right click and choose Restart.
Ok I tried that. However the service status shows not started and Starting it gives me this error. Also Render Queue is open and running.
Reboot. Then try to restart the service once windows is back up.
Tried that. Still giving the same error message.
I ran Queue as admin and I was able to stop it. Increased the render timeout and will see if that solves the issue now.
I have the same problem in 2018 version.
Queue render some jobs and then returned a "Job Failed" error for rest of jobs.
I attached the log files.
Make sure you have the approved GPU driver installed and disable the auto update feature for GPU driver.
There is no GPU on my system.
You don't have a graphics card?
No i don't.
Abdollah Taheri Ledari wrote:
No i don't.
Wow! I never saw a computer run without a graphics card! Cool!
Just out of curiosity can you open device manager (click start and type device manager and hit enter). Then twirl down display adapter and screen shot for us.
There's no smoking guns in general and no way to even get a clue without seeing log files from:
C:\ProgramData\SOLIDWORKS\SOLIDWORKS Visualize 2018\Log
Perhaps Abdollah can .zip them up and attach here.
Ron
There's some TCP/IP port failures trying to launch offlinerender and offlinerenderconsole (the processes responsible for running the jobs). Unfortunately I can't see why.
Do you experience the same frequency and ease of failed jobs, after a reboot?
Do you have an anti-virus running?
This seems to happen over the weekends. Any suggestions or thoughts?