Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Invalid Command Line Error


13 replies to this topic

mimar

mimar
  • Members
  • 4 posts

Posted 27 July 2004 - 23:35

I have a question...some of my setups fail with the error "invalid command line" returned by the MSI engine. I managed to isolate some of the systems this was happening on - users without admin rights, for instance seemed to cause this error. But now I have another verbose log, in which everything looks proper; albeit the error is "invalid command line".

Is there a way to extract more information from the MSI engine as to what exactly it didn't like, or is it pretty much hit-or-miss? I searched on the web and found that this can be caused by a very wide variety of things, such as:

- quotes in paths
- quotes in user/company names
- improper environment variables
- using a mapped drive as install source

I am hoping there might be a way to make more educated guesses on why this error might occur.
Any advice?

luke_s

luke_s
  • Full Members
  • 532 posts

Posted 28 July 2004 - 00:50

I dont think that you can extract any more information. You could try looking at the event viewer, maybe that has some extra detail.



Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 28 July 2004 - 03:59

The msiexec is picky, I think it will complain about spaces in the command line for example. I'd check that first.
Regards
-Stein Åsmul

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 28 July 2004 - 07:19

Could you post a quote from the verbose log file that shows which command line msiexec is seeing?

mimar

mimar
  • Members
  • 4 posts

Posted 28 July 2004 - 15:44

Stefan,

Here is the complete log. Thanks!

