Skip to main content
M
msteffke15-Moonstone
15-Moonstone
May 24, 2017
Question

Creo Agent

  • May 24, 2017
  • 9 replies
  • 6942 views

Trying to install Creo3 m130.  Nothing but creo agent errors on the two that I've done.   Looks like this has been going on in the Creo world for a couple years.

So the solution is to jerry rig the install by setting creo_agent_exe_path?     This seems like a simple to fix, should PTC not simply fix the install?

I have concerns about this.  What about my current production Creo Elements pro version that still needs to be running?   Will this need to change with every install?

Am I submitting to a lifetime of babysitting this env variable for 150 people?

9 replies

M
msteffke15-MoonstoneAuthor
15-Moonstone
May 25, 2017

No Takers?    I do a search and find pages of people fighting this.    The advertised solution does not seem to work so well.

D
davehaigh13-Aquamarine
13-Aquamarine
May 25, 2017

No problems here.

CS104032 states the only reason you would have to set the environment variable is if you are running Creo from a network share.

From previous discussions with PTC you can't put that specific variable in the startup script. It has to be added to the client machine. And again this is only applicable if your running Creo from a network share. Your screen shots indicate you are not doing that.

You shouldn't need to do anything. It should just run. M130 works for me using the same install path you show. Installed on a clean VM in Windows 7. I made a shortcut on the desktop of parametric.exe and set the start in folder to the desktop.

If you do need to install an environment variable, you could add it to your install script using the setx command, you'll need to look up the syntax. I used this to prevent the windchill workgroup manager from auto registering Mathcad.

setx UWGM_SKIP_AUTOREGISTRY TRUE /m

Terms & ConditionsAccessibility statement