Slow Sartup SW2007 SP2.1 1

[oharag]

Anyone notice that SW2007 SP2.1 takes forever to startup on initial launch? It takes like 5 minutes to finally come up. You first see the launch screen, and then nothing. I have 1 Gig of memory, but I don't think this is the issue. A colleague of mine has 4 gigs in his computer (oh, and it's a very fast dual core system as well). This gentlemen states that he even launches two instances of the program thinking the first one did not take.

We have licensing on each computer (i.e. not network driven licensing).

SW2006 was never this slow to boot.

 

[pdybeck]

I have not seen 5 minutes as a length of time to initially start. Something is goin on there. Check and see if your ant-virus is scanning your program files directory for SolidWorks. As a side note, I think SolidWorks is written for the .NET platform and generally the first time you start a program there is an extended period (should not be 5 minutes though). Each subsequent time is much faster. I believe this has something to do with the Just in
Time compile that occurs. I may be wrong, so don't quote me. You will notice the same with a program like Adobe Reader, altough with later versions I think portions of adobe may run when you start up your computer and login to Windows.

 

[Theophilus]

Make sure you don't have the little update window pop up--that will hang everything for a long time (until discovered). I've had it pop up behind every window on my machine before (dumb) and not show up on my task bar for several minutes. (I love it when that happens. ..)



Jeff Mowry

http://www.industrialdesignhaus.com

Reason trumps all. And awe transcends reason.

 

[J-C]

Something is up....you may try disconnting your computer from your network just to see if something is going on there. Also, what add-ins are you loading on startup?

My PC is a 2.4ghz P4 with 1gb ram and a Geforce 6800GT graphcis card. Swx2007 takes maybe 30 seconds or so to open right after a reboot (certianly no more than a minute). Subsequently opening it takes only a few seconds since its cached some of the files.

Jason

UG NX2.02.2 on Win2000 SP3
UG NX4.01.0 on Win2000 SP3
SolidWorks 2007 SP2.2 on WinXP SP2

 

[Theophilus]

That's about what mine is like normally, too.



Jeff Mowry

http://www.industrialdesignhaus.com

Reason trumps all. And awe transcends reason.

 

[SBaugh]

If you have all the Add-ins turned on it will take much longer to start up, because it has to run each *.dll for each add-in. Turn off all add-ins until you need them.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[CorBlimeyLimey]

When are you launching SW? At boot-up or after booting has fully finished?

Which OS (XP or Vista ... x32 or x64)?

Which SW version (x32 or x64)? Can you update to SP3?

Which AV are you using? If Norton ... dump it ... ASAP.

Are you using Novell?


SW07-SP3

 

[Olid]

We went through the same thing when we upgraded to 2007.
Are you also using PDMWorks? If so, there is a known problem regarding Windows 2003 Server. Solidworks has issued a technical bulletin which will help you resolve the problem.

Basically you need to install a hotfix on your PDMWorks server.

SolidWorks Technical Bulletin

Apr-26-05 Bulletin - Applying Microsoft Hot Fix 831168 for PDMWorks on a Windows 2003 Server

(

http://support.microsoft.com/default.aspx?scid=kb;en-us;831168)

to Windows Server 2003 SP1 and SP2.

With the release of Service Pack 1 for Windows 2003 Server, Microsoft Hot Fix 831168 (

http://support.microsoft.com/default.aspx?scid=kb;en-us;831168

) will no longer work and cannot be reapplied. This hot fix addresses performance problems with some applications running on Windows Server 2003, including PDMWorks. Typical symptoms with PDMWorks are excessive time to login to the vault and take ownership of files, as well as high CPU usage on the server.

Workaround: For Windows 2003 Server machines which have been upgraded to SP1 and are exhibiting the performance problems described above, it is possible to use the mfc42.dll / mfc42u.dll files from the hotfix. The PDMWorks service should be stopped and these two dll files (mfc42.dll / mfc42u.dll) should be placed in the same install folder as PDMWorks vault executable, i.e. the folder where pdmwservice.exe is located. When the PDMWorks service is started up again it will use the DLLs in the local folder rather than those in the c:\windows\system32 folder. This will workaround the problem, without changing any files on the Operating System which other applications may be using, until Microsoft provides a solution.




Regards,
Dan Olid
SW2007 SP2.2
PDMW 2007 SP2.2
Cad Designer/PDMW Admin

 

[oharag]

Launching SW at bootup, or after it doesn't matter. Both are slow.
Using Windows XP SP2 32 bit
Yes using PDMWorks 2007 on a server offsite (no clue what they use for server).
I did have PhotoWorks on, decided to turn it off.

Thanks Olid for the info. I'll check with IT tomorrow.

 

[ctopher]

I have noticed that since upgrading to SW 3.0, PDMW does not auto load. The addin is always checked. After SW loads, I have to go to PDMW and login.
SW07 has loaded slow for me since install.

Chris
SolidWorks 07 3.0/PDMWorks 07
AutoCAD 06
ctopher's home (updated 03-13-07)

 

[oharag]

Timed it this morning.

3.5 mins to boot.

It seems to have taken longer than that in the past. I did turn off PhotoWorks. Maybe that helped a little.

 

[oharag]

OLID sent your info onto our IT staff. Thanks again for the heads up.

This is why I come here first for my SW related questions and problems