Hi all.what causes this error and how it can be removed.i get this error when i want to load Cro Parametric.
I suspect your startup shortcut if incorrect. Do you still have the default Creo startup shortcut and does this function? Has anyone changed folder names or locations for the Creo install? Do you have multiple Creo installations? Is the path pointing to non-existing "earlier" installation?
I will suggest you start a case with PTC to confirm the install if you still have maintenance.
yea it is the shortcut.
it is not functioning.
No one has changed the forlder names.
yes i have installed creo 1 but that has a separate folder in a separate drive.i have uninstalled that but still a problem.
The path doesnot point so.
Are you installing any additional extensions? Have you tried to install to the default folder?
I know this is frustrating and it really should be a simple thing. I can tell you, although it will not help, that every installation has worked as long as I follow some basic steps: Uninstall completely; download the install program and help files (6+gb!) and extract them to an install folder in the root; create a Creo program folder; drag and drop the license file when prompted during install; step through the pages to include Mechanism extension (the default included version); provide my custom install path; install... and install the help files the same way. I test this with using the default icon on the desktop and no custom config.pro. with this procedure, it always boots up without issue. The 1st time it boots up, it has to install a few programs. This could be where your bootup is failing.
The only time the install failed is when I did an auto install over the web on Creo 1.0 F001.
If this continues, please contact customer support.
I have been having the same problem and am dead in the water.
We just upgraded to Creo 2.0 and cannot get it to open.
Application configuration file open error,
unable to launch application because no valid configuration (*.psf). etc, etc, etc,
Uninstalled everything that is PTC related, and re-installed manually to no avail.
It appears that Creo cannot find the parametric.psf that does exist in the parametric\bin folder.
Or there is something incorrect in the parametric.psf file itself.
I see that this question is "Not Answered".
I'm going to take a wild guess here but I will recommend you open a support case and have customer support walk through this with you.
My guess is that the PST file is the personal preferences file that exists somewhere in the user folders (not PTC folders). I know that as you upgrade, your personal settings are maintained. This is primarily the ribbon modifications. I don't know exactly where they are located, but you might need to remove this folder before installation of the application.
Antonius, thanks for your response.
This is an install from new - no custom or personal preferences.
The only .pst file on my computer is an Outlook archive file, so I don't understand how that could possibly connect.
I suspect a company controlled file someplace has something incorrect within, but to get our IT department to help is like a silboat without a rudder and a keel.
Marshall, you would do well to get the information from IT or the purchasing department to get access tot he PTC Support site. You need the support account number so you can sign up and from then on, you will get support from PTC through their site. Fully traceable and they are capable of helping you with a screen share (if allowed by your company). You can also submit files with non-disclosure if you have corrupt of problem files that you need PTC to look at or reference. I have worked at companies that shield the users from support sites. Now that I've used them, I can't see why anyone wouldn't want access.
However, you wouldn't be the 1st to have roll-out problem. It could be as simple as a wrong MAC address or problems with the way your registry reports the nic cards. Maybe the error message is a red herring. In this case, I would get with customer support or even you VAR to get this resolved ASAP.
It's looking for a *.PSF file, not *.PST. It's a "PTC Startup File" and it tells Creo Parametric what license to use upon launch and sets a bunch of environment variables. You need at least one and it should have been created when you installed Creo.
I have never met such situation. If you can upload your parametric.psf file I can check its contents.
You can also try the following procedure:
Thanks for your response.
Like you, I suspect that there is something written wrong in the process of our custom start up files.
We are bound by the IT department's controls during log in, and customization is most likely the culprit.
I am a distant installation from our main installation.
I wish I could install raw from a DVD, using all the defaults because I beleive it would function.
I am on day 3 with no real support from out IT.
My paramatric.psf minus the license statement (proprietary):
// PTC - PSF file: parametric
DESC=Creo Parametric (default)
License statement was here
ENV=CREOPMA_FEATURE_NAME=PROE_Flex3C PROE_Flex3CRG ()
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\nms\nmsd.exe" -noservice -timeout %NMSD_TIMEOUT% &
// USER - PSF
// Add User specific environment or run applications below here
Double clicking on parametric.exe does nothing.
cd PTC\Creo 2.0\Common Files\M040\text
copy "T:\common\Pro\configs\config.pro" "c:\PTC\Creo 2.0\Common Files\M040\text"
"C:\PTC\Creo 2.0\Parametric\bin\parametric.exe" "C:\PTC\Creo 2.0\Parametric\bin\parametric.psf" %*
I have un-installed EVERYTHING that is PTC related, including the Environment Variables from Creo Elements, and re-installed manually using the controlled batch files from IT which is from their written proceedure.
I found that double-clicking parametric.exe does nothing on your PC. It's strange ... It looks like parametric.exe cannot be executed on your PC for some reason. I can imagine only one possibility - you have 64-bit installation on 32-bit operating system.
Your two step proceedure was to open Creo2.0 folder, then double click parametric.exe which I did and nothing happened whatsoever.
The icon associated with parametric.exe is the generic windows icon, which appears that the exe is not properly associated, but is indeed linked to PTC.
go into Creo 2.0\Common Files\M040 directory and look for the following subdirectories
Are these directories present in you installation ?
i486_nt is present in 32-bit installation
x86e_win64 is present in 64-bit installation
your psf file is OK.
Your Creo_Start.bat is also OK:
So the main problem is ... "double-clicking parametric.exe does nothing". Unfortunatelly I don't know how to resolve it.
Thanks for the review of the files.
Yes I agree that Exit is not needed, but I am not at liberty to make change at this time.
I am concerned that our IT cannot resolve the problem either.
If I click on reconfigure.exe what will I experience?
reconfigure.exe launches installation manager. I never use it. I think you can use it if you need to define new startup command (psf file) of modify existing one.
I have no idea how to help you. I give up...
We have determined that the installation files on our network are corrupted and are attempting to refresh the files.
Hopefully this will solve the problem.
Installation across out network is probably the worst way we can attempt this, but its the process we must abide by.
I think it is logical that your installation does not work because installation files are corrupted.
BTW ... copying files over the network is usual way I use when I install ProE/Creo on several computers.
My procedure (litle bit simplified):
You have described our process also.
Problem is today that the zipped file is corrupt and it took over 5 hours to transfer through our T1 internet.