This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Error 1639. Invalid command line argument.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2011
04:58 AM
Error 1639. Invalid command line argument.
On a customer's computer we encounter with all our setups Error 1639.
Verbose log (setup.txt) attached.
We would appreciate any advises.
Verbose log (setup.txt) attached.
We would appreciate any advises.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2011
07:53 AM
Hello,
I've had the 1639 error before. Here is one possible way to track down the problem. Look in your log file on the line:
and parse that into all the different variables (one per line). In the case of the log you attached, it would look something like this:
*snip*
It looks like your customer is putting double quotes around the COMPANYNAME and USERNAME fields which is causing your problem. Instead of typing
have them try just
I was able to reproduce your issue using double quotes in the user/company names and it worked fine without.
HTH
I've had the 1639 error before. Here is one possible way to track down the problem. Look in your log file on the line:
1: Ready to launch MsiInstallProduct, Command line :
and parse that into all the different variables (one per line). In the case of the log you attached, it would look something like this:
Command line :
ADDLOCAL=Program
AFMG="C:\Program Files (x86)\AFMG\"
ALLUSERS=1
ALLUSERSPROFILE=C:\ProgramData\
ARPPRODUCTICON=ARPPRODUCTICON.exe
ARPURLINFOABOUT=http://www.afmg.eu
COMPANYNAME=""Merrick&Co.""
DWUSINTERVAL=30
*snip*
USERNAME=""Merrick&Co.""
USERPROFILE=C:\Users\sarni\
_Modify=""
ARPSYSTEMCOMPONENT=1
ISSETUPDRIVEN=1
It looks like your customer is putting double quotes around the COMPANYNAME and USERNAME fields which is causing your problem. Instead of typing
"Merrick&Co."
have them try just
Merrick&Co.
I was able to reproduce your issue using double quotes in the user/company names and it worked fine without.
HTH
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2011
09:35 AM
Thanks so far.
There is no Company/User Name dialog in the setup.
The question is from where the names are retrieved.
I have read that the default company name is retrieved from the registry key
HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info .
Such a key exist on my machine but not on the customer's one.
There is no Company/User Name dialog in the setup.
The question is from where the names are retrieved.
I have read that the default company name is retrieved from the registry key
HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info .
Such a key exist on my machine but not on the customer's one.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2011
09:41 AM
If that's the case, you might need to change (at least temporarily) the following registry keys before you try installing:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\
RegisteredOrganization
RegisteredOwner
HTH
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\
RegisteredOrganization
RegisteredOwner
HTH
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2011
11:24 AM
Yes, removing the quotes from
RegisteredOrganization
RegisteredOwner
did the trick.
Thanks once more.
RegisteredOrganization
RegisteredOwner
did the trick.
Thanks once more.