Pro-E takes forever at Startup

[anandel]

Hello all,

I am posting this for a fellow worker. In his machine it takes really long for Pro-E to open up. Ofcourse the subsequent startups are pretty quick, but the first one is really slow. Ours is a small shop, all clients are local installations with the license in the server. I sit right beside him, pretty much the same computer and I can't really complain of my startup speed. This morning we timed his startup time, came up to 6 min 20 seconds, from double click pro icon to File->Open.

Any suggestions, comments? I did a quick search, couldn't find something very relevant. And no, I am not logging a call with PTC.

 

[newton126]

Could be a network issue. It would also be helpful to know if your statup command only calls the Pro/E executable or does it do a bunch of other stuff too (like copying files from a server...)?


Why wouldn't you open a call with PTC support?

 

[ABB_pajo]

Hi !!

If you are using any Windchill products, check your local cache file. Stored under Application Data>PTC in your local profile. Delete / Remove that and ProE is starting much faster. Just make sure you don't have any modified files in your workspace first...

 

[pmack009]

You should also look at your license configuration if you only have one license server make sure there only one license in there.

Try opening Pro/E with no config.pro config.win or config.sup

Also are you using Intralink or Windchill?

 

[anandel]

newton126:
The startup command calls only for the Pro-E exe. There's no script that runs to copy files. Also, the hardware is pretty much the same too (though mine is a little better in terms of processor/hard drive). I do suspect that this could be network issue, but can't put my finger and say how and why. As for logging a call, well I thought you guys are a bit more reliable than PTC

ABB & pmack:
No, we don't have Intralink or Windchill. We only have one license server and... "make sure there only one license in there"... I don't understand that part. But I'll try opening Pro without config.pro or win.

Thanks for the response all. Please keep it coming.

 

[ABB_pajo]

Hi anandel !

Do you have mapped disk that is used for coping data to ProE or search_paths. If thouse servers is down, it could also cause a lots of pain..

Regards
Patrik

 

[anandel]

Hello Patrick,

We do have mapped disks, but nothing is copied from them into our search paths. Also, does it matter at startup? I thought all proe would do at startup is to execute proe.exe from the startup directory. Btw, the startup directory is a local one.

 

[pmack009]

make sure there only one license in there

You need to run the pro/e setup file ptcsetup.bat in the bin dir: or insert the install CD next over until you get to the license part.

To test the network you could hook his/hers computers to your network cable. This can be done at the sever side as well.

 

[anandel]

oh.. I got you.. yes, I already did the ptcsetup and yes, there is only one server. As for the network cable, I'll try doing that some time. Could it be a bad cable or something? but he doesn't seem to have a problem otherwise after Pro-E is started.

Ours is a relatively small shop, one person taking care of like 6-7 seats. So, I guess there isn't very many variables that could be different or can go wrong. That's what really is perplexing to me. This problem is not entirely a show stopper here but more of an annoying one that we wanna get rid of sometime.

 

[anandel]

Ok..here's what happened. My co-worker had his trail files location pointed to the same directory as of his startup one. And he hasn't been clearing them out regularly. I basically purged it, took out all the other unwanted files there, created a new folder and pointed the trails to there and started Pro-E (I did all that first thing in the morning before he started pro). Voila.. the startup time was cut down to about 40 secs. I don't know if this made any sense to you guys at all, but it worked. I would love to know the exact reasoning, if there's one, but clearing out junk from the startup directory did the trick for me.

Thanks all.

 

[ABB_pajo]

Hi anadel !

Again regarding search paths: Even though you not are copy from them or not. BUT if ProE is reading info from the drives and gets no responce, it will take time..

That's why we copying all required files and stores them locally (at each startup). It takes 20 sec more but in the end of the day we increace the overall performance.
Regards
Patrik