AnsweredAssumed Answered

Solidworks 2012 sp.4 installtion 1903 & 1603

Question asked by Lewis Hardacre on Oct 22, 2012
Latest reply on Nov 1, 2012 by Steve Prodger

Like • Show 0 Likes0
Comment • 3

2 This error is actually driving me crazy !

I am trying to install solidworks 2012 sp. 4 onto my windows 7 32 bit laptop .

Everthing was going fine and then it hit the error !

The error is as following :

Internal error: The Windows Installer for this product component did not run as expected: 0.

Contact Technical Support.

When contacting Technical Support about installation issues, you will need to provide the installation log files available in this directory. Use the button below to save your logs as a zip file for sending to your support representative.

This is while im trying to install visual studio tools .

There is a option to skip this and continue on installing , I tryed to do this and got the following error :

Internal error: The Windows Installer for this product component did not run as expected: 1903.

Contact Technical Support.

Also i have tried many solutions like regestiry edits and installing the preq before hand

Thanks for any help

Lewis

No one else has this question

Outcomes

Deepak Gupta Oct 24, 2012 1:30 PM

Welcome to SolidWorks forums Lewis.

Please check solution id S-057711 in SolidWorks Knowledge Base for a possible solution.

You might also find this post helpful for your future reference.

Actions

Jim Sculley Oct 24, 2012 2:16 PM

I install from admin images and will sometimes get the 1603 error on some machines. One thing that seems to help is to be sure to uninstall (using Window Control Panel) *all* instances of the Visuall C++ 2005 and 2008 runtimes and VSTA (Visual Studio Tools for Applications). The SW installer will install the versions it needs. These runtimes are a common source of conflict because different applications will intall different versions and they often do not play well together.

I also use Piriform's CCleaner tool to scrub the registry of bad CLSIDs, orphaned registry entries and other miscellaneous junk before installing. Run the Registry scan and fix all issues as many times as needed until you get a scan with no issues. Reboot and then try to install SW.

http://www.piriform.com/

Other things I've seen cause 1603 errors:

Lack of disk space
Locked toolbox database
No admin rights on the machine

Jim S.

Actions

Steve Prodger Nov 1, 2012 3:48 PM

I am getting similar results.

I have 45 or so workstations that all have SW 2012 SP3.0 that were installed from the same admin image. I just created an image for 2012 SP5.0 and renamed the shares so the latest SP will update automatically. When I launch SolidWorks on a workstation to test the update I get to about 23% and the 1903 error pops up.

After reading some posts with similar problems that pointed to a shared Toolbox, I deselected the Toolbox install from the SP 5.0 image but now get a generic fatal error message.

I checked the knowledge base on S-057711 which instructs to rename the VSTA reg keys and re-install but that would defeat the entire purpose of an automatic update. If I have to visit every workstation to do that I might as well run the deployment at the same time.

Has anyone been able to get the automatic SP deployment to work without having to visit every workstation to fix something? Seems awefully flakey...

Actions

3 Replies

Deepak Gupta Oct 24, 2012 1:30 PM
Mark Correct
Correct Answer
Welcome to SolidWorks forums Lewis.

Please check solution id S-057711 in SolidWorks Knowledge Base for a possible solution.

You might also find this post helpful for your future reference.
Like • Show 0 Likes0
Actions
Jim Sculley Oct 24, 2012 2:16 PM
Mark Correct
Correct Answer
I install from admin images and will sometimes get the 1603 error on some machines. One thing that seems to help is to be sure to uninstall (using Window Control Panel) *all* instances of the Visuall C++ 2005 and 2008 runtimes and VSTA (Visual Studio Tools for Applications). The SW installer will install the versions it needs. These runtimes are a common source of conflict because different applications will intall different versions and they often do not play well together.

I also use Piriform's CCleaner tool to scrub the registry of bad CLSIDs, orphaned registry entries and other miscellaneous junk before installing. Run the Registry scan and fix all issues as many times as needed until you get a scan with no issues. Reboot and then try to install SW.

http://www.piriform.com/

Other things I've seen cause 1603 errors:
- Lack of disk space
- Locked toolbox database
- No admin rights on the machine
Jim S.
Like • Show 0 Likes0
Actions
Steve Prodger Nov 1, 2012 3:48 PM
Mark Correct
Correct Answer
I am getting similar results.

I have 45 or so workstations that all have SW 2012 SP3.0 that were installed from the same admin image. I just created an image for 2012 SP5.0 and renamed the shares so the latest SP will update automatically. When I launch SolidWorks on a workstation to test the update I get to about 23% and the 1903 error pops up.

After reading some posts with similar problems that pointed to a shared Toolbox, I deselected the Toolbox install from the SP 5.0 image but now get a generic fatal error message.

I checked the knowledge base on S-057711 which instructs to rename the VSTA reg keys and re-install but that would defeat the entire purpose of an automatic update. If I have to visit every workstation to do that I might as well run the deployment at the same time.

Has anyone been able to get the automatic SP deployment to work without having to visit every workstation to fix something? Seems awefully flakey...
Like • Show 0 Likes0
Actions

Solidworks 2012 sp.4 installtion 1903 & 1603

Outcomes

Related Content

Recommended Content