EFLOW - Cannot run Deploy-Eflow through powershell about iotedge-eflow HOT 4 CLOSED

Okay, so a bit more info:
The two reg values eflowBaseDir and eflowVhdxDir had not been set for some reason. I had not edited anything in regedit at any point in time, until now.

After setting eflowBaseDir to "C:\Program Files\Azure IoT Edge" and eflowVhdxDir to "C:\iotedge\vm" (I had thought the permission issues where happening here, thats why I changed it, and I didn't know what else to set), it managed to continue from where it failed previously.

Now though, it started failing when trying to locate the images that should have been located in that folder. For some reason, I found AzureIoTEdgeForLinux-v1.cab and AzureIoTEdgeForLinux-v1.vhdx in the root of my program data folder. After moving them to "C:\iotedge\vm", it managed to continue even further, although now it fails in another step.

I will now try to uninstall everything (again), clear the reg, and try to reinstall Eflow and redeploy. Hopefully, that will fix the next issue as well.. I will post how that goes soon.

from iotedge-eflow.

Same issue arrises. So I fixed it by creating a folder called vm ("C:\Program Files\Azure IoT Edge\vm"), moving "AzureIoTEdgeForLinux-v1.cab" to that directory and modifying eflowVhdxDir in the registry to point to that location. Then it works... Until it needs to instantiate the VM. Then it fails with the following error:

C:\Program Files\Azure IoT Edge\nodectl.exe compute virtualmachine create --config "C:\Program Files\Azure IoT Edge\\yaml\cloudvm.yaml" failed to execute [Error: rpc error: code = Unknown desc = executePowershell failed with error new-vm : 'XXX-EFLOW' failed to add resources to 'XXX-EFLOW'. Failed to set folder permission. Verify that the host machine account has read/write access to the share. Failed to set security info. 'XXX-EFLOW' failed to add resources. (Virtual machine ID AE70119B-F4B8-41B5-A36A-3919F45D1929) 'XXX-EFLOW' failed to set folder permission for C:\Program Files: Access is denied. (0x80070005). Verify that the 'XXX' machine account has read/write access to the share. (Virtual machine ID AE70119B-F4B8-41B5-A36A-3919F45D19 29) Failed to set security info for 'C:\Program Files': 'Access is denied.'('0x80070005'). At line:24 char:10 + ... $vm = new-vm -Name $vmName -MemoryStartupBytes $memory -BootDev ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [New-VM], VirtualizationException + FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.NewVM : exit status 1] at line 2289

Seems like it is trying to change permissions for the Program Files folder.

After rereading the docs, I found out that I could change those directories during installation. Note that I had not done that previously, all paths had been default paths.

After running the installer with the following parameters, everything worked as expected.

INSTALLDIR="C:\iotedge", VHDXDIR="C:\iotedge\vm"

So I was able to install eflow and then immediately run Deploy-Eflow, and everything ran as expected.

from iotedge-eflow.

@ericvruder,

I am glad that you were able to get over the hurdle by specifying a different install directory. I initially thought that perhaps you were running into a low disk space or low memory situation that was right on the border, but your latest update appears to eliminate that concern. The error indicates that you do not have write access to the default installation location where the virtual machine is attempting to startup. Do you have some sort of management software on this device that restricts write access to C:\Program Files? Perhaps an AntiVirus solution that is preventing access?

Terry

from iotedge-eflow.

Well, I have a pretty strict IT group managing my machine ;)

I am pretty confident it is some kind of group policy preventing me from editing permissions on that folder. I am actually not sure why its not on my original report, but it was failing on line 3067 - which is a set-acl command. Also, I had elevated my powershell as well, both when installing and running Deploy-Eflow.

Is it unusual for a group policy to block permissions changes on that folder? I was wondering if it would make more sense to have the default directory for the vm images be a less "contended" directory? Maybe one inside the base directory itself?

Unfortunately, I am having some issues with the installer not recognizing the arguments I pass to it, so I can't test this out myself. This doesn't seem to work; here the MSI help message box is shown instead of the installer.

Start-Process -Wait msiexec -ArgumentList '/i', $fileName, '/log', $logFile, '/qn', INSTALLDIR='C:\Program Files\Azure IoT Edge', VHDXDIR='C:\Program Files\Azure IoT Edge\vm'

while this does work

Start-Process -Wait msiexec -ArgumentList '/i', $fileName, '/log', $logFile, '/qn', INSTALLDIR="C:\iotedge", VHDXDIR="C:\iotedge\vm"

from iotedge-eflow.