October 17, 2016
Dear Solid Edge Customer:
Solid Edge ST9 Microsoft Installer (MSI) Maintenance Pack 2 is available for download.
The Solid Edge Team
Microsoft Installer (MSI) Maintenance Packs – Solid Edge ST9 Maintenance Packs are delivered as and installed using Microsoft Installer (MSI) technology. Solid Edge MSI based Maintenance Packs are tracked as Installed Updates.
ST9 Maintenance Packs can be downloaded from:
Maintenance Pack .zip files are complete product setups. Therefore, existing versions must be
uninstalled using Uninstall a program from the Control Panel.
with a lesser version.
in MP1 and MP2.
been cases where the Disk Space Computation takes several minutes to complete. Please be patient.
Update was applied.
Product Update package, if any, must be available to allow the recovery of previous file versions.
After the current Update is uninstalled, the previous Update will become the current Update, if
there were multiple Updates installed.
updates -> Uninstall).
To receive direct e-mail notifications for new Solid Edge Maintenance Packs, subscribe to the SFBmail notification.
To initiate your subscription, navigate to: http://support.industrysoftware.automation.siemens.com/general/email.shtml for the web interface.
This Maintenance Pack addresses the following PRs:
PR 7769767: API function for extra window
PR 7796733: CommandCategories API in ST9 is no longer returning a full set of application commands
PR 7771616: Opened Part is not displayed
PR 7766292: Updating physical properties gives an error and Solid Edge freezes
PR 7774687: Unable to place companion flange for valves
PR 7778146: Not possible to select measurement variable in measure minimum distance.
PR 7788834: reproducible abort, when opening the relation list of a part
PR 7792303: Center Plane - command cannot be finished with the Enter key on the keyboard
PR 1983638: Sketches invisible, Highlight not working after pressing RMB
PR 7766545: Graphic Problems, when having several parts open in the same SE session
PR 7798046: Pattern of parts not oriented correctly
PR 7802414: Pathfinder does not do a Select highlight for graphically selected pattern
PR 7809270: Not getting Stress results case on non-manifold body in Simulation
PR 7594353: Linked geometry lost its connection to original parent
PR 7792385: Tabs incorrect if Assembly, Subassembly opened and Part in edit mode
PR 7810204: Override is applied for Drawing Views on copied asy using Ctrl+ steering wheel
PR 7763079: flat pattern view that disappeared on update
PR 7764032: Connector table doesn't match harness model
PR 7784594: an abort on close involving draft and PWD files
PR 7784887: Rotating front view does not result in correct drawing view
PR 7789410: Editing text and it crashes
PR 7800994: Break Line Type display changes to Straight Break when editing broken view
PR 7782097: Dimensions connected to auto centerlines go sick when opening a pre-V18 file
PR 7782097: Dimensions moves when Draft opened as inactive
PR 7811883: Zoom Area stops working if delete a drawing sheet
PR 7781896: The positions of View Scale are different in ST8
PR 7814032: Changing balloon styles always force split balloon
PR 7818067: Dimension tracker is not listing all balloons
PR 8314750: Shown parts hatch boundary logic
PR 8524496: change of display of drawing view and fill on open in inactive mode
PR 7775234: Solid Edge aborts placing holes
PR 7779469: Solid Edge aborted when creating a tab
PR 7794467: Cannot suppress pattern occurrences within selected region
PR 7753643: Missing Link between BendFaces in Flat Pattern and Bendfaces in Design Model
PR 7792766: SYNC PSM edit fails
PR 7792786: SYNC PSM- Cannot pull/create flange from the specified face
PR 7793010: ST9 files become unusable a frequent occurrence
PR 7802741: Save as flat does not save to registry key location
PR 7759158: Crashes leaving simulation-reproducible
PR 7746211: Abort in sheet metal
PR 7780176: Reverse Eng - SE foundation license contains reverse engineering feature
PR 7798340: Issues with Reverse Engineering when accessed through new template dialog
PR 7796037: Insight ST9 PL - inactivated parts of assembly indicates released status.
PR 7804090: Insight ST9 PL: Problem with automatic add of FolderMap.txt entries
PR 7785890: Impossible to type text in criteria field of Insight Web part Search
PR 7796292: Creation Date of a copied file will not be updated, if the file is write protect
PR 7804389: Rename action is not changing status to update on parent
PR 7806356: Where used not displaying results for folder having French characters
===Built-in Data Management===
PR 7796833: *.selock files are not getting sync'd with the Box file replication service
PR 7772952: Disable built-in data management check-out/check-in functionalities for DBSolidEdge
===Solid Edge SP, Server, Standalone Client, Solid Edge Client===
PR 7752047: SESP Content Browser - Part-Revisions listed in wrong order
PR 7784870: 'Solid edge stopped working' msg displayed after running SESPUpdateCallouts.exe
PR 7794999: Move command doesn't work (Hungarian)
PR 7807330: SESP EC crashes after executing 'Component structure Editor' command.
PR 8314760: Workflow screen not displaying with workflow carts option
===Teamcenter Integration for Solid Edge===
PR 7775430: SESE: SaveAS error when replacing the property value
PR 7795014: STRUCTURE EDITOR_ LINKED FILES NOT FOUND
PR 7817225: Missing custom attribute (Material) in Solid Edge ST9 managed mode
PR 8311265: SEEC: TC error when opening SE draft from RAC
PR 7800595: With TCExportDir set opening Solid Edge datasets from RAC not working correctly
PR 7804678: Add to Teamcenter with >1 block of SE docs prompts for login at each block
PR 7343219: Positions of part is incorrect when this assembly JT is imported in SE.
PR 7728401: Data Migration fails to create DV when booted into Russian
PR 7781964: Incorrect translation of title of Technical Requirements
PR 7774835: DwgIn: Dimensions properties for suppressed lines are ignored
Do we need to install Maintenance Pack 1 before 2? Or will they both be included in the latest pack?
Edit: Also does the latest ST9 install include the Maintenance Packs or are they all separate installs?
all Solid Edge Maintenance Packs are cumulativem that means, YOu only have to install the last one.
There only is one issue, that when You start with MP2 then there is no way for uninstalling MP2 and going back to MP1.
But I think this is not the big problem or issue
My SE ST9 user community is growing so, to save time, I need a way of automating the installation/uninstallation of SE. I also need a way of automating the installation of the maintenance packs as they emerge.
ST9 MP3 is nearing completion of the validation phase. MP3 should be available for download early next week.
If you will Google search "automating msi installs" you will find numerous articles and tools to help you build packages to deploy software remotely and or simply install an applicaiton silently.
There are also several companies that monitor this community site that have experience using tools to automate MSI installations to their user communities. Hopefully one or more of them will reply to you as well.
The MSI command line options for Solid Edge can be found in the Solid EDge readme.htm. Here are the basics:
The following is a complete command line argument set for silently installing Solid Edge. Silent install needs to run from an elevated cmd prompt (such as, command window "Run as Administrator"). Setup no longer supports the use of the ADDLOCAL property. All arguments should be encased in double quotes if there are spaces in the paths.
msiexec /i "J:\Solid Edge\Solid Edge ST9.msi" MYTEMPLATE=2 USERFILESPECXML="C:\temp\My Docs\SEAdmin\Options.xml" USERFILESPEC="C:\temp\My Docs\SEAdmin\selicense.dat" INSTALLDIR="C:\Program Files\Silent Solid Edge" /qn+ /l*v "C:\temp\mysilentsetup.log"
The string “J:\Solid Edge\Solid Edge ST9.msi" represents the fully qualified path to the Solid Edge MSI file.
The MSI Property MYTEMPLATE indicates which templates are to be installed. If no value is specified, Solid Edge uses the setting from the Standard.ini file. The default in the Standard.ini file is “Auto”. For “Auto”, the templates will set based on the current user’s “Region and Language Format” setting.
(2) JIS Metric
(3) ISO Metric
(4) ANSI Inch
(5) DIN Metric
(6) UNI Metric
(7) ESKD Metric
(8) GB Metric
(9) ANSI Metric
The MSI Property USERFILESPECXML allows the user to optionally install an SE Admin file. The user should supply a fully qualified path and filename.
The MSI Property USERFILESPEC allows the user to optionally provide a license file that setup will copy to the Solid Edge Program folder at the end of the setup.
The MSI Property INSTALLDIR is used to specify the installation folder for Solid Edge.
The argument "qn+" instructs the Windows installer to provide NO user interface and alert the user at the completion of the setup with a dialog box. Refer to the Windows help system for further information about Windows Installer arguments. Leaving this argument off the command line will display the setup user interface with selections made and fields provided. Note: if you are using this option some installations that require user interaction could fail.
The argument "l*v" tells the Windows installer to create a log file of important messages, warnings and errors and write it to the location provided, in this example, C:\temp\mysilentsetup.log. If you have silent install errors, please add the following argument to your command line and review the resulting log file. Please add: /L*v "%TEMP%\install.log"
Here are more instructions for using the /L option (note that the path MUST exist):
/L [i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] Log file
Writes logging information into a log file at the specified existing path. The path to the log file location must already exist. The installer does not create the directory structure for the log file. Flags indicate which information to log. If no flags are specified, the default is /l*.
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 file.
! - Flush each line to the log.
"*" - Wildcard, log all information except for the v and x options. To include the v and x options, specify "/l*vx".
The following is an example command line argument for silently installing the MSI Solid Edge MPs. Silent install needs to run from an administrator command window.
"C:\temp\” Solid_Edge_MSI_MPx.exe /s /v" /qn /l*v %temp%\mysilentupdate.log”
/s InstallShield switch that makes the InstallShield EXE run silent.
/v InstallShield switch that passes the string following it directly to the wrapped MSI installer.
/qn InstallShield switch for setting the user interface level. The q activates the UI level options, n is the option for “No UI”.
/l*v InstallShield switch that creates a log file of important messages, warnings and errors. This switch must be followed by the path and filename.
Be careful attempting to output a log file since MSI will not create folders if they don’t exist. So, if you want to create a log file set your path to a folder that exits, for exampleC:\temp\mysilentupdate.log, or as in the example above %TEMP%\mysilentupdate.log. Where %TEMP% is an existing environment variable that
points to an existing folder that is used to store temporary files. For example:
“c:\users\yourusername\local\appdata\temp” or “c:\temp”.
What is "C:\temp" doing in the following line?
"C:\temp\” Solid_Edge_MSI_MPx.exe /s /v" /qn /l*v %temp%\mysilentupdate.log”
That's what I was guessing but why the quotes (no spaces in the string) and the space before the msi file?