Task Scheduler 2006 - Upgrade required?

Nov 24, 2006 5 Replies

Hi all, I have TSched2006 SP0.0. I no longer have the service agreement with my SW provider. As murphy would have it as soon as you stop paying for the service/mainteance, something goes wrong. I have worked around this problem up till now, but really need to use TS now.



The problem is that I scheduler a bunch of .slddwg's to be exported to .dxf. The scheduled task just sits there and does not start running.



From the discussions I have had with support, it has something to do

with the engine not starting and requires the next service pack upgrade.


Anyone else had his problem or got any ideas on how to fix this? Don't say to get service/maintenance contract :p


Cheers, Chris.

I was under the belief that SolidWorks would give you the SP needed, for a specific fix, without being on maintenance.

But if that doesn't work, I'd recommend PAC4SWX it will do batch conversions to DXF and quite a bit more. I personally prefer this utility to printing with the Task Scheduler.

John Layne

formatting link

I read this on another issue and so I sent an email asking my VAR. I never got an answer back but only the question of what was my current Version and SP. I replied and they sent me a link that gave me the update. But, they never did answer the question as to if SP's are available without being on maintenance.... Seems like if this is the policy that SW and the VAR's should just be honest and say so.

Yet another reason why I believe that the Technical half of SW works very hard but perhaps the Marketing group, (whoever has come up with so many of these bad policies that are bad for the users and also for SW) should be replaced. BTW, I changed VAR's... :-)

Edt

Thanks John and Ed,

I will give PAC4SWX a go. As for batch printing I have been using SWBatchPrint by Vinodh Kumar.

Thanks again, Chris.

What I've found to be the problem when this happens, is it's usually caused by the file 'swBOEngine.exe' not running BEFORE you run your batch.

I've found that even if you try to run 'swBOEngine.exe' AFTER you have already run your batch, it still won't work.

You need to cancel your batch and run 'swBOEngine.exe' before starting up Task Scheduler.

One thing you can do, to make sure 'swBOEngine.exe' is running before you run Task Scheduler is, put 'swBOEngine.exe' in your 'Startup' group. that way it will always be running. Unless of course you were to kill the process. Then 'swBOEngine.exe' would need to be restarted.

Richard

Richard,

Thankyou. It works!!

Much appreciated, Chris.

Richard Charney wrote:

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required