Cancel in-process publishing job

[gkemner]

How can you cancel a publishing job that is hung up in the "EXECUTING" state? I have stoped and restarted the cad worker but that didn't clear the job out of the Publish Monitor is still shows as "EXECUTING" Windchill Intralink 9.1 M060

Thanks!

[RandyJones]

On 12/13/12 10:53, Kemner, Greg (AS) wrote:
>
> How can you cancel a publishing job that is hung up in the "EXECUTING" state? I have stoped and
> restarted the cad worker but that didn't clear the job out of the Publish Monitor is still shows
> as "EXECUTING" Windchill Intralink 9.1 M060
>
1. From the Publisher Monitor get the Queue Number and the Job
* Queue Numbers will be like L1, L2, M1, M2
* the number part of the name corresponds to the PublisherQueueN (step 3)
2. Start the "Queue Manager"
* Site | Utilities | Queue Manager
3. Find the appropriate PublisherQueueN
* from step 1 queue number
* L1 = PublisherQueue1
4. select View Entries from the "Select Action" menu
5. find the offending Entry (Job from step 1) and select "Show" (or delete) from the "Select
Action" menu
6. change status as needed from the Entry detail

> Thanks!
>

[DanielReid]

I think it is even worse in 10.0 but I have finally figured out a couple
tricks.



Figure out what worker is performing the job and kill just its
"xtop.exe" process. I have put in paths and other labels so that I can
tell which process belongs to which worker. I also use Process Explorer
in tree view to help identify the correct xtop.exe.

Killing that process will Fail the job, after which you can delete it
from the Publish Monitor (WVS Monitor in 10.x).



If the job is still in the process of "downloading" and so doesn't have
a worker running yet, look at the details of the job in the Publish/WVS
Monitor and note the path for the file transfer ("...pubtemp..."). Go
to your Windchill server and delete that folder.

This will interrupt the download process, the worker will get the job
and then fail relatively quickly. This condition takes longer to clear
than the above condition.

[DanielReid]

FYI, this process worked in 9.1 but no longer works in 10.0. I am told
something similar will be brought back in a later version of WC.

[SteveVinyard]

On WC10.0 M030 this method of removing an executing job fails. There is NO way to remove an executing job (hung) consistently that doesn't involve restarting Windchill or hacking at the database.

However in WC10.1 this method of simply removing the clogged item works just fine.

[cid:image001.gif@01CDDD06.68F680E0]

Steve Vinyard
Application Engineer

[BenLoosli]

Is this bug going to be fixed in a newer release of 10.0?

Thank you,

Ben H. Loosli
USEC, INC.

[SteveVinyard]

I think so, in M040 perhaps.

[cid:image001.gif@01CDDD0C.25A0BE90]

Steve Vinyard
Application Engineer

[DanielReid]

Yes, I was told 10.0 M040 and 10.1 M020.



However, it is possible to kill these jobs in 10.0. I sent the details
to someone not long ago but can't find what I wrote now.



The trick is basically to go to your Worker and kill the specific
xtop.exe process that is performing the job. I use Process Explorer in
tree view to help find the right xtop process. I also set up my workers
with individual startup batch files and folders which makes it easy for
me to identify (with Process Explorer in tree view) which xtop goes with
which worker.



Killing xtop specifically will cause the job to fail. Then you can
delete the failed job from the WVS/Publish Monitor. I don't bother
going into the Queue Manager to clear jobs anymore.



If the job is hung up in "downloading" state and so does not have an
"xtop" running yet, you can still kill the job, though it takes a bit
longer to go away. Look at the WVS/Publish monitor and note the path
for the download (it'll be in the tmp/pubtemp folder on your Windchill
server). Go to your server and delete the specific folder for that job.
This will stop the download within several minutes and then when the job
hits the worker, it will quickly fail because files are missing (or
something). Now you have a failed job you can remove from the
WVS/Publish Monitor instead of going into the queues.



I have to do this very often. I couldn't wait for PTC to "fix" the
queue management to handle this.