Error: Could not connect to the Azure Sphere Device Communication Service

peterfenn any ideas about the above issue?

Found a relevant thread in Microsoft Azure Forums - https://social.msdn.microsoft.com/Forums/en-US/8b19e10b-4d88-4de0-a805-e0eeff6d88bc/azure-sphere-device-communication-se…

Solutions provided there were

• #1 - Hi, it works if you copy ftd2xx.dll as you propose.

          There's already one in my C:\Windows\System32. But still didn't work. If I need to place this file somewhere else, let me know.

• #2 - Another solution is to run the  Azure Sphere Device Communication Service (under services.msc) with your user instead of the local system account.

          I ran it using my user but still didn't work.

Even there is a TAP Adapter but it isn't running,

Azure SDK version,

I had this problem and a reinstallation (not a repair) did the trick. I seemed quicker and easier to do this than track down the reason, but it's good to know if it happens again.

I had the reinstallation in mind but was a bit reluctant to do it. Since the installation took around 3 hours to complete. But thanks your suggestion boosted me to try it and the reinstallation did the trick. Although I had to perform one more step after reinstallation and right away it didn't work.

The 'Azure Sphere Device Communication Service' was running as a 'Local Service' and I had to change it to my user to make it work.

Right Click the Service and then Properties and then the 'Log On' tab. Select This account and then browse to select the user. Enter the credentials and give OK.

You should see that user under the 'Log on' column against the service.

Now restart the service and try again ... it should work fine.

By reinstallation I only meant the SDK. That's pretty quick.

Yes, that's pretty quick and I didn't know that before. Thought it would take a long time like the installation. To reiterate, Reinstallation + Service Log on as to my user worked for me. For you, just Reinstallation did the trick?

TAP-Windows Adapter V9 missing or remane to Azure Sphere (Dyxon screenshot)

Adapter TCP/IPv4 IP = 192.168.35.1 MASK 255.255.255.0

https://github.com/Wiz-IO/platform-azure/wiki/Install-Notes#azure-shpere-device-communication-service-manually

Actually service is continuiosly restarting. i resolved this by configuring the Azure Sphere Service to be run by a local admin account

Actually service is continuiosly restarting. i resolved this by configuring the Azure Sphere Service to be run by a local admin account

I repeated the steps prescribed from the Dixon Selvan,

where you have to only change the services (Azure Sphere Device Communication Service)--- Startup type (Automatic; Trigger) --- Properties (logon---USER NAME and Password) apply, and it would definitely show the status as 'RUNNING'; that's it. "You should not reinstall the SDK before applying this method."