Can't install 2006 SP3.1 - MSI file issue

Discussion in 'SolidWorks' started by melickas, Feb 5, 2006.

  1. melickas

    melickas Guest

    Trying to install Solidworks 2006 SP3.1 (from SP2.0) on (7) XP
    workstations and getting an "error" on a (4) of them. Note - never had
    any issues installing service packs before, all maintained the same,
    hardware identical, some software in use is different,etc..

    When installing SP3.1 get the message:

    "Wizard cannot access: (where M:\is the CD-ROM)

    M:\swwi\data\English_i386_Solidworks.msi

    Please insert CD#1 used for the initial Solidworks installation &
    click Retry.../Browse"

    Then, after failure, get this Solidworks gray message box (not
    verbatim):

    "Installation source (CD or local network) product not available..
    (1612-0)"

    Have tried 3 different CD#1s, tried other CD-ROMs, cleared Temp files,
    re-downloaded SP3.1, etc

    This service pack did install on (3) workstations but will not install
    on (4) of them.

    Only thing these 4 failures have in common was a recent installation of
    Quickbooks 2006. I suspect a Windows installer file (*.msi) is corrupt
    or damaged but why one .msi file would affect another has me perplexed.

    Thanks for any advice!
     
    melickas, Feb 5, 2006
    #1
  2. melickas

    Bo Guest

    Also heard that Microsoft Windows Installer does NOT support external
    CD drives.
     
    Bo, Feb 6, 2006
    #2
  3. melickas

    Pete Guest

    SolidWorks states that SP3.1 is only for the Chinese version, unless
    you speak Mandarin you should install SP3.0
     
    Pete, Feb 6, 2006
    #3
  4. melickas

    melickas Guest

    Did not use an external CD Drive. By used "other CD-ROMS", the systems
    have more than one internal CD-ROM drive. Thanks anyway.
     
    melickas, Feb 6, 2006
    #4
  5. melickas

    melickas Guest

    Should I update to SolidWorks 2006 SP3.1 from SolidWorks 2006 SP3.0?

    Thanks but you must not have read my post (I updated from SP2.0 to 3.1
    and 3.1 is the only choice I had, and it worked on 3 systems)- from the
    Soildworks website:

    "If you are a non-Chinese SolidWorks customer, there is no upgrade from
    SP3.0 to SP3.1 as there is no change to the non-Chinese SolidWorks
    version. SolidWorks 2006 SP3.1 is an update only for the Chinese
    language version.

    If you are updating from a SP, in any language, previous to SP3.0,
    SP3.1 will be the only SP shown. SP3.0 will not appear on the list. For
    non-Chinese languages, there is no difference between SP3.0 and SP3.1."
     
    melickas, Feb 6, 2006
    #5
  6. See the thread "Installing 2006 SP3 - cannot access file d:.......works.msi
    error", where someone else reported the same problem and a solution was
    suggested that seemed to help. (I may not have typed the subject in exactly
    right.)


    Jerry Steiger
    Tripod Data Systems
    "take the garbage out, dear"
     
    Jerry Steiger, Feb 7, 2006
    #6
  7. melickas

    melickas Guest

    Thanks, I'll give this a try!
     
    melickas, Feb 7, 2006
    #7
  8. melickas

    melickas Guest

    Tried not using the swspmanager.exe however there is not a Sw2006
    2.0-3.1.exe file just an .msp file. Which gives a different error
    message if you click on it.

    Tried lauching the other *.msi from the Cd ( Such as French, etc) and
    the wizard works. What wrong with the English *.MSI????

    Thanks - anyone
     
    melickas, Feb 8, 2006
    #8
  9. melickas

    Bo Guest

    Why not just install everything from scratch from your original 2006
    CDs?

    Then do the correct update from SP0 to SP3.1.

    Bo
     
    Bo, Feb 9, 2006
    #9
  10. I have run into installing from external drives in the past. I have also
    just succefully ran an install of SW2003 and SP 3.1. Here is what I did.

    I use the original release of the CD's to create an administrative install
    on the network. "Important" - the share was referenced by share name, not
    drive letter! I then applied the patch to the share by share name, not
    drive letter. I then ran the install by share name, not drive letter.

    The reason for the share name is because some administrators on some
    networks can play with network policies and have Windows installer run with
    elevated priviledges which allows non-adminstrators to install approved apps
    via scripts when they have time because some users might not have time to be
    interupted if something does not work correctly. Since the Windows
    Installer is theoretically being installed by someone other than you that
    profile most likely does not have the drives mapped as you do when you are
    logged in or have some hardware activated as you might. Basically, to the
    installer the files are not there because they don't see the M: Drive.

    Using the share name works because Share Names can always be found even when
    something is running as a different user that technically as not logged in.

    See if that helps.
     
    news.lightship.net, Feb 9, 2006
    #10
  11. melickas

    zoetrope Guest

    Wow, here we have hack-and-slash IT genius Boy "Radeon" Wonder at it
    again. Ever heard of UNC paths? Of course you never needed to read
    the documentation, being such a freakin' genius. Using the UNC path is
    the recommended technique and far more stable than share names or
    mapped drives, being rather explicit. Rattle off those certifications
    again for us, would you?
     
    zoetrope, Feb 14, 2006
    #11
  12. You are such an IDIOT. What they heck do you think a SHARE NAME is??? HA
    HA HHAAAAAAHHH!!! You are so desperately grasping at straws to prove you
    are not the fool you really are but you end up saying things that make you
    look stupider by the second.

    So dumb @$$, was the answer right or wrong? Darn right it was right and I
    did not see you posting the solution! Thank you for showing the world what
    a dumb @ss you are.

    If you knew anything about dealing with actually helping people, which
    obviously you don't, you would know you try to Keep It Simple Stupid and not
    be some condesending jerk that thinks everyone should know everything you
    do. Since I had no idea of this person's technical background and was not
    totally clear on the network setup they had the best thing to do was to keep
    the terms as simple as possible.

    HA HA HA HA You don't know that a UNC is the server share name
    (\\Server\Share)!!! What a bone head...........
     
    news.lightship.net, Feb 14, 2006
    #12
  13. melickas

    zoetrope Guest

    HA HA HA HA You don't know that a UNC is the server share name

    No, dolt, a "share name" is an incomplete part of the UNC, which is the
    complete path name, including the server. Your example shows this
    well, if you only understood your own example.

    http://en.wikipedia.org/wiki/Uniform_Naming_Convention
    http://en.wikipedia.org/wiki/Uniform_Naming_Convention#Representations_of_paths_by_operating_system
    http://en.wikipedia.org/wiki/Network_share
     
    zoetrope, Feb 14, 2006
    #13
  14. You just can't admit you jumped the gun yet again and did not read the post.
    You just read what you thought you wanted to see and responded like a fool
    when everyone else knew what to do. You have to stop typing before you
    think about what you are writing. It is really making you look foolish.

    Go to bed and get a good night sleep. Take tomorrow off and relax your
    mind. You are obviously high strung and obsessed.
     
    news.lightship.net, Feb 14, 2006
    #14
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.