=== Verbose logging started: 26/07/2004 16:16:30 Build type: SHIP UNICODE 2.00.2600.1106 Calling process: C:\DOCUME~1\albatati\Local Settings\Temp\miaCE.tmp\mia.exe ===
MSI © (D8:D8): Resetting cached policy values
MSI © (D8:D8): Machine policy value 'Debug' is 0
MSI © (D8:D8): ******* RunEngine:
******* Product: C:\DOCUME~1\albatati\Local Settings\Temp\mia1\mia.msi
******* Action:
******* CommandLine: **********
MSI © (D8:D8): Client-side and UI is none or basic: Running entire install on the server.
MSI © (D8:D8): Grabbed execution mutex.
MSI © (D8:D8): Cloaking enabled.
MSI © (D8:D8): Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (98:70): Resetting cached policy values
MSI (s) (98:70): Machine policy value 'Debug' is 0
MSI (s) (98:70): ******* RunEngine:
******* Product: C:\DOCUME~1\albatati\Local Settings\Temp\mia1\mia.msi
******* Action:
******* CommandLine: **********
MSI (s) (98:70): Machine policy value 'DisableUserInstalls' is 0
MSI (s) (98:70): Setting cached product context: User non-assigned for product: 41A69EC62E16CC8438E72217A059A3ED
MSI (s) (98:70): Using cached product context: User non-assigned for product: 41A69EC62E16CC8438E72217A059A3ED
MSI (s) (98:70): Setting cached product context: User non-assigned for product: 5A7C44FC50754E14EB489A4A9277BA50
MSI (s) (98:70): Using cached product context: User non-assigned for product: 5A7C44FC50754E14EB489A4A9277BA50
MSI (s) (98:70): Setting cached product context: User non-assigned for product: 6FE09FA69F7FC664994F714728F6BB04
MSI (s) (98:70): Using cached product context: User non-assigned for product: 6FE09FA69F7FC664994F714728F6BB04
MSI (s) (98:70): Setting cached product context: User non-assigned for product: 98154D9215813D11F8DE723CF4D17D87
MSI (s) (98:70): Using cached product context: User non-assigned for product: 98154D9215813D11F8DE723CF4D17D87
MSI (s) (98:70): Setting cached product context: User non-assigned for product: FB127F1FC040690489A8D10BE17BB3C0
MSI (s) (98:70): Using cached product context: User non-assigned for product: FB127F1FC040690489A8D10BE17BB3C0
MSI (s) (98:70): Setting cached product context: machine assigned for product: 06E9C39A6B92ad94AB127FA06CAAED02
MSI (s) (98:70): Using cached product context: machine assigned for product: 06E9C39A6B92ad94AB127FA06CAAED02
MSI (s) (98:70): Setting cached product context: machine assigned for product: 0B79C053C7D38EE4AB9A00CB3B5D2472
MSI (s) (98:70): Using cached product context: machine assigned for product: 0B79C053C7D38EE4AB9A00CB3B5D2472
MSI (s) (98:70): Setting cached product context: machine assigned for product: 0DBA73CF8012beb40B0121450E66B2A5
MSI (s) (98:70): Using cached product context: machine assigned for product: 0DBA73CF8012beb40B0121450E66B2A5
MSI (s) (98:70): Setting cached product context: machine assigned for product: 19F4AD9090A22324BAC8B67C0490D63E
MSI (s) (98:70): Using cached product context: machine assigned for product: 19F4AD9090A22324BAC8B67C0490D63E
MSI (s) (98:70): Setting cached product context: machine assigned for product: 20CC412817268CD48BDD779933542046
MSI (s) (98:70): Using cached product context: machine assigned for product: 20CC412817268CD48BDD779933542046
MSI (s) (98:70): Setting cached product context: machine assigned for product: 216DB45C19C924345B921D77EC8B0C3C
MSI (s) (98:70): Using cached product context: machine assigned for product: 216DB45C19C924345B921D77EC8B0C3C
MSI (s) (98:70): Setting cached product context: machine assigned for product: 245B89384CC39D4438FD96C6EC0721B4
MSI (s) (98:70): Using cached product context: machine assigned for product: 245B89384CC39D4438FD96C6EC0721B4
MSI (s) (98:70): Setting cached product context: machine assigned for product: 29FE602138E29584CABC02843CBCD76A
MSI (s) (98:70): Using cached product context: machine assigned for product: 29FE602138E29584CABC02843CBCD76A
MSI (s) (98:70): Setting cached product context: machine assigned for product: 2BB0C01793EFE484BB329C9B86531AA4
MSI (s) (98:70): Using cached product context: machine assigned for product: 2BB0C01793EFE484BB329C9B86531AA4
MSI (s) (98:70): Setting cached product context: machine assigned for product: 38A9FAE519B3FB54F8D299B0EBDB9CBA
MSI (s) (98:70): Using cached product context: machine assigned for product: 38A9FAE519B3FB54F8D299B0EBDB9CBA
MSI (s) (98:70): Setting cached product context: machine assigned for product: 41858184422Aa74418AD17DB0285E0B1
MSI (s) (98:70): Using cached product context: machine assigned for product: 41858184422Aa74418AD17DB0285E0B1
MSI (s) (98:70): Setting cached product context: machine assigned for product: 5C9A346DAAAE1864E8EDB643263FCA3E
MSI (s) (98:70): Using cached product context: machine assigned for product: 5C9A346DAAAE1864E8EDB643263FCA3E
MSI (s) (98:70): Setting cached product context: machine assigned for product: 6350C2CFC3850c6448A426ECAC0EF122
MSI (s) (98:70): Using cached product context: machine assigned for product: 6350C2CFC3850c6448A426ECAC0EF122
MSI (s) (98:70): Setting cached product context: machine assigned for product: 667FCD348386A9F4C8199DD25A68FD7A
MSI (s) (98:70): Using cached product context: machine assigned for product: 667FCD348386A9F4C8199DD25A68FD7A
MSI (s) (98:70): Setting cached product context: machine assigned for product: 687A92B33085e9e4B98503415A4B5E91
MSI (s) (98:70): Using cached product context: machine assigned for product: 687A92B33085e9e4B98503415A4B5E91
MSI (s) (98:70): Setting cached product context: machine assigned for product: 68AB67CA330100007706000000000010
MSI (s) (98:70): Using cached product context: machine assigned for product: 68AB67CA330100007706000000000010
MSI (s) (98:70): Setting cached product context: machine assigned for product: 7CC4146D512FF764881B45E68D363FB5
MSI (s) (98:70): Using cached product context: machine assigned for product: 7CC4146D512FF764881B45E68D363FB5
MSI (s) (98:70): Setting cached product context: machine assigned for product: 806763CD7A467FB4294FB8AA52AB20BD
MSI (s) (98:70): Using cached product context: machine assigned for product: 806763CD7A467FB4294FB8AA52AB20BD
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9040110900063D11C8EF10054038389C
MSI (s) (98:70): Using cached product context: machine assigned for product: 9040110900063D11C8EF10054038389C
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9040150900063D11C8EF10054038389C
MSI (s) (98:70): Using cached product context: machine assigned for product: 9040150900063D11C8EF10054038389C
MSI (s) (98:70): Setting cached product context: machine assigned for product: 90401A0900063D11C8EF10054038389C
MSI (s) (98:70): Using cached product context: machine assigned for product: 90401A0900063D11C8EF10054038389C
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9040710900063D11C8EF10054038389C
MSI (s) (98:70): Using cached product context: machine assigned for product: 9040710900063D11C8EF10054038389C
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9040B30900063D11C8EF10054038389C
MSI (s) (98:70): Using cached product context: machine assigned for product: 9040B30900063D11C8EF10054038389C
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9399EE5EF9522ED40832C5941EA6F434
MSI (s) (98:70): Using cached product context: machine assigned for product: 9399EE5EF9522ED40832C5941EA6F434
MSI (s) (98:70): Setting cached product context: machine assigned for product: 95C67D3D6587FCF4B9458509ECF03F3F
MSI (s) (98:70): Using cached product context: machine assigned for product: 95C67D3D6587FCF4B9458509ECF03F3F
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9CFA723DAAB7A3743891E67B0A4D1083
MSI (s) (98:70): Using cached product context: machine assigned for product: 9CFA723DAAB7A3743891E67B0A4D1083
MSI (s) (98:70): Setting cached product context: machine assigned for product: 9E9B2E211B50d7040BDF5B3F05351552
MSI (s) (98:70): Using cached product context: machine assigned for product: 9E9B2E211B50d7040BDF5B3F05351552
MSI (s) (98:70): Setting cached product context: machine assigned for product: A4B3B7B3C8FA17649AE2E3E7A9CB2BB2
MSI (s) (98:70): Using cached product context: machine assigned for product: A4B3B7B3C8FA17649AE2E3E7A9CB2BB2
MSI (s) (98:70): Setting cached product context: machine assigned for product: A8D075F928E34234098909187D14DDD7
MSI (s) (98:70): Using cached product context: machine assigned for product: A8D075F928E34234098909187D14DDD7
MSI (s) (98:70): Setting cached product context: machine assigned for product: BCE9955B27ADEE34A803C20893F68FBB
MSI (s) (98:70): Using cached product context: machine assigned for product: BCE9955B27ADEE34A803C20893F68FBB
MSI (s) (98:70): Setting cached product context: machine assigned for product: BF8EE74E0CCA806458C9E482151BA8A6
MSI (s) (98:70): Using cached product context: machine assigned for product: BF8EE74E0CCA806458C9E482151BA8A6
MSI (s) (98:70): Setting cached product context: machine assigned for product: CABF2C13FC763904F863511A64167374
MSI (s) (98:70): Using cached product context: machine assigned for product: CABF2C13FC763904F863511A64167374
MSI (s) (98:70): Setting cached product context: machine assigned for product: CD2F893A607D2bb4CA835523DC22D980
MSI (s) (98:70): Using cached product context: machine assigned for product: CD2F893A607D2bb4CA835523DC22D980
MSI (s) (98:70): Setting cached product context: machine assigned for product: CD5DA6254CFCa2f448248CC49CD1C6F7
MSI (s) (98:70): Using cached product context: machine assigned for product: CD5DA6254CFCa2f448248CC49CD1C6F7
MSI (s) (98:70): Setting cached product context: machine assigned for product: D36577651BC0f584E9815C203560BBF3
MSI (s) (98:70): Using cached product context: machine assigned for product: D36577651BC0f584E9815C203560BBF3
MSI (s) (98:70): Setting cached product context: machine assigned for product: D822AB7C9E0D5E440B6BA74D0B6DBE0B
MSI (s) (98:70): Using cached product context: machine assigned for product: D822AB7C9E0D5E440B6BA74D0B6DBE0B
MSI (s) (98:70): Setting cached product context: machine assigned for product: DDE7F2BCF1D91C3409CFF425AE1E271A
MSI (s) (98:70): Using cached product context: machine assigned for product: DDE7F2BCF1D91C3409CFF425AE1E271A
MSI (s) (98:70): Setting cached product context: machine assigned for product: E1BF586C5A82E154FB41959C8A73A7A9
MSI (s) (98:70): Using cached product context: machine assigned for product: E1BF586C5A82E154FB41959C8A73A7A9
MSI (s) (98:70): Setting cached product context: machine assigned for product: E4C56ECF8E0BDBF4DA61DEBC6EDC95F1
MSI (s) (98:70): Using cached product context: machine assigned for product: E4C56ECF8E0BDBF4DA61DEBC6EDC95F1
MSI (s) (98:70): Setting cached product context: machine assigned for product: E9A3F9443099d0a42A908030D0549A53
MSI (s) (98:70): Using cached product context: machine assigned for product: E9A3F9443099d0a42A908030D0549A53
MSI (s) (98:70): Setting cached product context: machine assigned for product: F1B4AA19819Bb0e43A408F4DCED57762
MSI (s) (98:70): Using cached product context: machine assigned for product: F1B4AA19819Bb0e43A408F4DCED57762
MSI (s) (98:70): Setting cached product context: machine assigned for product: F56FE4FE26D47D44289CA1CEBC7AC405
MSI (s) (98:70): Using cached product context: machine assigned for product: F56FE4FE26D47D44289CA1CEBC7AC405
MSI (s) (98:70): Setting cached product context: machine assigned for product: FC6B5F6CC906E82478F6AC3871C620B1
MSI (s) (98:70): Using cached product context: machine assigned for product: FC6B5F6CC906E82478F6AC3871C620B1
MSI (s) (98:70): File will have security applied from OpCode.
MSI (s) (98:70): SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\DOCUME~1\albatati\Local Settings\Temp\mia1\mia.msi' against software restriction policy
MSI (s) (98:70): Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (98:70): SOFTWARE RESTRICTION POLICY: C:\DOCUME~1\albatati\Local Settings\Temp\mia1\mia.msi is not digitally signed
MSI (s) (98:70): SOFTWARE RESTRICTION POLICY: C:\DOCUME~1\albatati\Local Settings\Temp\mia1\mia.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (98:70): End dialog not enabled
MSI (s) (98:70): Original package ==> C:\DOCUME~1\albatati\Local Settings\Temp\mia1\mia.msi
MSI (s) (98:70): Package we're running from ==> C:\WINDOWS\Installer\434e73c.msi
MSI (s) (98:70): APPCOMPAT: looking for appcompat database entry with ProductCode '{DB56DBEB-2985-4BEF-A157-2E9085B56CDE}'.
MSI (s) (98:70): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (98:70): Machine policy value 'TransformsSecure' is 0
MSI (s) (98:70): User policy value 'TransformsAtSource' is 0
MSI (s) (98:70): APPCOMPAT: looking for appcompat database entry with ProductCode '{DB56DBEB-2985-4BEF-A157-2E9085B56CDE}'.
MSI (s) (98:70): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (98:70): Transforms are not secure.
MSI (s) (98:70): Command Line: ADDLOCAL=ALL ALLUSERS=2 ARPSYSTEMCOMPONENT=1 ARPNOREMOVE=1 ARPNOMODIFY=1 ARPNOREPAIR=1 SRCDIR=C:\PROGRA~1\COMMON~1\MimarSinan\InstallAware
MSI (s) (98:70): Product Code passed to Engine.Initialize: ''
MSI (s) (98:70): Product Code from property table before transforms: '{DB56DBEB-2985-4BEF-A157-2E9085B56CDE}'
MSI (s) (98:70): Product Code from property table after transforms: '{DB56DBEB-2985-4BEF-A157-2E9085B56CDE}'
MSI (s) (98:70): Product not registered: beginning first-time install
MSI (s) (98:70): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (98:70): User policy value 'SearchOrder' is 'nmu'
MSI (s) (98:70): Adding new sources is allowed.
MSI (s) (98:70): Package name extracted from package path: 'mia.msi'
MSI (s) (98:70): Package to be registered: 'mia.msi'
MSI (s) (98:70): Note: 1: 2205 2: 3: Error
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2729
MSI (s) (98:70): Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (98:70): Machine policy value 'DisableMsi' is 0
MSI (s) (98:70): Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (98:70): User policy value 'AlwaysInstallElevated' is 0
MSI (s) (98:70): Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (98:70): Running product '{DB56DBEB-2985-4BEF-A157-2E9085B56CDE}' with elevated privileges: Product is assigned.
Info 1639. Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
INSTALLATION
MSI (s) (98:70): MainEngineThread is returning 1639
MSI © (D8:D8): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI © (D8:D8): MainEngineThread is returning 1639
=== Verbose logging stopped: 26/07/2004 16:16:39 ===

