OpenDCL Forums

OpenDCL => Deployment => Topic started by: owenwengerd on April 05, 2009, 02:46:55 PM

Title: Re: deployment options..
Post by: owenwengerd on April 05, 2009, 02:46:55 PM
I've attached a VBScript example that performs a silent reinstall of the OpenDCL Runtime MSI by looking up the product code from the list of installed applications. Note that this won't work unless you installed from the runtime MSI, because the hard-coded UpgradeCode is from the runtime MSI. The same tactic can be used with the OpenDCL Studio MSI, but the UpgradeCode is different.
Title: Re: deployment options..
Post by: Fred Tomke on April 05, 2009, 11:53:21 PM
The other option is to specify the MSI file instead of the product code GUID.

Hm, that could be a solution. Specifing the MSI makes it possible to include a newer Runtime.MSI within a single Servicepack.exe along with other new files. If the ReleaseNumber of the copied MSI is newer than the installed release on the client computer (in a network environment) the MSI will be called to install (checking the release means to avoid that the MSI will be called at every start of our application).

Fred
Title: Re: deployment options..
Post by: BazzaCAD on April 06, 2009, 09:18:17 AM
I've attached a VBScript example that performs a silent reinstall of the OpenDCL Runtime MSI by looking up the product code from the list of installed applications. Note that this won't work unless you installed from the runtime MSI, because the hard-coded UpgradeCode is from the runtime MSI. The same tactic can be used with the OpenDCL Studio MSI, but the UpgradeCode is different.

Thanks Owen, looks good. But does this only work for reinstalls or for first time installs also?
Title: Re: deployment options..
Post by: owenwengerd on April 06, 2009, 11:13:51 AM
That only works for re-installs. First time installs must use the MSI file.
Title: Re: deployment options..
Post by: chairpak on June 15, 2009, 04:27:12 PM
Hello,
I have some new machines that are 64 bit running ACAD MEP 2010. I had just got all the ACAD MEP 2009 up and running using OpenDCL. I have not found a msi version (past or present) that installs correctly on these newer Dell Laptops. They are new and only have ACAD MEP on them outside of the usual windows and Internet softwares. Any suggestions?

Thank you in advance.
Title: Re: deployment options..
Post by: Kelie on June 15, 2009, 11:12:55 PM
Thanks Owen.
Title: Re: deployment options..
Post by: owenwengerd on June 15, 2009, 11:33:08 PM
I have not found a msi version (past or present) that installs correctly on these newer Dell Laptops.

What exactly does not work?
Title: Re: deployment options..
Post by: chairpak on June 16, 2009, 09:03:17 AM
System:
Windows XP Professional x64 Edition
Intel xeon 1.6 Ghz CPU
4GB Ram
ACAD MEP 2010

When installing 5.1.1.4 Runtime we get:
Error code 2356

When installing 5.1.1.5 Studio:
Error Code 2356

Then tolds to restart the installer again.
Title: Re: deployment options..
Post by: owenwengerd on June 16, 2009, 09:38:26 AM
Please try logging the installation and attach the log file (or email it to me at owenw@manusoft.com) so I can see where it's failing. Create the log file by running msiexec at the command prompt:

msiexec /log /i OpenDCL.Runtime.5.1.1.6.msi
Title: Re: deployment options..
Post by: BazzaCAD on June 16, 2009, 09:56:55 AM
I just updated my Studio from 5.1.1.5 to 5.1.1.6 on Win XP Pro (32 bit) with Acad 2008, 2009, 2010 installed & all seams fine.
Seams like it maybe a 64 bit issue our a vertical product issue....
Title: Re: deployment options..
Post by: chairpak on June 16, 2009, 11:32:54 AM
OK,

Ran the install from dos and it seemed to install correctly.
The log file was more like a help file and gave no stats of this machine.

I ran it twice thinking I may have mistyped the command but still get the same result.

Also, If there is a procedure that I could follow to do a manual install I would like to have that as well. I see that there is talk of a manual setup, but I have yet to actually find it.


Here is what the log looks like:


Windows ® Installer. V 4.5.6001.22159

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
   </package | /i> <Product.msi>
      Installs or configures a product
   /a <Product.msi>
      Administrative install - Installs a product on the network
   /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
      Advertises a product - m to all users, u to current user
   </uninstall | /x> <Product.msi | ProductCode>
      Uninstalls the product
Display Options
   /quiet
      Quiet mode, no user interaction
   /passive
      Unattended mode - progress bar only
   /q[n|b|r|f]
      Sets user interface level
      n - No UI
      b - Basic UI
      r - Reduced UI
      f - Full UI (default)
   /help
      Help information
Restart Options
   /norestart
      Do not restart after the installation is complete
   /promptrestart
      Prompts the user for restart if necessary
   /forcerestart
      Always restart the computer after installation
Logging Options
   /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
      i - Status messages
      w - Nonfatal warnings
      e - All error messages
      a - Start up of actions
      r - Action-specific records
      u - User requests
      c - Initial UI parameters
      m - Out-of-memory or fatal exit information
      o - Out-of-disk-space messages
      p - Terminal properties
      v - Verbose output
      x - Extra debugging information
      + - Append to existing log file
      ! - Flush each line to the log
      * - Log all information, except for v and x options
   /log <LogFile>
      Equivalent of /l* <LogFile>
Update Options
   /update <Update1.msp>[;Update2.msp]
      Applies update(s)
   /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
      Remove update(s) for a product
Repair Options
   /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
      Repairs a product
      p - only if file is missing
      o - if file is missing or an older version is installed (default)
      e - if file is missing or an equal or older version is installed
      d - if file is missing or a different version is installed
      c - if file is missing or checksum does not match the calculated value
      a - forces all files to be reinstalled
      u - all required user-specific registry entries (default)
      m - all required computer-specific registry entries (default)
      s - all existing shortcuts (default)
      v - runs from source and recaches local package
Setting Public Properties
   [PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.

Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.


Thank you is advance.
Title: Re: deployment options..
Post by: BazzaCAD on June 16, 2009, 02:49:22 PM
The help file popped up because you (& Owen :)) didn't do the arguments right. (I made the same mistake & read the help)
You'll note in the help file the /log is expecting a file name, where to put the log.

msiexec /log C:log.txt /i OpenDCL.Runtime.5.1.1.6.msi

then C:log.txt will be created...

Title: Re: deployment options..
Post by: chairpak on June 16, 2009, 04:21:41 PM
Sheesh... Thank you Bazzad.

I did a complete thrashing of any and all programs that were installed on the new laptop.
I then re-installed ACAD MEP 2010
I then re-installed OpenDCL 5.1.1.6 with no hick - ups

Everything is fine now. My dialogs work perfect.

Just a note to all: re-compile your odcl.lsp files and add to your code.

Thanks all for your help. Now I can play with the other new machines scattered all over the US.
Title: Re: deployment options..
Post by: owenwengerd on June 16, 2009, 07:57:49 PM
I'm glad you got it working. Sorry about the wild goose chase.