Skip to main content
Anonymous
April 29, 2011
Question

Windchill publishing does not get files to worker

  • April 29, 2011
  • 9 replies
  • 1715 views

I have Pro/E publishing set up for the first time in Intralink 9.1, but cannot publish any Pro/E model or drawing.
When I click on "Create Default Representation" (where the thumbnail should be) for an EPMDocument, The job fails, and I get the following in the job details:



Apr 29, 2011 1:04:26 PM:The EPMDocument As Stored Config Spec was selected as the default
Apr 29, 2011 1:04:26 PM:make temp dir D:\PTC\Windchill\temp\pubtemp\publish7291880950650252002.tmp
Apr 29, 2011 1:04:26 PM:Start: CAD Part - st88610.prt, A.0
Apr 29, 2011 1:04:26 PM:Authoring Application: Pro/ENGINEER
Apr 29, 2011 1:04:26 PM:empty temp dir: D:\PTC\Windchill\temp\pubtemp\publish7291880950650252002.tmp
Apr 29, 2011 1:04:26 PM:Transferring Files to: D:\PTC\Windchill\temp\pubtemp\publish7291880950650252002.tmp
Apr 29, 2011 1:04:26 PM:Number of Files (identified to be) Transferred: 0
Apr 29, 2011 1:04:26 PM:No content to process
Apr 29, 2011 1:04:26 PM:End: CAD Part - st88610.prt, A.0
Apr 29, 2011 1:04:26 PM:remove temp dir: D:\PTC\Windchill\temp\pubtemp\publish7291880950650252002.tmp
Apr 29, 2011 1:04:26 PM:Publish Complete event dispatched
Apr 29, 2011 1:04:26 PM:End PublishJob (with Error): CAD Part - st88610.prt, A.0


It seems that the Pro/E files are not getting to the worker.


The worker is definately running/started (status=ON).
And I was able to confirm such by taking it offline (temporariliy) and using the "Test Worker" button, which was usccessful.


Gerry

9 replies

crosato1-Visitor
1-Visitor
April 29, 2011

Is your worker on a different box? Are you actually seeing <d:\ptc\windchill\temp\pubtemp\publish7291880950650252002.tmp> make it there?


Anytime we ended up with an issue in publishing CATIA docs it was usually an ftp error as we had the worker on it's own box.

Anonymous
April 29, 2011

More info:
The worker is on the same server as Windchill itself.
I cannot tell if the temp folder is being created because it happens too fast.
The worker is definately writing to the log file D:\PTC\Windchill\temp\pubtemp\PublisherQueue1
Therefore, I doubt there is a permission issue.


Gerry


In Reply to Chris Rosato:



Is your worker on a different box? Are you actually seeing <d:\ptc\windchill\temp\pubtemp\publish7291880950650252002.tmp> make it there?


Anytime we ended up with an issue in publishing CATIA docs it was usually an ftp error as we had the worker on it's own box.


BenLoosli23-Emerald III
23-Emerald III
April 29, 2011
Pro/E Wildfire is installed on the Windchill server?
ProductView Adapter is installed on the Windchill server?
Pro/E worker is pointing to the proper adapter location?
Pro/E worker is started as a service?
Protk.dat has the right .dll file in it?
Adapter.pvi has the right location for the adapter files?


Thank you,

Ben H. Loosli
USEC, INC.
murucbe1-Visitor
1-Visitor
April 29, 2011
Hi,

- Is your WF version compatible with Intralink 9.1 version ?

- Check the trail file for errors from the adapter installation folder.

- It could also be due to license setup

Regards,

Murugesh

On Fri, Apr 29, 2011 at 11:03 PM, Gerry Champoux <-<br/>> wrote:

> More info:
> The worker is on the same server as Windchill itself.
> I cannot tell if the temp folder is being created because it happens too
> fast.
> The worker is definately writing to the log file
> D:\PTC\Windchill\temp\pubtemp\PublisherQueue1
> Therefore, I doubt there is a permission issue.
>
> Gerry
>
> In Reply to Chris Rosato:
>
> Is your worker on a different box? Are you actually seeing
> <d:\ptc\windchill\temp\pubtemp\publish7291880950650252002.tmp> make it
> there?
>
> Anytime we ended up with an issue in publishing CATIA docs it was usually
> an ftp error as we had the worker on it's own box.
>
>
Anonymous
April 29, 2011
Ben,

Yes to all.

The worker is definitely running.
After I start the worker from Windchill, I can see xtop.exe in the task manager on the server.
And the test job (also fired off from within the Windchill browser) worked perfectly.

Take a look at the 2 lines below that I highlighted in red.
It appears that the Pro/E files are not getting sent to the worker.

Note: The example below is of a single part with no dependencies.

Gerry Champoux
Lead Engineer
Information Technology

Williams International
2280 E. West Maple Road
Walled Lake, MI 48390-3828

' (248) 960-2816

7 (248) 960-2607

* -

þ www.williams-int.com <outbind: 123=" www.williams-int.com=">

Anonymous
April 29, 2011
I am using Wildfire 5 (Creo Elements Pro) M070.


The worker test job was successful, confirmed this.


Licenses are fine. Again, the test job confirmed this.


Bill_Kunz1-Visitor
1-Visitor
April 29, 2011
What about your auth.properties file, is it set up correctly?
jmomber12-Amethyst
12-Amethyst
April 29, 2011

Does the user you are using to publish the viewable (from auth.properties) have permission to accessto the object you are trying to publish? I believe I ended up making the user an Organization Admin or something of the sort.


~Jamie

Anonymous
April 29, 2011

Thanks to all that replied, and special thanks to several (like Jamie below) that had the solution.


I was totally unaware of the need for auth.properties, and it did not already exist in my Windchill install folder.
I can't beleive how deep this information was burried in the sys admin guide.



Gerry



In Reply to Jamie Groos:



Does the user you are using to publish the viewable (from auth.properties) have permission to accessto the object you are trying to publish? I believe I ended up making the user an Organization Admin or something of the sort.


Terms & ConditionsAccessibility statement