RobertDickau

RobertDickau
  • Members
  • 29 posts

Posted 28 July 2004 - 18:40

You might need to set the Debug policy to 7 in order for command lines to appear in the log file; please see the MSI Help Library page "Debug". (And the command line will appear within the first several lines of the log file, so you could perhaps post just those in the future...)
Robert Dickau
InstallShield, a Macrovision company
InstallShield training, books, seminars, newsletters, ...

mimar

mimar
  • Members
  • 4 posts

Posted 28 July 2004 - 19:07

The command line already appears in the log:

MSI (s) (98:70): Command Line: ADDLOCAL=ALL ALLUSERS=2 ARPSYSTEMCOMPONENT=1 ARPNOREMOVE=1 ARPNOMODIFY=1 ARPNOREPAIR=1 SRCDIR=C:\PROGRA~1\COMMON~1\MimarSinan\InstallAware

As you can see, the problem is not the command line.
The problem is, Windows Installer is returning this error for things other than the command line.

Example: install on a system where no admin priviledges exist returns the same error.

I am trying to find the real cause of the error, which is why I pasted the entire log.

Any ideas?

luke_s

luke_s
  • Full Members
  • 532 posts

Posted 28 July 2004 - 23:42

What did you set the logging to?? It doesnt look like a full verbose log to me.

