We moved from Creo 2.0 to Creo 4.0 M040 (shared over the network) in March this year and I had the same trouble with the creoagent. What helped was the admin guide (see below) - all the CS confused me. I have "\\" the environment entry ENV=CREO_AGENT_EXE_PATH I used before for Creo 2.0 and CREO_AGENT_LDP_LIST in the parametric.psf. And updated created.reg from the installation on the server:
<creo_loadpoint>\<datecode>\<app_name>\bin\pim\xml\created.reg. The created.reg is given with a silent installation to the clients "regedit /s created.reg". Our IT is using a Microsoft software distribution for this.
Bevore on the server I shared \\servername\creoapplication and connected drive letter i.e. "D:" to the share "net use 😧 \\servername\creoapplication". So the load point for all user is D:\PTC to which they are connected. Then I installed all the Creo applications to D:\PTC. The Agent and the Platform Services are installed then to there default location - in this example to D:\PTC\Creo. The environment variables are not needed in this case. The share, registry, net use and installation is taken/adapted from the former Creo 2.0 approach. New is the Installation of the Platform Agent along with the Creo Agent which is to a different location than for Creo 2.0 and not using the ENV's in the .psf file.
from the "Creo® Installation and Administration Guide" page 53:
If you access Creo applications from a shared location across the network, you do
not need to install Creo Platform Services on your client machine.
If a Creo installation on a custom location (For Example, D:\PTC), is relocated to
a network drive (For Example, D:\PTC is exported as \\SERVER\CREO4_
Share\), then Creo automatically finds the creoagent executable file relative to
the install location.
Creo does not require the environmental variable CREO_AGENT_EXE_PATH to
find the path of creoagent.exe.
However, if the Creo installation structure in the network location is different
from the default one, then the environmental variable CREO_AGENT_EXE_PATH
must point to the file creoagent.exe.
The environment variable, CREO_AGENT_LDP_LIST must also be set and must
point to the manifests folder on the Platform location. (For Example,
\\SERVER\CREO4_Share\Creo\Platform\4\manifests).
For local installation, the above environmental variables are not used.
If Creo is started from a network install and Creo Platform Services package
(creoagent.exe and Creo platform) is installed locally and the environmental
variables are not set, local installation takes precedence even if Creo finds the
network installation. Using environmental variables, you can change the order of
lookups.
Regards
Jan
... what came in mind after posting the above: The file location of the creoagent.exe in the Windows task manager is given with this path "\\server\share\ptc\Creo\Agent". May be one has to use UNC instead of drive letter for the ENV's. Also in March (see above) I had local old installations of creoagent and I still have them. I assume, this could have been the problem then, if the syntax of the environment settings in the parametric.psf might have been wrong (drive letter instead of UNC) if PTC has changed this from CREO 2.0 to 4.0?
"...If Creo is started from a network install and Creo Platform Services package
(creoagent.exe and Creo platform) is installed locally and the environmental
variables are not set, local installation takes precedence even if Creo finds the
network installation. Using environmental variables, you can change the order of
lookups...."
