Publishing issue?

[rstav]

I had a user come to me today and ask why he could not view something in ProductView, so I asked for the part number and opened it up myself. ProductView opened successfully but there was not a model in the viewing window. It had all of the information for the part, but no model to manipulate.

So I forced it to publish a new representation and it did the same thing. The thumbnail looks good. When I look into the log everything looks normal.

We are using WC 9.0 M050 and Wildfire 4.0 M120.

I do not remember making any publishing changes to Windchill, so I am pretty sure that it is not Windchill. So it must be the publisher.

Does anyone have any suggestions?

Thanks
Rich

Richard Stavish
Pro/E System Administrator

[cid:image001.jpg@01CB8653.E01C26E0]

E-mail:
Office:
Fax:
Mobile:

RStavish@sargentaerospace.com
520-744-1000 x4570
520-744-7529
520-437-5811

[avillanueva]

Is it possible that the model is off the screen in space, very far away?
Refit the window or highlight the bounded box. See if its in a corner of
the box. If so, check the model for a feature or datum, really far away.
Try also publishing but saving locally or from the client side.

[rstav]

I tried to refit and it did not show up. Then I opened the model in Pro/E and did a save as to a PVS file. I was able to open that PVS file in ProductView and it looked normal.

Richard Stavish
Pro/E System Administrator

[cid:image001.jpg@01CB8659.ACF6FC30]

E-mail:
Office:
Fax:
Mobile:

RStavish@sargentaerospace.com
520-744-1000 x4570
520-744-7529
520-437-5811

[pwilliams-3]

The recipe file for the server publishing may be different from the recipe
file on your local machine. You may want to do a comparison of the two.

PATRICK S WILLIAMS
Information Technology
Mechanical Engr Solutions
Missile Systems
Raytheon Company

+1 520.545.6995 (office)
+1 520.446.0244 (pager)
+1 520.545.6399 (fax)
-

6221 S Palo Verde Rd
Tucson, AZ 85706-5093 USA
www.raytheon.com

Follow Raytheon On




This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this
message in error, please so advise the sender by reply e-mail and delete
this message. Thank you for your cooperation.

[rstav]

Our publisher is an engineering workstation that has been setup to publish CAD models only. I was able to open the model in Pro/Engineer on the publishing machine and create a pvs file from the model and view it in ProductView successfully. I know that I have not made any changes to the recipe file that the publisher is using.

Richard Stavish
Pro/E System Administrator

[cid:image001.jpg@01CB865B.BDD12F60]

E-mail:
Office:
Fax:
Mobile:

RStavish@sargentaerospace.com
520-744-1000 x4570
520-744-7529
520-437-5811

[avillanueva]

Just checking. Saving from Widlfire (Save a copy - Product View) uses
the recipe that comes OOTB. Did you launch Wildfire from the publisher
startup script that gets created along with the CAD worker startup
script. Another thing to look at is the file size of the .ol file that
is created. Compare the two. Scratching my head on this one.

[BobLehman2]

On 11/17/2010 12:46 PM, Villanueva, Antonio wrote:
Richard,
Can you go back into Windhill, delete the representation, force it to
republish and then verify the publish job succeed. If it did look at it
again and see if the viewable looks good. If not send out the
publishing error and we can take a look.

--Bob