Try using msiexec /I <msifile.msi> /L*V c:\mymsilog.txt

Does your install work ok if you dont specify any command line? If yes, then try running the install by adding just one command line argument at a time. This might help identify the problem.

To Follow Robert's advise, open the key -

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer

Create a value (DWORD) called "Debug" and give it a value of 7.

You might be able to do this inside gpedit.msc but the registry was easier for me.


mimar

mimar
  • Members
  • 4 posts

Posted 29 July 2004 - 02:03

Its a full verbose log. Please notice how near the top it says "verbose logging started @...".

I am installing using an external UI, so the external UI kicks off the installer. It does not kick off the installer from the command line using MSIExec, but by using APIs.

There is no need to follow Robert's advice, as I have already captured the full command line passed to the engine. Please see my prior post for the full command line.

The Windows Installer engine complains that the command line is invalid only on a very limited number of systems, where there is actually _another_ problem. Like I said earlier, the problem can be caused by many unrelated things:

- quotes in user names
- lack of sufficient priviledges
- mis-set environment variables

What I am trying to understand here is NOT how to capture the command line or pass the correct command line. I know my command line is correct. Unfortunately, on a very limited number of systems, which I do not have access to, the engine reports this _misleading error_ which has also misguided the replies on this helpful forum so far.

What I am really trying to understand is:

