Azure IoT Edge
An Azure service that is used to deploy cloud workloads to run on internet of things (IoT) edge devices via standard containers.
Provision-EflowVm fails with exception at Line 2415. No further info on error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 84%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Sandeep Manikonda
0
Reputation points
Setup:
OS: Windows 10 Pro X64
Hyper-V: Enabled,
Installation as per the quickstart guide at the link: https://learn.microsoft.com/en-us/azure/iot-edge/quickstart
Authentication: Symmetric Keys
Execution Policy set to AllSigned on 'Local machine' scope
Host config from Get-EflowHostConfiguration | format-list
- FreePhysicalMemoryInMB : 9660
NumberOfLogicalProcessors : 8
- DiskInfo : {@{Drive=C:; FreeSizeInGB=46}, @{Drive=D:; FreeSizeInGB=344}, @{Drive=E:; FreeSizeInGB=0}}
- GpuInfo : <NIL>
Installation folder selected to Default: C:/Program Files/Azure IoT Edge
Deploy-Eflow -acceptEula Yes -acceptOptionalTelemetry Yes -cpuCount 1 -memoryInMB 2048 -vmDataSize 10
Provision-EflowVm output:
Setting provisioning information for provisioning type: ManualConnectionString
OK
Exception caught!!!
- Failed to provision at line 2415
Failed to provision
Further, on Connect-EflowVm, sudo iotedge list returns:
A module runtime error occurred
caused by: A module runtime error occurred
caused by: timed out
```sudo systemctl restart iotedge returns:
Failed to restart iotedge.service: Unit iotedge.service not found.
The above error most likely would mean a corrupted install, user proceeded with an Uninstall via Control Panel -> Add/remove Programs, restart device & fresh re-install including downloading msi.
The same issue still persists.
The iotedge-check logs
1. host time is close to reference time - timedatectl status reveals NTP service active & system clock synchronized
2. could not load cert with ID "aziot-edged-trust-bundle" - Not relavant to symmetric key auth
3. configuration has correct URIs for daemon mgmt endpoint - error: sudo chown -R iotedge:iotedge /var/run/iotedge/mgmt.sock , & restart iotedge runtime, but does not impact the outcome.
4. Container on the IoT Edge module network can connect to upstream AMQP port - why does it try to connect over AMQP? Should it not be 8883?
Azure IoT Edge
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 74%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
VSawhney 880 Reputation points Microsoft External Staff Moderator2025-07-08T10:01:47.25+00:00 Hello Sandeep Manikonda,
It looks like you're running into a provisioning issue with EFLOW (
Provision-EflowVmfails at line 2415), followed by runtime errors when listing IoT Edge modules. Here's a structured approach to help troubleshoot and resolve this:
There could be 3 root cause possibilities for this:- Provisioning Exception at Line 2415: This typically indicates a failure during the VM setup phase—often due to resource constraints, corrupted installation, or issues with the WSSDAgent service.
- iotedge.service not found: This suggests the IoT Edge runtime wasn't installed correctly inside the EFLOW VM. It may be a result of a failed provisioning step or missing runtime components.
- AMQP vs MQTT (Port 8883): The runtime may default to AMQP if MQTT is blocked or not explicitly configured. Ensure port 8883 is open and preferred in your IoT Hub settings.
You may follow these troubleshooting steps:
- Check WSSDAgent Service:
If it fails to start, check logs underGet-Service -Name WSSDAgent Start-Service -Name WSSDAgentC:\ProgramData\wssdagent. - Clean Reinstall EFLOW:
- Uninstall EFLOW via Control Panel.
- Manually delete:
C:\Program Files\Azure IoT EdgeC:\ProgramData\wssdagent - Reboot and reinstall using the latest MSI from https://learn.microsoft.com/en-us/azure/iot-edge/quickstart.
- Verify VM Networking: After running Connect-EflowVm, check:
Ensure the VM has a valid IP and can reach the internet.ifconfig eth0 - Run Diagnostics Use:
This generatesGet-EflowLogseflowlogs.zipwith detailed logs—helpful for deeper analysis. - Check IoT Edge Runtime Inside the EFLOW VM:
Ifsudo iotedge check sudo iotedge listiotedgeis missing, the runtime likely failed to install—manual reinstallation may be needed.
Hope this helps!
Thank you! -
VSawhney 880 Reputation points Microsoft External Staff Moderator
2025-07-09T12:08:20.7633333+00:00 Hello Sandeep Manikonda,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Thank you!
-
Sandeep Manikonda 0 Reputation points
2025-07-09T18:06:05.0733333+00:00 Hi Sawhney,
Thanks for the reply & the troubleshooting tips.
I tried a clean uninstall, restarted the device & re-install fresh, including downloading the latest msi. But the same issue remains.
Looking at the iotedge system logs shows the following errors:
`EFLOW aziot-identityd[3302]: Failed to provision with IoT Hub
service encountered an error
caused by: Hub client error
caused by: {"errorCode":401002,"message":"Unauthorized access"`
Just to ensure there are no typos in the connection string, I used az iot hub device-identity connection-string show to pass into a var & then pass the var in the Provision-Eflow command. Still the same error.
The config.toml seems fine with the correct provisioning type and connection string updated. Next, I tried with X509 auth with test certificates. Complete reinstall and tried provisioning. same issue persists.
-
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator2025-07-15T08:12:51.19+00:00 Thank you for sharing the EFlow logs.
caused by: {"errorCode":401002,"message":"Unauthorized access"`Seem to be authorization issue.
With connection string
We normally install EFlow with connection string with below command
Provision-EflowVm -provisioningType ManualConnectionString -devConnString "<CONNECTION_STRING_HERE>"With Symmetric key
If you want to use symmetric keys in provisioning Eflow please use follow command including your Registration Id
Provision-EflowVm -provisioningType DpsSymmetricKey -scopeId PASTE_YOUR_ID_SCOPE_HERE -registrationId PASTE_YOUR_REGISTRATION_ID_HERE -symmKey PASTE_YOUR_PRIMARY_KEY_OR_DERIVED_KEY_HEREReference used for symmetric Key authentication - https://learn.microsoft.com/en-us/azure/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-symmetric?tabs=individual-enrollment#provision-the-device-with-its-cloud-identity
With X509 attestation
Provision-EflowVm -provisioningType DpsX509 -scopeId PASTE_YOUR_ID_SCOPE_HERE -registrationId PASTE_YOUR_REGISTRATION_ID_HERE -identityCertPath PASTE_ABSOLUTE_PATH_TO_IDENTITY_CERTIFICATE_HERE -identityPrivateKey PASTE_ABSOLUTE_PATH_TO_IDENTITY_PRIVATE_KEY_HEREReference used for x509 - https://learn.microsoft.com/en-us/azure/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-x509?tabs=individual-enrollment
Please uninstall EflowVM prior before you go with new installation. Trying to replicate with configuration and shall update you post that.
Looking forward to your results in the mean while.
Thank you
-
VSawhney 880 Reputation points Microsoft External Staff Moderator
2025-07-16T10:10:09.78+00:00 Hello Sandeep Manikonda,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Thank you!
-
Sandeep Manikonda 0 Reputation points
2025-07-16T11:18:14.14+00:00 Hi Sawhney & Manas,
I tried a couple of ways with each time a fresh re-install of the EFLOW
- Provision one edge enabled device with symmetric key (which might a misnomer, since we are actually using a 'Primary or secondary key' / 'SharedAccessKey') of the device. We are not generating an additional symmetric key?). Or are these all the same thing, but different names, just so that we learn new terminology?
- Result- same issue -
Failed to provision config.toml. Please provision manually.The Connect-EflowVm returned 'Connection timed out during banner exchange.'
- Result- same issue -
Connected to eflowvm using hcsdiag list -> hcsdiag console <id>.
Then a iotedge list returned:
A module runtime error occurredcaused by: A module runtime error occurredcaused by: connection error: Connection reset by peer (os error 104)caused by: Connection reset by peer (os error 104)Further iotedge logs shows:
aziot-identityd[126646]: 2025-07-16T10:54:00Z [ERR!] - caused by: could not create home directorycaused by: Permission denied (os error 13)Probable rootcauses suggests to check the connection string, if the provisioning info in config.toml correctly updated - Yes to both
Why does one need to change folder permissions manually for each of the services to run identityd, keyd, etc, to make the basic provisioning work is beyond my understanding.
- Provision a new edge enabled device manually with X509 certificate, using test certificates.
Similar result -
Exception caught. provision fails with exception.I see that Manas has provided the command to provision with DPS X509, but not manual X509. Is the manual X509 not recommended now?
- Provision one edge enabled device with symmetric key (which might a misnomer, since we are actually using a 'Primary or secondary key' / 'SharedAccessKey') of the device. We are not generating an additional symmetric key?). Or are these all the same thing, but different names, just so that we learn new terminology?
-
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator
2025-07-24T15:10:15.45+00:00 Hello Sandeep Manikonda,
Sorry for delay in getting back to you and about the misinterpretation about symmetric key. I think it might be virtual network blocking your connection request as it succeed with virtual network protected VM and Public IOT hub.
Have requested details to private message for further assistance.
Thank you
Sign in to comment
Sign in to answer