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
‎Dec 03, 2010
06:46 PM
Error: -1639 Invalid command line argument
Hello,
I have an Installscript MSI project which has been working fine. Today, it errors just before the feature transfer begins with "Error: -1639 Invalid command line argument. Consult the Windows Installer SDK for detailed command line help".
I have no idea what I've done that's caused this; the only argument I am passing to the msi file is verbose logging. The log gets created, and it's not clear to me what to look for within.
I haven't found any instances of this on the forum that apply to my situation (so far as I can tell). Can anyone suggest something to check, perhaps something in the log file? I have for the moment hit a wall.
Thanks very much.
I have an Installscript MSI project which has been working fine. Today, it errors just before the feature transfer begins with "Error: -1639 Invalid command line argument. Consult the Windows Installer SDK for detailed command line help".
I have no idea what I've done that's caused this; the only argument I am passing to the msi file is verbose logging. The log gets created, and it's not clear to me what to look for within.
I haven't found any instances of this on the forum that apply to my situation (so far as I can tell). Can anyone suggest something to check, perhaps something in the log file? I have for the moment hit a wall.
Thanks very much.
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 05, 2010
12:27 AM
Might there be spaces or special characters in the string?
Have you tried putting quotes around the command line argument?
Have you tried putting quotes around the command line argument?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 07, 2010
12:50 PM
Thanks for that response. However, I added quotes, even removed the darn command, and still the feature transfer error occurs.
I've attached the log file in case anyone would be so kind as to have a look. I'm not expert at interpreting the verbose logs, but this one is telling me nothing... :confused:
I've attached the log file in case anyone would be so kind as to have a look. I'm not expert at interpreting the verbose logs, but this one is telling me nothing... :confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 14, 2010
02:52 PM
Thanks very much for that suggestion! I had [$Documentation} in the Add/Remove programs section of the IDE. Alas, the error still occurs after correcting it to [$Documentation].
Thanks again for the link.
Thanks again for the link.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 27, 2011
01:49 PM
For anyone who encounters this, the problem in my case was consecutive semi-colons (i.e., ";;") in the SecureCustomProperties MSI property; removing one resolved the issue.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)