Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AzureIoT Sample MSB3073 Error when compiling #32

Closed
piercalderan opened this issue Mar 24, 2019 · 10 comments
Closed

AzureIoT Sample MSB3073 Error when compiling #32

piercalderan opened this issue Mar 24, 2019 · 10 comments

Comments

@piercalderan
Copy link

This is the output when compiling:
Gravità Codice Descrizione Progetto File Riga Stato eliminazione
Errore MSB3073 uscita dal comando "%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -NoProfile -NonInteractive -File "C:\Users\pier\Desktop\azure-sphere-samples-master\Samples\AzureIoT\AzureIoT\script\validate_manifest.ps1
:VCEnd" con codice 1. AzureIoT C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 128

@piercalderan piercalderan changed the title AzueIoT Sample MSB3073 Error AzureIoT Sample MSB3073 Error when compiling Mar 24, 2019
@richardtaylorrt
Copy link
Contributor

Hi - you need to configure the app to work with your IoT Central or to work with your IoT Hub.

If you switch to the "Output -> Build" panel in Visual Studio, you will see this advice:

1>------ Build started: Project: AzureIoT, Configuration: Debug ARM ------
1>Validating project app_manifest.json
1>CmdArgs is empty, this needs to contain the ScopeId for your IoT Hub/Central application
1>The app_manifest.json 'AllowedConnections' needs to contain:
1>  Your IoT Hub/Central application Endpoint address
1>The app_manifest.json file contains a placeholder 'DeviceAuthentication'
1>this needs to be replaced with your Azure Sphere Tenant Id
1>This can be obtained using the Azure Sphere Developer Command Prompt
1>'azsphere tenant show-selected'
...
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Please let us know if this solves the problem, thanks.

@piercalderan
Copy link
Author

piercalderan commented Mar 25, 2019 via email

@richardtaylorrt
Copy link
Contributor

Hi - are you having problems at steps 11 and 12 of the IoT Central configuration? Note the need to run a powershell command to convert the device ID into lower case letters. If this doesn't work, please send a screenshot of the error you see, or of your successfully created 'real' device in IoT Central. Thanks.

@piercalderan
Copy link
Author

piercalderan commented Mar 25, 2019 via email

@piercalderan
Copy link
Author

piercalderan commented Mar 25, 2019 via email

@richardtaylorrt
Copy link
Contributor

The component ID is not the same as a device ID.

  • You do not need to change the component ID in the app manifest. The existing value of "819255ff-8640-41fd-aea7-f85d34c491d5" will work fine.
  • You do need to use your device ID (128 hex digits in lower case) to create a real device in Azure IoT Central (steps 11 and 12). Does this work for you?
  • Once you have a real device, you can run "ShowIoTCentralConfig". It will tell you what you need to put in your manifest.

If this still doesn't work, to help us to help you further, please could you attach:

  1. a screenshot of your device created in IoT Central
  2. the output from running "ShowIoTCentralConfig"
  3. the output from the "Output -> Build" panel in Visual Studio

Thanks.

@piercalderan
Copy link
Author

Hi, here the result following your instructions (Please see the screenshots).
If your MT3260 is really working, please make the screenshot that you make on your side.
Thank you.

Immagine 1
Immagine 2
Immagine 3
Immagine 4
Immagine 5
Immagine 6
Immagine 7

@richardtaylorrt
Copy link
Contributor

Thanks for the additional information. There may be an issue with creating devices in IoT Central, which is impacting you. We are investigating and will update here as soon as we can.

@m-chau
Copy link

m-chau commented Mar 28, 2019

I am having the same issue where I have created "real" devices in my IoT Central application but the ShowIoTCentralConfig.exe fails to find them. Please keep us updated on the resolution. Thank you.

@richardtaylorrt
Copy link
Contributor

Hi @piercalderan , @m-chau - some fixes have been made to IoT Central and to the "ShowIoTCentralConfig" tool. Please can you pull the latest, retry, and let us know if any further problems in getting this app to run. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants