Skip to main content
D
17-Peridot
Dobi17-Peridot
17-Peridot
December 16, 2024
Question

How to publish a CAD file that triggers a 13032 error?

  • December 16, 2024
  • 2 replies
  • 803 views

Version: Windchill 13.0

 

Use Case: Production system is Windchill 13.0.2.1 and several VMs running a mix of Creo, NX and Office workers. In the recipes I have a worker exit on error code for 13032. Now I have an NX drawing triggering that code... but I still need to publish it. Is there a good process somewhere to work through this error to get a successful publish?


Description:

An NX drawing (NX2312 running on publisher with WGM 13.0.2.0) doesn't publish because of the "worker exists after job on 13032 error" line. What can I do to publish the file via the CAD worker despite this error? 

 

Dobi_0-1734377699191.png

 

2 replies

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
December 16, 2024

What is that error code related to and do you need it?

My system has a different code in there that is in by default, nothing I have entered.

D
17-Peridot
Dobi17-PeridotAuthor
17-Peridot
December 16, 2024

That was a misclick on it being a solution... 😞

 

That error code previously would result in NX disconnecting from the WGM on the CAD worker. I had a PTC tech support call that ultimately resulted in that being in there but we never did figure out what was triggering it. 

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
December 17, 2024

Hi @Dobi 

Try to publish it manually, can you do that? 

 

If you could not find the root case with PTC Support I would escalate the question to someone who really understand the issue. 

Have you tried the Windchill Visualization Services Publishing Troubleshooter, haven't you?

Publishing failure due to error ”worker failed to sync file” 

PetrH

D
17-Peridot
Dobi17-PeridotAuthor
17-Peridot
December 17, 2024

The issue is just with this one file. It opens on any other system just fine and I can save-as PDF. But however it goes to the CAD worker (except ugpublish.bat... haven't tried that), it shuts it down. 

 

Thankfully, since that error is in there, the worker (all three of them) recover and everything goes back to normal. 

Terms & ConditionsCookie settingsAccessibility statement