none
Sequencing Solidworks 2009 - Problem with VSTA

    Question

  • I'm currently trying to sequence Solidworks 2009. The problem is that with the sequencer running, the installer fails part way through, leaving the core program incomplete and missing most of the addons. By comparing the install logs, I've tracked the problem down to a new "feature" in Solidworks 2009 - VSTA (Visual Studio Tools for Applications).

    Has anyone successfully sequenced Solidworks 2009 or any other apps that use VSTA? I've tried the usual stuff (installing prereqs first, etc) and I'm stumped.
    Thursday, July 9, 2009 7:32 PM

Answers

  • This is my recipe

    Before installing the 4.5.1 sequencer

    1: Install updates from solidworks prereq folder. Should be 2 installers

    2: Make sure that c++ 2005 and Dot net framework is installed before installing the sequencer

    3: Install sequecner, create exception to exclude local settings from exclusion items and then select save as default so it keeps the setting.

    4: Install to q:\sworks09.v1

    5: You will have to export the network license portion of the registry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Solidworks

    6: Once exported change CurrentControlSet with ControlSet001 and save it.

    7: Run the reg file with the change and you should now see the solidworks service inside ControlSet001 in the registry.

    8: Make sure you make the service start Automaticlly !!!!!!!

    9: Now stop monitoring and make it FB1

    10: check the services tab and make sure services are set to Automatic as well.

    11: Copy file to content directory and give it a whirl.

    -Danny

    Tuesday, September 1, 2009 2:27 PM

