# Unable to launch MSI installers off NFS share

I have a Linux server where I've configured a read only NFS share. The client I'm currently working on is a Windows Server 2008 R2 machine that has the NFS features installed. I'm able to open and execute all files except any MSI file. For some reason, unless I map the drive to a drive letter, I am unable to execute MSI installers over this share (the installer works when copied locally but I'm trying to avoid this if at all possible). I get the following error when I try to execute it straight off a UNC path:

What could be causing this? What is it about mapping the share that makes it work?

EDIT - Here are the results when call on the MSI using msiexec with verbose logging:

=== Verbose logging started: 1/30/2014  10:12:29  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (80:F0) [10:12:29:228]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (80:F0) [10:12:29:228]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (80:34) [10:12:29:237]: Resetting cached policy values
MSI (c) (80:34) [10:12:29:237]: Machine policy value 'Debug' is 0
MSI (c) (80:34) [10:12:29:237]: ******* RunEngine:
******* Product: \\d-devfs02.domain.com\software\Nunit\NUnit-2.6.2.msi
******* Action:
******* CommandLine: **********
MSI (c) (80:34) [10:12:29:246]: Note: 1: 2203 2: \\d-devfs02.domain.com\software\Nunit\NUnit-2.6.2.msi 3: -2147024846
MSI (c) (80:34) [10:12:29:247]: MainEngineThread is returning 1620
=== Verbose logging stopped: 1/30/2014  10:12:29 ===

• This error message is a common result of an installer that has been truncated or corrupted in transit, and as such, I would suggest that for some reason, Windows is able to read the start of the file from the NFS share, but not all of it. – HopelessN00b Jan 29 '14 at 23:32
• What happens if you temporarily set the NFS share to allow all permissions to any? (Looking to find out if the failure is a result of the MSI execution process trying to unpack the MSI temporarily to the NFS share, but not being able to because it's read-only.) – HopelessN00b Jan 29 '14 at 23:40
• I strongly suspect you're running into an edge case w/ the NFS client and Windows Installer (msiexec.exe). I can't imagine Microsoft did a lot of testing of deployment of packages from NFS volumes. I'm fuzzy on the specifics, but I know that adding the "mapped" "drive" causes your requests to run through some more "plumbing" (the Multiple Provider Router layer, I believe) before making it down to the NFS redirector. I haven't written anything that interfaces w/ Windows at that level, though, to say with certainty (hence this being a comment rather than an answer). – Evan Anderson Jan 30 '14 at 0:06
• Yeah, I think msiexec is getting confused about the path during the file extraction. Does it make a difference if you run it as "msiexec /i path\to\your.msi"? – Katherine Villyard Jan 30 '14 at 0:25
• msiexec also has options for verbose logging, which might help troubleshoot. – Greg Bray Jan 30 '14 at 4:30