Skip to main content
F
fmueller1-Visitor
1-Visitor
January 31, 2014
Solved

Creo 2 hangs at startup sporadically but not reproducable

  • January 31, 2014
  • 4 replies
  • 7278 views

Hi Creo 2.0 users,

Since we upgraded to Creo 2.0 we have the following problem. sometimes when we try to start Creo the application does not start. If we look into the task manager we then always see that one CPU core is running at 100% (a dual core says CPU load is 50% a quad core says 25% a.s.o.) used by xtop.exe. The RAM used by xtop.exe is always within a certain rance between 45.000K and 51.000K. This differs slightly from workstation to workstation and from case to case but it does not differ very much.

Sometimes we just need to start Creo a 2nd time (with the same configuration) and it starts well, sometimes it needs other tricks to get it running. What we have found so far is that sometimes if we just start with another License (e.g. CreopParametrick with AAX instead of plain CreoParametric) Creo starts successfully. Sometimes we need to tamper with the enviroment variable Pro_Lang. On some computers we need to set these variable to an invalid value in order to get Creo starting. On other computers our standard Pro_lang is set to german and they work works successfully.

If we start without any config.pro a complete plain and naked CREO it always works. We have tried to half/quarter a.s.o. our config.pro-file to identify if there is any line causing that problem but it was not reproducable at all. Sometimes everything works and sometimes it just does not work without any modification.

We have 13 licenses of CreoParametric/Essentials/AAX running on two different license servers in our company. Each of the licence servers is managing only a part of all our floating licenses. All client CAD-Workstations can use licenses from both licence servers. If the Creo start hangs, CREO always has reserved one licence for the session which does not start.

Using the CreoSystemMonitor (which is available since M060) does not give any information - The session is simply not yet recognized by the system monitor.

All our computers are running with Symantec Endpoint protection Version 12.1.1000.157 RU1 and we are not allowed to switch that off on the workstations.

We have still Windows XP64bit and plan to update to Win7-64bit this year. Our workstations are different HP workstations all with certified NVIDIA graphic cards. RAM is between 8GB and 32GB depending on the workstation. Processors are different intel Dual-, Quad and 8-Core.

After one year facing this problem its still there with the current M090 and I think that it might be a timing problem of some time critical processes during the start of the Creo application. I somehow cannot imagine any other cause of such non-reproducable error. Our Hotline cannot help us, because we cannot tell them a way how we could reproduce it.

Is there anyone out there who has similar experiences or ideas what the cause of that problem could be?


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 fmueller

Hi Folks,

it seems that Creo M140 solved the problem or at least significantly reduced the no-start behaviour. Since we updated to M140 it has not happened again.

We also changed from two different Licence servers (running on different virtual servers) to only one server where all licenses are managed. This might also have been part of solving the problem.

4 replies

H
HugoBarosa1-Visitor
1-Visitor
January 31, 2014

Can you show us your config.pro so we can try to help you?

F
fmueller1-VisitorAuthor
1-Visitor
January 31, 2014

Sorry, I should have done that with my initial post.

Please find attached my current config.pro, taken from c:\Program Files\PTC\Creo 2.0\Common Files\M090\text\

The local workdirectory does not contain any other config.pro.

H
HugoBarosa1-Visitor
1-Visitor
January 31, 2014

Do you create a new config.pro when new versions are released?

In a fast look i think there are some options not available now, so that can be the problem, try to start Creo

with the first 10 lines of config.pro, then add 10 more, then 10 more... i can't analise if the paths are all correct of even if they exist

F
fmueller1-VisitorAuthor
1-Visitor
January 31, 2014

When updating, we usually check if options are not available anymore and add new ones. In our case we did so when we updated from Wildfire 3 to Creo2.

As I wrote above, we did check the config.pro by splitting it in two halfs - then testing each half a.s.o. That should working as well as your proposal. For reproducable errors we should be even quicker than looking line by line or 10-lines by 10-lines.

The problem is: How do you recognize an error, when the error does not occur each time but only sporadically? You can wait until it happens once - then you modify your config. pro and afterwards it runs. You add the line(s) again to doublecheck and it runs too. So you are as wise or as thumb as before.

We are working with about 10 people with that config.pro and it happens "just" sporadically (once or twice a week at some workstations. At others luckily more seldom).

Furthermore - if I didn't even touch the config.pro. but just start Creo another way e.g. with the AAX-Licence option attached, the chance getting it running the next try is 90%. Or I just change in my batch script the Pro_Lang environmental variable from german to a non valid value or vice versa - again it works - until it hangs the next time.

F
fmueller1-VisitorAuthor
1-Visitor
March 7, 2014

Hi Folks,

it seems that we are to only one experiencing this matter???

I was hoping that perhaps someone else has similar issues and that we could compare our installation and configuration to look about common things which could cause that problem. It looks as if we has a quite "special" issue here, isn't it?

F
fmueller1-VisitorAuthorAnswer
1-Visitor
March 3, 2015

Hi Folks,

it seems that Creo M140 solved the problem or at least significantly reduced the no-start behaviour. Since we updated to M140 it has not happened again.

We also changed from two different Licence servers (running on different virtual servers) to only one server where all licenses are managed. This might also have been part of solving the problem.

Terms & ConditionsCookie settingsAccessibility statement