Hello,
when I try to start an MSI installation from the network, I get the following log file on some machines:
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.
Error 2303 (could not get volume info)
Started by
Matthias1967
, Feb 03 2010 14:06
1 reply to this topic
Posted 03 February 2010 - 14:06
QUOTE |
=== Verbose logging started: 02/02/2010 11:16:58 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINDOWS\system32\MSIEXEC.EXE === MSI © (30:38) [11:16:58:591]: Resetting cached policy values MSI © (30:38) [11:16:58:591]: Machine policy value 'Debug' is 0 MSI © (30:38) [11:16:58:591]: ******* RunEngine: ******* Product: \\.host\Shared Folders\G\CompShares\xxxxxxxDsk\xxxxxx\Master\CurVer\yyyyyyyyyyyyyyyyyyyyyy\zzzzzz\xxx\MyProduct.msi ******* Action: ******* CommandLine: ********** MSI © (30:38) [11:16:58:747]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI © (30:38) [11:16:58:779]: Machine policy value 'DisableUserInstalls' is 0 MSI © (30:38) [11:16:58:826]: Note: 1: 2303 2: 144 3: \\.host\Shared Folders\ MSI © (30:38) [11:16:58:826]: Note: 1: 2303 2: 144 3: \\.host\Shared Folders\ MSI © (30:38) [11:16:58:826]: Note: 1: 1325 2: CompShares MSI © (30:38) [11:16:58:826]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI © (30:38) [11:16:58:826]: MainEngineThread is returning 2 === Verbose logging stopped: 02/02/2010 11:16:58 === |
(this is from a VM, but it also happens over actual networks)
For me this means that msiexec tries to locate the MSI file and cannot get volume info (2303). Then it complains about a part of the path that does not fit into 8.3 (1325).
This happens only on some client machines, on other machines (using the same network drive as source) installation works fine.
Unfortunately, I have no clue why this happens. Any ideas?
Regards,
Matthias
Posted 10 February 2010 - 13:05
I saw that a long time ago, on systems having drive mappings on Novell Netware servers.
My explanation was that Windows Installer evaluates all drive letters, to figure out which drives are suitable for installing the software (therefore you will not see your CD-ROM drive). Apparently the driver on the local computer, responsible for that particular mapping, does not supply the information requested by Windows Installer.
My explanation was that Windows Installer evaluates all drive letters, to figure out which drives are suitable for installing the software (therefore you will not see your CD-ROM drive). Apparently the driver on the local computer, responsible for that particular mapping, does not supply the information requested by Windows Installer.