Creo View Lite fails to open files

[ptc-5163001]

Thanks in advance for any helpful recommendations.

We recently upgraded Product View to Creo View Lite 2.0, datecode M040 build 15.

This has not been a good experience.

Many of our drawings will not open to be viewd and printed, and many means an everyday event.

The files that fail are "EPM: As Stored xxxxxx.dxf".

It appears that we may not have all the needed adapters in place, because there is no adapter (.inf) for a dxf.

Looking in: C:\Program Files\PTC\Creo 2.0\View\Adapters

Is there an adapter required?

In the Options Drawing Viewer DXF-DWG a path statement for SHX exists as such: $PVIEW_HOME.i486_nt/realdwg/Fonts

Are more parameters required?

Does anyone have experience with this also?

If so what is the solution you have discovered?

[shussaini]

Mark,

Try the following:

• Update graphic card driver to latest version.
• Check if the platform is certified. You can refer the software matrices for Creo View adapters.
• Check If it is a file specific issue.

Hope that helps.

Regards
~Syed

[ptc-5163001 · Accepted solution]

Syed, thanks for your input.

A fellow worker nearly 500 miles away sent me an email with a solution regarding Re-Publishing and broken links:

Re-Publish a Creo View Drawing

When you enter a drawing number then select the Creo View Icon and get a blank white screen, close the page.

1. Select the Content Tab at the top of the page.

2. In the Representations/Annotations section of the page, select the far left pick box alongside the default radio button.

3. Select the Action pull down, then select Delete Selected.

4. Click OK on the Message from webpage dialog box, at this time the old publication will be deleted.

5. Select the Details tab.

6. Select the refresh arrow at the top of the browser page.

7. After the refresh the icon will change to resemble printing rolls.

8. Select the icon, this sends the drawing to the publisher.

9. A new Creo View Browser page will open, close this page.

Pending on the size of the drawing and how many Publication Requests are in the queue, the time will vary, so be patient.

This did solve the problem, but its very cumberson and SLOW.

We have many users out in the field that cannot be burdened with this time consuming task.