4 Replies Latest reply: Feb 1, 2013 9:11 PM by Richard Wagenaar

    2013 Install..not

    James Barnes

      I first allowed SW 13 to install over 12.. all I seem to have had are random crashes.. so giving up and doing what I've alwayst been told to do.. Uninstall/Reinstall.. seems like thats what I did when moving to 2012 version..

      Now I can't get SW 13 to install at all, gets to around 25-26% and crashes with some cryptic error that makes no sense.

       

      searching through the logs I find:

       

      07:52:41 Info Step 90 0 "{0: Installing} MSI: {1: D:\swwi\data\SolidWorks.Msi}; command-line: {2: INSTALLDIR="C:\Program Files\SolidWorks Corp\SolidWorks (2)\"  ADDLOCAL=FeatureWorks,PhotoView,SolidWorksAnimator,SolidWorksToolbox,SolidWorksUtilities,CoreSolidWorksTaskScheduler,RealViewGraphicsdisplay,ExampleFiles,Manuals,HelpFiles   SLDIM=1 REBOOT=ReallySuppress TRANSFORMS="D:\swwi\data\1033.mst" TOOLBOXFOLDER="C:\SolidWorks Data (2)\" OFFICEOPTION=1 ARPSYSTEMCOMPONENT=1 IMTOKEN=95badf909d83a52bd84a5daac7772dc9}
      (ID {3: SolidWorks}, lang {4: }, pcode {5: {B6B5EA7E-B91F-443D-A958-B0062FB53804}}, mode {6: 3}, upg = {7: }, f{8: 0}, costKB {9: 3702671})"

      07:54:05 Info Status 58 55803 "Received data from Installation Manager server (Script: {0: http://im.solidworks.com/bin2013/Connect.pl?Release=20130-40000-1100-100&Debug=0&ini=0&osa=64:1:2&lid=1033&app=I&cx=4097:0&cm=-1&lfr=&lfp=&lfv=}, Code: {1: 0}, Error: {2: }, File: {3: <none>})"
      07:57:05 Info Status 58 55803 "Received data from Installation Manager server (Script: {0: http://im.solidworks.com/bin2013/Connect.pl?Release=20130-40000-1100-100&Debug=0&ini=0&osa=64:1:2&lid=1033&app=I&cx=4097:0&cm=-1&lfr=&lfp=&lfv=}, Code: {1: 0}, Error: {2: }, File: {3: <none>})"

      07:57:38 Error Status 156 0 "***START DUMP OF WINDOWS INSTALLER DATA***"
      07:57:38 Error Status 157 0 "=== Logging started: 1/31/2013  7:52:48 ==="
      07:57:38 Error Status 157 0 "Action start 7:52:48: INSTALL."

       

      then some error text at the bottom..

      07:58:58 Error Message 9 55200 "Dialog Shown: {0: Internal error: The Windows Installer for this product component did not run as expected: RollbackUnReg_DocMgrDLL.9FB07B3D_0B7D_4A2F_82AB_F16B1F24912C.: Contact Technical Support.}.  User selected: {1: 1}"

      07:58:58 Info Status 164 0 "Enter Final State called with install error = {0: ** Install FAILED with code 1603}.  InServer = 45359544, EnterFail = 45359624, status = 45360184"

      07:58:58 Info Status 64 55809 "The installation failed."

       

      I've tried some of the stuff in the knowagebase.. no luck.. have a call into the VAR.. but who knows when I'll hear back.

       

      still the worst version of SW I've ever used.. never have had any install issues before.. all the way back to 2004..

       

      jb..

        • Re: 2013 Install..not
          Paul Marsman

          James,

            First, remove the attached logs or edit them to remove your Serial Number and re-attach.

           

            Second, it looks like it is having trouble registering your .NET dlls.  Some history on exactly what you've done since starting this process would help us help you.

           

          Paul

          • Re: 2013 Install..not
            Dan Riffell

            Are you sure you are using supported hardware and software? I had an install issue with 2013 on my laptop that ended up being a weird graphics card problem that i didn't have in 2012.

            • Re: 2013 Install..not
              Richard Wagenaar

              When scaling at 160% dimension input is a mess.jpg

               

              Solidworks 2013 has serious scaling problems.

              At 2560x1440 and 160% scaling you can't see

              your dimension in the edit dimension box, see picture..

              This problem is also in the find references command

              since SW2010. These problems get worse.

              SW2005 didn't have these 2 problems.

              These problem are only in SW2013 both in W7 and W8

              and it depends on the resolution of the monitor.

               

              I don't understand why these problems show up

              in the most used command, I can understand that

              this gets missed with the find reference command

              but not with the most used command.

               

              2560x1440 27"  is standard for modern hardware, even

              Microsoft 10" tablets have this resolution.

               

              I also don't understand what this parameter does on top,

              if you almost never need to edit parameter names then

              you should not have to look at that while editing a dimension.

              I find myself unintended editing parameter names instead of

              dimensions. I don't understand why a clean good working dimension

              box gets messed up both with parameter names and messed up

              because of DPI scaling problems.

              Using modern hardware should not be a problem