cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Magnus
Flexera beginner

msiexec properties gets corrupt when using command line

Hello
I am using msiexec arguments to set public msi properties. I have discovered that if I use many arguments, some of my properties will be corrupt.
I have not seen any documented limitations on the number of arguments or leght of the command line.

When using this command line:
"D:\Setup.exe" /v"REDUCED_UI=CLIENT_INSTALL SQLSRC=HCARNUNISQLDNP1\DELTAORN SQLCAT=DELTAORN_MAIN DASS="FqQ==" LIC_SERV=LOCALHOST END_DIAG=TRUE HIDE_LICENSE_AGREEMENT=FALSE HIDE_OS_REQ_WARNING_DIALOG=TRUE CTRL_SW=FALSE AD_ENCR=TRUE AD_ENCR_PORT=637 CLIENT_SRV_AD=UseDB DMC_ENCR=TRUE DMC_TRUST=FALSE IPADDR=10.1.1.2 SUMASK=255.255.255.0 MAX_SETUPEXEDIR_LENGTH=445 API_RVR_ENABLED=FALSE API_RVR_CERT=\"DELTAORN Server API\" API_RVR_TRUSTCERT=TRUE API_RVR_PORT=443 API_RVR_SESSIONKEEPALIVE=30 API_RVR_MAXCLIENTS=100 API_RVR_MAXSESSIONS=3 API_RVR_REGISTRYUPGRADECODE={DEB44969-6415-4C8D-A410-7B1904083861} API_AUT_ENABLED=FALSE API_AUT_TRUSTCERT=TRUE API_AUT_PORT=40516 API_AUT_MAXCLIENTS=100 API_AUT_MAXREQUESTS=100 API_AUT_REGISTRYUPGRADECODE=undefined API_SYS_PORT=40514 API_SC_ENABLED=FALSE API_SC_WSPORT=40513 API_SC_CERTIFICATE=\"DELTAORN Server API\" API_SC_TRUSTCERTIFICATE=TRUE API_SC_PORT=40514 API_AUT_CERT=\"DELTAORN Server API\" API_SC_SESSIONKEEPALIVE=30 API_SC_MAXCLIENTS=100 API_SC_MAXREQUESTS=100 API_SC_MAXSESSIONS=3 API_SC_REGISTRYUPGRADECODE=undefined API_RVR_MAXREQUESTS=100"


This property will be corrupt:
API_SC_CERTIFICATE: DELTAO?? Server API

(See also attached image)

If I reduce the number of arguments, the installation works fine.

Does anyone know what limitation causes this behavior? Or if there are any other reason behind this behavior.

Regards
Magnus
Labels (1)
0 Kudos
1 Reply
banna_k
Intrepid explorer

Re: msiexec properties gets corrupt when using command line

@Magnus :

Looks like this issue has been fixed in IS2018 release.

IS2016, there were a limitation in number of character passed in command line parameter.

Check IS 2018 release note  for more information : https://helpnet.flexerasoftware.com/installshield24helplib/rn/ReleaseNotes.htm#isreleasenotes_263079...

 

IOJ-1823277

Calling a Basic MSI setup launcher from a command prompt and including parameters where the entire command exceeds 752 characters results in a “Setup Launcher Unicode Has Stopped Working” error. Although the error is seen, the MSI still launches and does contain all of the properties passed on the command line.

 

 

0 Kudos