> Just checking. Saving from Widlfire (Save a copy -- Product View) uses
> the recipe that comes OOTB. Did you launch Wildfire from the
> publisher startup script that gets created along with the CAD worker
> startup script. Another thing to look at is the file size of the .ol
> file that is created. Compare the two. Scratching my head on this one.
>
> ------------------------------------------------------------------------
>
> *From:*Stavish, Richard [
>
> 6221 S Palo Verde Rd
> Tucson, AZ 85706-5093 USA_
> _www.raytheon.com
> <">http://www.youtube.com/user/raytheoncompany> Facebook
> <">http://www.facebook.com/Raytheon> LinkedIn
> <">http://www.linkedin.com/companies/raytheon> Dual Band podcasts
> <">http://www.raytheon.com/newsroom/podcasts>
>
> Raytheon Sustainability
> /
> This message contains information that may be confidential and
> privileged. Unless you are the addressee (or authorized to receive
> mail for the addressee), you should not use, copy or disclose to
> anyone this message or any information contained in this message. If
> you have received this message in error, please so advise the sender
> by reply e-mail and delete this message. Thank you for your cooperation./
>
> From:
>
>
>
> "Stavish, Richard" <rstavish@sargentaerospace.com>
>
> To:
>
>
>
> "Villanueva, Antonio" <->,
> "-" <->
>
> Date:
>
>
>
> 11/17/2010 01:17 PM
>
> Subject:
>
>
>
> [solutions] - RE: Publishing issue?
>
> -----End Original Message-----

[davehaigh]

Richard,
Go to the information page on the file in I.E. and pick on the folder under the thumbnail, "Display List of Representations". From the Actions menu in the representation list, pick "Save Representation", "Save the Representation as a file", zip/pv/edz.
Look in the zip file to see if you have the required files and if you can open them in productview.

Is is possible that a change in the Oracle database could have lost Windchill's connection to existing files? The content and the content holder could have lost their linkage. You might want to look at TPI 119769, and open a call with PTC.

I suspect it's a Windchill or Oracle problem.

David Haigh

[davehaigh]

One more thing to check, look in the shared folder on the worker, where it does the publishing. Did Windchill move the published files back to the server, or are they still stuck in the folder?

David Haigh

[mlocascio]

That's a good try. One would assume that Product View would center and zoom
in on the part in question. Maybe that's too much to assume..maybe not.



Michael P. Locascio

[rstav]

I tried this suggestion and it did not work.  I am not receiving any publishing error message in any of the logs.  (worker, helper, or monitor)

Richard Stavish
Pro/E System Administrator

[cid:image001.jpg@01CB866E.790E5CA0]

E-mail:
Office:
Fax:
Mobile:

RStavish@sargentaerospace.com
520-744-1000 x4570
520-744-7529
520-437-5811

----------

[leger.xavier.pr]

Hi,

Do you have any replication mechanism of your master vault ? PView files might not be replicated well.

Are you using PView Lite/Prof or Standard ? Are your models solid bodies, or surfaces ?

Trying to help.

Xavier LEGER

[rstav]

Thank you everyone who sent me so many suggestions!!!

PTC Tech support was able to figure out what the heck was happening with my ProductView publishing issue.

Here is the error message that I was receiving in my Background Method server log

PublisherQueue1.PollingThread: wt.pom.DatastoreException: A persistence error occurred. System message follows:
PublisherQueue1.PollingThread: Nested exception is: java.io.IOException: ORA-01691: unable to extend lob segment PDMLINK8.SYS_LOB0000016152C00001$$ by 4096 in tablespace BLOBS
PublisherQueue1.PollingThread:
PublisherQueue1.PollingThread: at oracle.jdbc.driver.DatabaseError.SQLToIOException(DatabaseError.java:517)
PublisherQueue1.PollingThread: at oracle.jdbc.driver.OracleBlobOutputStream.flushBuffer(OracleBlobOutputStream.java:214)

So it looks like I need to revault and that should take care of my issues.

Does anyone have any revaulting advice?

Windchill 9.0 M050

Thanks
Rich

Richard Stavish
Pro/E System Administrator

[cid:image001.jpg@01CB8BE9.11D25930]

E-mail:
Office:
Fax:
Mobile:

RStavish@sargentaerospace.com
520-744-1000 x4570
520-744-7529
520-437-5811

[sdrzewiczewski]

Are you not externally vaulting your data? If so I would recommend not storing the vaulted data as blobs in the database.

Steve D.

[patrick.chin1]

1. For issues of successful publish and blank viewables for models and assemblies. Drawings come out fine. The tesselation required entities enabled in the proe2pv.rcp file.The fact is that tesselation are now required to enabled to have transparencies to be converted and solid geometry to publish with the thumbnail inlatest versions of the publishing adapters.
2. Regarding the error: unable to extend lob segment... by 4096 in tablespace BLOBS.

• I advise to have free space in your oracle tablespaces. You should have at least 70% free space at a time so that you don't have to rely on oracle auto extending. This way you have ample time before it starts to autoextend and causes issues. Oracle auto extending is great way for less DBA maintenance, but Windchill doesn't wait for the extension of free space. So, it sometimes produces this error.
• Another possible issue is to just increase the extents of of your entire system.
  • do this on a test windchill system first ormake sure you have a backup of Windchil
  • Add this to your site.xconf

<property name="wt.generation.sql.tinyBlobSize" overridable="true"&lt;br"/> targetFile="codebase/user.properties"
value="32k"/>
<property name="wt.generation.sql.smallBlobSize" overridable="true"&lt;br"/> targetFile="codebase/user.properties"
value="32k"/>

• In windchill shell run xconfmanger -p
• In a windchill shell run $WT_HOME/bin/JavaGen.sh registry false false true false false
• Restart Windchill

Good luck,

Patrick

[patrick.chin1]

If you want to constantly externally vault:

• If you have ever exported your oracle dump, check thesize. If oracle uses compression, you better make sure you have tons of diskspace in yourvaultor have extramounted folders with free space.
• This may take a while, and make sure you do this first on a mirrored test system first to see how much space you actually needed on your production system.
• modify your $WT_HOME/site.xconf to add the following line:

<property name="wt.fv.forceContentToVault" overridable="true"&lt;br"/> targetFile="codebase/wt.properties"
value="true"/>

• in a Windchill shell run the command xconfmanager -p and restart windchill
• In Windchill External Storage Manager, select your host, vault and then perform a revault.

Good luck