Skip to main content
J
jweaver1-Visitor
1-Visitor
April 4, 2014
Solved

Parametric.exe will not run

  • April 4, 2014
  • 4 replies
  • 22934 views

We just recently updated to Creo 2.0 M100 from M070 and ran into one problem. When you try an run the parametric.exe in the bin directory nothing happens. Same for simulate.exe and creosysmon.exe. Unless I'm mistaken, running the executable should give you the option of choosing all the psf files that you had created when installing the software. I believe that for each psf file it also creates a batch file that runs the executable with the psf and skips the list. Running those batch files directly do work.

 

I've been working with PTC on this and the only solution they gave me was uninstall everything and start fresh. Since this is a server install with multiple users running Creo from it, that is not a convenient way of troubleshooting this.

 

Has anyone else run into this issue?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by jweaver

I believe I have solved the issue. The aps_ui_default_resources.dll in PTC\Creo 2.0\Parametric\text\complied_resources directory was not updated when going from M070 to M100. I replaced the dll with one from a working install and everything seems to be running like it should.

4 replies

Mahesh_Sharma
Mahesh_Sharma22-Sapphire I
22-Sapphire I
April 4, 2014

Hi Justin,

Possibly this is due to incomplete installation of Creo Parametric, look for xtop.exe in <Install Location>\Creo 2.0\Common Files\M100\x86e_win64\obj. If it is not available, uninstall and reinstall Creo 2.0

I hope this will help you.

J
jweaver1-VisitorAuthor
1-Visitor
April 4, 2014

xtop.exe is there. I did run the program Beyond Compare on that install compared to another install that is working and all the files in the working one DO show up in the one that is having issues as well.

This makes me think that a file may have not been correctly updated when going to M100?

Mahesh_Sharma
Mahesh_Sharma22-Sapphire I
22-Sapphire I
April 4, 2014

As it is not starting with parameteric.exe, can you make a try with parametric.bat. Sometimes .exe’s may fail to start but works well with batch files.

J
jweaver1-VisitorAuthorAnswer
1-Visitor
April 7, 2014

I believe I have solved the issue. The aps_ui_default_resources.dll in PTC\Creo 2.0\Parametric\text\complied_resources directory was not updated when going from M070 to M100. I replaced the dll with one from a working install and everything seems to be running like it should.

J
jferreira-21-Visitor
1-Visitor
January 12, 2015

I've changed that file you mentioned "aps_ui_default_resources" and I've already reinstalled several times all the PTC products and still can't get Parametric started via .exe.

Is there any other solution besides changing the shortcut from .exe to .bat ?

Thanks

M
MartinHanak24-Ruby III
24-Ruby III
January 12, 2015

Jorge,

you can launch Creo 2.0 using parametric.bat and you are not able to launch Creo 2.0 using parametric.exe ?

It's strange because parametric.bat is calling parametric.exe.

Marin Hanak

    J
    jferreira-21-Visitor
    1-Visitor
    January 12, 2015

    In this case it's the Creo 3.0 M020, but yes, that's what happens.

    Maybe it's missing its argument "parametric.psf" ?

    S
    STEVEG21-Topaz I
    21-Topaz I
    April 2, 2015

    Just for your information...we had trouble running Creo 2 builds M080 - M110 on computers with an integrated graphics card. Build M120 fixed it for us.

    Terms & ConditionsAccessibility statement