cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Open In Creo 9.0.6.0 takes more time to load in one of the servers

HM_10636609
4-Participant

Open In Creo 9.0.6.0 takes more time to load in one of the servers

Hi All,

 

When I try to open a model in Creo 9.0.6.0, it is taking more time to open (About 2 hours). The same model when opened in a different server, is taking less than 10 minutes to open. Can you please suggest what can be checked here? The server where I am facing this issue is a High clock speed server where we would generally expect better performance.

 

Thanks

Hari

1 ACCEPTED SOLUTION

Accepted Solutions
BenLoosli
23-Emerald II
(To:HM_10636609)

That sounds like there is something in that assembly that Creo does not like and is having a hard time resolving.

First thing to check for is circular references.

If this assembly is made up of sub-assemblies, try opening them one at a time and see if they will open quickly, this should isolate which file has the issues.

Look in the Creo log file and see if there are any warnings or other issues reported as the file is opened.

If it is only this one assembly, then there is something in it that is causing the issue.

Since it opens on one workstation fast and another slow, check the config.pro options on each workstation to be sure someone has not put something in there that the system does not like.

View solution in original post

6 REPLIES 6
BenLoosli
23-Emerald II
(To:HM_10636609)

Where is the data located that you are loading? Local server or remote?

Are you using Windchill? Files in the workspace already or coming from a local or remote server?

Is Creo loaded locally?

Have you tried to copy the file(s) to a local disk and then open?

HM_10636609
4-Participant
(To:BenLoosli)

Hi Ben,

 

The data is checked into Windchill. The files are coming from a remote server.

Creo application is installed locally. We have not copied the files to local disk. We will try that and get back.

 

Thanks

Hari

Hi @BenLoosli ,

 

We have copied the files locally and tried to open the model in Creo. We still see the same issue. We have tried with large model than the current model, We are able to open it without any issue. Any suggestion would be of great help.

 

Thanks

Hari

BenLoosli
23-Emerald II
(To:HM_10636609)

That sounds like there is something in that assembly that Creo does not like and is having a hard time resolving.

First thing to check for is circular references.

If this assembly is made up of sub-assemblies, try opening them one at a time and see if they will open quickly, this should isolate which file has the issues.

Look in the Creo log file and see if there are any warnings or other issues reported as the file is opened.

If it is only this one assembly, then there is something in it that is causing the issue.

Since it opens on one workstation fast and another slow, check the config.pro options on each workstation to be sure someone has not put something in there that the system does not like.

HM_10636609
4-Participant
(To:BenLoosli)

Hi @BenLoosli ,

 

We have tried isolating the issue. There were no Circular references. When an assembly is removed from the main model, the model opens up quickly (3 minutes). However there were many sub parts inside that assembly. So it is very hard to isolate to the single object level. 

 

We have checked the config.pro and it is same in the machine that has the issues when compared to the other machine which does not have the issue.

 

However, we are seeing this only for one such instance. Maybe we will further see if the issue reoccurs, we will resume our investigation.

 

Thanks

Hari

StephenW
23-Emerald II
(To:HM_10636609)

Since this is only one computer and is also associated to a windchill workspace, I would guess it is workspace cache related.

If the user has using a large workspace or "old" workspace, these tend to cause issues over time. 

Test with in new workspace.

You could also test by clearing the workspace cache. Deleting and re-creating the .wf folder is an option. Be aware that these options could cause loss of data if files are not checked-in or at least uploaded to the server side cache, so make sure you understand how that works before doing these options.

 

I would also test with no config.pro/config.sup files and no connection to the windchill database (out of the box configuration) on files that are located on the computers hard drive. 

Top Tags