AnsweredAssumed Answered

Installation of Solidworks 2012 thru SCCM

Question asked by Jeff Lang on Oct 31, 2012
Latest reply on Jan 13, 2014 by Nathan White

Like • Show 0 Likes0
Comment • 14

Was wondering if anyone has had a successful install thru sccm using a admin image? I have followed the recommendation to the letter, using the following to create a package and inserting this in the command line:

msiexec /i " \\Server*\name*\Solidworks\swwi\data\SolidWorks.Msi" INSTALLDIR="C:\Program Files\Solidworks Corp" SOLIDWORKSSERIALNUMBER="#### #### #### #### " ENABLEPERFORMANCE=1 OFFICEOPTION=3 ADDLOCAL=SolidWorks,SolidWorksToolbox /qb

It seems to start to install but fails and gives me the error 0x643 (1603)

Any help would be appreciated. In trick to inserting and running it in sccm 2012 would help.

No one else has this question

Outcomes

14 Replies

Rod Trent Nov 12, 2012 5:25 PM
Mark Correct
Correct Answer
That error is usually associated with the .NET framework. Does the .NET framework need to updated or installed first? Is it the correct version required by SolidWorks?
Like • Show 0 Likes0
Actions
- Jeff Lang @ Rod Trent on Nov 26, 2012 11:45 AM
  Mark Correct
  Correct Answer
  .Net was installed before installing solidworks and yes I believe I have the correct version of .net It's funny becuase I can run the install fine with the this thru a command line and works great:
  
  msiexec /i " \\Server*\name*\Solidworks\swwi\data\SolidWorks.Msi" INSTALLDIR="C:\Program Files\Solidworks Corp" SOLIDWORKSSERIALNUMBER="#### #### #### #### " ENABLEPERFORMANCE=1 OFFICEOPTION=3 ADDLOCAL=SolidWorks,SolidWorksToolbox /qb
  
  I guessing It's somethign in SCCM that is the cuase of this but t=for the life of me I can't figured it out.
  Like • Show 0 Likes0
  Actions
Greg Rupp Nov 12, 2012 5:41 PM
Mark Correct
Correct Answer
I believe 1603 is the generic error code. We had the same issue, both computers got 1603, but had to different solutions.

Computer “A” with the ”featurestate” error was fixed by uninstalling all old versions of solidworks using the Microsoft “Fixit” tool.

Computer “B” with the “1903/1603” error was fixed by uninstalling VSTA, cleaning up the registry. (see S-045424 for more details).

We too pushed an admin image using SCCM 2012.
Like • Show 0 Likes0
Actions
Nathan White Aug 27, 2013 10:43 AM
Mark Correct
Correct Answer
We are installing fine through SCCM. We are using this command line:
32bit\sldim\sldIM.exe /adminclient /new /source .\AdminDirector.xml

Just make sure the AdminDirector.xml file is correct and sets the licence key etc...
Like • Show 0 Likes0
Actions
- Russel Oxley @ Nathan White on Jan 12, 2014 10:47 AM
  Mark Correct
  Correct Answer
  When I run this I get a bad environmant error..
  
  32bit\sldim\sldIM.exe /adminclient /new /source .\AdminDirector.xml
  Like • Show 0 Likes0
  Actions
  - Nathan White @ Russel Oxley on Jan 13, 2014 6:27 AM
    Mark Correct
    Correct Answer
    Make sure you have distrubuted the content and make sure when you advertise the program to run from the distrubution point.
    
    We have it as a "Package" rather than an application in SCCM 2012 as if you run as an application it will try and download all the installation files from the distrubution point and then run on the client, as its rather large i wouldn't do that.
    
    Also make sure you have this set up on the distrubution settings:
    Like • Show 0 Likes0
    Actions
    - Russel Oxley @ Nathan White on Jan 13, 2014 7:04 AM
      Mark Correct
      Correct Answer
      Its set up like the Pic above, and we have it Deploying as a package and set to run from the DP.
      Below is the command line. I think at this point thats what the issues is.
      What is yours set to?
      Like • Show 0 Likes0
      Actions
      - Nathan White @ Russel Oxley on Jan 13, 2014 7:41 AM
        Mark Correct
        Correct Answer
        Hi Russel, my package is like:
        Like • Show 0 Likes0
        Actions
        Russel Oxley @ Nathan White on Jan 13, 2014 7:44 AM
        Mark Correct
        Correct Answer
        Can I see the the rest of the command line?
        Like • Show 0 Likes0
        Actions
      - Nathan White @ Russel Oxley on Jan 13, 2014 7:43 AM
        Mark Correct
        Correct Answer
        Also set on the Enviroment tab:
        Like • Show 0 Likes0
        Actions
        Russel Oxley @ Nathan White on Jan 13, 2014 7:47 AM
        Mark Correct
        Correct Answer
        I didnt run it to display and this is the error I got. Looks like I'm not running the admin image maybe? I'm banging my head agaisnt the wall. lol
        Like • Show 0 Likes0
        Actions
      - Nathan White @ Russel Oxley on Jan 13, 2014 7:45 AM
        Mark Correct
        Correct Answer
        Full command line: 64bit\sldim\sldIM.exe /adminclient /new /source .\AdminDirector.xml
        Like • Show 0 Likes0
        Actions
      - Russel Oxley @ Russel Oxley on Jan 13, 2014 7:53 AM
        Mark Correct
        Correct Answer
        what about your folder structure?
        
        Dassault Systems\Solidworks\SolidWorks 2013 SP5\64bit
        
        the x64 id the folder that includes the AdminDirector XML File.
        
        What are the these folders?
        
        /adminclient /new /source ? Just something you created with your structure?
        
        64bit\sldim\sldIM.exe /adminclient /new /source .\AdminDirector.xml
        Like • Show 0 Likes0
        Actions
        Nathan White @ Russel Oxley on Jan 13, 2014 7:59 AM
        Mark Correct
        Correct Answer
        This structure is created when you create the Admin image. I would create this as you can set your licencing and SLDreg file. Go to sldAdminOptionEditor.exe in the root:
        
        Then click the pencil to make changes:
        Like • Show 0 Likes0
        Actions

Incoming Links

Re: SW 2013 installation errors

Installation of Solidworks 2012 thru SCCM

Outcomes

Related Content

Recommended Content

Incoming Links