- whether there is any information in the log at all, that may yield the correct cause of the error
- whether there is any other thing I can check for, to provide insight on the error
- whether there is a known list of errors that are known to cause windows installer to fail with "bad command line"

I am repeating myself, but just to be 100% clear, my search on the web indicated that the invalid command line error can occur when any of the following are the case:

- quotes in user names
- lack of sufficient priviledges
- mis-set environment variables

Please notice that these issues have _nothing_ to do with the command line being good or bad. It is simply the engine reporting a misleading error.

I hope I have been better at explaining the problem now...please, any assistance is much appreciated.

Sinan

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 29 July 2004 - 10:15

I have no direct answers to your questions. However I want to emphasisze that you should set the Debug policy to 7. Only this will ensure that the verbatim command line parameters are written to the log. The later "Command Line" entry in the log strips quotes for instance.

didier

didier
  • Members
  • 2 posts

Posted 14 September 2004 - 21:27

Hi,

I have the same problem when I'm doing upgrade from CD. The strange thing is that it's appearing only on NT OS family machines.
When I run upgrade from network or local disk, everything is ok.

I read articles about problem with readme dialog. It is possible?

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 16 September 2004 - 08:25

Another posiible reason is if you perform an AppSearch for a registry entry that returns a multi-line string, like the PendingFileRenameOperations entry for instance.

didier

didier
  • Members
  • 2 posts

Posted 16 September 2004 - 12:30

Yesterday I found reason of my problem.

During my upgrade I'm searching for some binary registry keys using RegLocator and AppSearch.

When upgrade is running
- under NT family OS and
- from CD and
- searched reg key is BINARY type,
than Windows installer will always retun strange value, i think that it is \0.

This value is passed to previous version of my msi ( when uninstalling during upgrade) by command line.

"Strange founded value \0" passed to command line will cause Invalid syntax command line parameter.

So I change my reg value to STRING type using custom action and everything is ok.

I think that this is a problem of Windows Installer for NT.

angus

angus
  • Members
  • 1 posts

Posted 30 June 2005 - 14:33

I had similar problems installing VS .Net 2003... This happened because I had quotes in my company name!

Angus