All replies

  • Here's what shows up in the log file when the install fails:

     SW MSG: Entering WIDll_RunVstaExe ...
     SW MSG: WIDll_RunVstaExe: szExeName = C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\vsta.exe  /hostid SolidWorks_VSTA /setup
    Action ended 11:21:13: set_Reg_VSTAHost. Return value 3.
    Action ended 11:21:13: INSTALL. Return value 3.

    Here's what it should look like:

     SW MSG: Entering WIDll_RunVstaExe ...
     SW MSG: WIDll_RunVstaExe: szExeName = C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\vsta.exe  /hostid SolidWorks_VSTA /setup
    MSI (s) (AC:90) [12:56:53:125]: Doing action: set_Reg_TB_ToolboxDataLoc
    Action ended 12:56:53: set_Reg_VSTAHost. Return value 1.
    MSI (s) (AC:AC) [12:56:53:328]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSIFE.tmp, Entrypoint: WIDll_SetReg_TB_ToolboxDataLoc
    Action start 12:56:53: set_Reg_TB_ToolboxDataLoc.
     SW MSG: Entering WIDll_SetReg_TB_ToolboxDataLoc...
     SW MSG: WI_GetProperty: SOLIDWORKSTYPE = SolidWorks (0)
     SW MSG: WI_GetProperty: SWREGISTRYKEY = SolidWorks 2009 (0)
     SW MSG: WI_GetProperty: TOOLBOXFOLDER = C:\SolidWorks Data\ (0)
    MSI (s) (AC:90) [12:56:53:562]: Doing action: Register_i386_SWFeedbackDll
    Action ended 12:56:53: set_Reg_TB_ToolboxDataLoc. Return value 1.
    MSI (s) (AC:40) [12:56:53:671]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSIFF.tmp, Entrypoint: WIDll_RegisterSWFeedbackDll
    Action start 12:56:53: Register_i386_SWFeedbackDll.
     SW MSG: WI_GetProperty: INSTALLDIR = Q:\SLDWKS09.001\SolidWorks\ (0)
     SW MSG: WI_GetProperty: REGASMDIR = C:\WINNT\Microsoft.NET\Framework\v2.0.50727\ (0)
     SW MSG: WIDll_RegisterDotNetDlls: szExeName = C:\WINNT\Microsoft.NET\Framework\v2.0.50727\regasm.exe "Q:\SLDWKS09.001\SolidWorks\swfeedback.dll" /codebase /silent
    MSI (s) (AC:90) [12:57:09:718]: Doing action: Register_i386_CWSWAddinDll
    Action ended 12:57:09: Register_i386_SWFeedbackDll. Return value 1.
    MSI (s) (AC:FC) [12:57:09:828]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI105.tmp, Entrypoint: WIDll_RegisterCWSWAddinDll
    Action start 12:57:09: Register_i386_CWSWAddinDll.
     SW MSG: WI_GetProperty: INSTALLDIR = Q:\SLDWKS09.001\SolidWorks\ (0)
     SW MSG: WI_GetProperty: REGASMDIR = C:\WINNT\Microsoft.NET\Framework\v2.0.50727\ (0)
     SW MSG: WIDll_RegisterCWSWAddinDll: szExeName = C:\WINNT\Microsoft.NET\Framework\v2.0.50727\regasm.exe "Q:\SLDWKS09.001\SolidWorks\CircuitWorksFull\cwswaddin.dll" /codebase /silent
    MSI (s) (AC:90) [12:57:26:781]: Doing action: register_i386_SldShellExtServerExe
    Action ended 12:57:26: Register_i386_CWSWAddinDll. Return value 1.
    Action start 12:57:26: register_i386_SldShellExtServerExe.
    MSI (s) (AC:90) [12:57:27:031]: Doing action: Register_i386_DotNet_DTSInterfaceDll
    Action ended 12:57:27: register_i386_SldShellExtServerExe. Return value 1.
    MSI (s) (AC:18) [12:57:27:187]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI10B.tmp, Entrypoint: WIDll_RegisterDTSInterfaceDll
    Action start 12:57:27: Register_i386_DotNet_DTSInterfaceDll.
     SW MSG: WI_GetProperty: INSTALLDIR = Q:\SLDWKS09.001\SolidWorks\ (0)
     SW MSG: WI_GetProperty: WindowsFolder = C:\WINNT\ (0)
     SW MSG: WIDll_RegisterDTSInterfaceDll: szExeName = "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\regasm.exe" "Q:\SLDWKS09.001\SolidWorks\swScheduler\DTSInterface.dll" /silent
    MSI (s) (AC:90) [12:57:43:421]: Skipping action: copy_HWDatabaseOnModify (condition is false)
    MSI (s) (AC:90) [12:57:43:421]: Doing action: run_UpdateBrowserDataNT_English
    Action ended 12:57:43: Register_i386_DotNet_DTSInterfaceDll. Return value 1.
    Action start 12:57:43: run_UpdateBrowserDataNT_English.
    MSI (s) (AC:90) [12:57:48:687]: Skipping action: run_SldSetDocProperties_NT (condition is false)
    MSI (s) (AC:90) [12:57:48:687]: Skipping action: set_AddAcadRxEntry (condition is false)
    MSI (s) (AC:90) [12:57:48:687]: Skipping action: Hasp_Install (condition is false)
    MSI (s) (AC:90) [12:57:48:687]: Doing action: set_XPHotFixInstall
    Action ended 12:57:48: run_UpdateBrowserDataNT_English. Return value 1.
    MSI (s) (AC:AC) [12:57:48:953]: Invoking remote custom action. DLL: C:\WINNT\Installer\MSI112.tmp, Entrypoint: WIDll_XPHotFixInstall
    Action start 12:57:48: set_XPHotFixInstall.
     SW MSG: Entering WIDll_XPHotFixInstall...
     SW MSG: WI_GetProperty: INSTALLDIR = Q:\SLDWKS09.001\SolidWorks\ (0)
     SW MSG: Q:\SLDWKS09.001\SolidWorks\setup\i386\x32\WindowsXP-KB919880-x86-ENU.exe
     SW MSG: The return value from Execute Command is : 1603
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: set_XP64HotFixInstall (condition is false)
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: set_VistaFileAssocCleanup (condition is false)
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: Uninst_Initialize (condition is false)
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: Uninst_UnInitialize (condition is false)
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: set_SolidworksSerialNumberProperty (condition is false)
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: set_EvalActivation (condition is false)
    MSI (s) (AC:90) [12:57:55:515]: Skipping action: set_EvalDeActivatio q n (condition is false)
    Action ended 12:57:55: set_XPHotFixInstall. Return value 1.
    Action ended 12:57:55: INSTALL. Return value 1.
    Thursday, July 9, 2009 7:33 PM
  • Hello,

    Try to install all the Visual C++ libraries natively both on the client and sequencer.

    I believe there are;
    Visual C++ 2005 SP1
    Visual C++ 2008 SP1
    Visual J# 2.0
    Visual J# 1.1

    /znack
    Thursday, July 9, 2009 7:37 PM
  • The VC 2005 libraries are one of the prereqs. I've tried installing them before sequencing.
    Thursday, July 9, 2009 7:49 PM
  • Would it be possible to install VSTA locally on the Sequencer before doing the actually Solidworks monitoring? And of course deploy it locally to the clients if the actual application then sequences successfully..

    Oh, btw, is that  C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\vsta.exe already existent in the system by some [earlier] process if Solidworks runs that as part of the installation?

    /Kalle
    Friday, July 10, 2009 7:22 PM
    Moderator
  • Hello,

    Yeah, VSTA is available as one of the PRE-REQs, check the folder prereqs on the dvd and it should look like this;
    MSSearch
    OfficeWeb
    VCRedist
    VSTA
    WindowsInstaller
    dotNetFx

    Insall dotnetfx, windows installer, vsta, vcredist and mssearch. I believe the officeweb can be sequenced if they are needed...

    /Znack
    Saturday, July 11, 2009 1:57 PM
  • As I stated in my original post, I tried a number of things, including installing all the prereqs before sequencing.

    I dug a bit deeper and the problem comes when the installer tries to register the VSTA application (vsta.exe  /hostid SolidWorks_VSTA /setup). I was able to get around this by taking the registry hives (HKLM\SOFTWARE\Microsoft\VSTAHOST and HKLM\SOFTWARE\Microsoft\VSTAHostConfig) from a working install and import it before I launch the setup program.

    For the record, Solidworks does not appear to be interested in supporting App-V. I'm currently trying to get a hold of someone beyond their first line tech support so that they're aware of this issue.
    Monday, July 13, 2009 3:12 PM
  • We're finally getting somewhere with the folks at SolidWorks. They're able to reproduce the problem but haven't found a solution yet.

    Monday, July 20, 2009 5:53 PM
  • This is my recipe

    Before installing the 4.5.1 sequencer

    1: Install updates from solidworks prereq folder. Should be 2 installers

    2: Make sure that c++ 2005 and Dot net framework is installed before installing the sequencer

    3: Install sequecner, create exception to exclude local settings from exclusion items and then select save as default so it keeps the setting.

    4: Install to q:\sworks09.v1

    5: You will have to export the network license portion of the registry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Solidworks

    6: Once exported change CurrentControlSet with ControlSet001 and save it.

    7: Run the reg file with the change and you should now see the solidworks service inside ControlSet001 in the registry.

    8: Make sure you make the service start Automaticlly !!!!!!!

    9: Now stop monitoring and make it FB1

    10: check the services tab and make sure services are set to Automatic as well.

    11: Copy file to content directory and give it a whirl.

    -Danny

    Tuesday, September 1, 2009 2:27 PM
  • You must unistall the vsta first!!!
    Thursday, September 1, 2011 6:05 AM