Issue when doing pcs login - Error: Cannot find module 'azure-arm-containerservice'

[falloutxAY]

When doing pcs login

It returns with below error:

C:\Users\demouser\AppData\Roaming\npm>pcs login

internal/modules/cjs/loader.js:582
throw err;
^

Error: Cannot find module 'azure-arm-containerservice'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
at Function.Module._load (internal/modules/cjs/loader.js:506:25)
at Module.require (internal/modules/cjs/loader.js:636:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (C:\Users\demouser\AppData\Roaming\npm\node_modules\iot-solutions\publish\deploymentmanager.js:11:38)
at Module._compile (internal/modules/cjs/loader.js:688:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
at Module.load (internal/modules/cjs/loader.js:598:32)
at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
at Function.Module._load (internal/modules/cjs/loader.js:529:3)

[akn9050]

PCS login is working now

[akn9050]

there is one more issue after login with PCS during Solution deployment.

Issue: Stuck while running pcs command to deploy solution

Description

After running PCS command, provided solution name, after that selected subscription and press enter but after that nothing is happening.

[toddwhitehead]

Confirmed same issue, after selecting subscription never prompted for location

[akn9050]

yes

[joelhulen]

I believe this may be a problem with the provided VM. Could you please try the steps that lead to the PCS login from either a new VM (using Windows 10 or Server 2016 with the latest build of Visual Studio) or your own machine and see if you get past this? This will help verify the issue is with the specific VM image we are using.

[toddwhitehead]

The issue is an issue with the underlying pcs code (Azure/pcs-cli#414) which is actively being addressed and hopefully fixed soon.

[toddwhitehead]

      I believe this may be a problem with the provided VM. Could you please try the steps that lead to the PCS login from either a new VM (using Windows 10 or Server 2016 with the latest build of Visual Studio) or your own machine and see if you get past this? This will help verify the issue is with the specific VM image we are using.

Issue seems to be related to version of node installed in base image vm. I confirmed if you uninstall and install latest v8 (https://nodejs.org/dist/latest-v8.x/node-v8.14.0-win-x64.zip) version of node, pcs works as expected.

Interestingly the current docs for installing remote-mon locally (https://docs.microsoft.com/en-us/azure/iot-accelerators/iot-accelerators-remote-monitoring-deploy-local) note that node v8 is required and not to use v10.

I'm running this workshop early next week so will have to use this as a workaround until root cause can be identified.

[joelhulen]

Looks like the issue is now closed, yet it's not available until the next release: Azure/pcs-cli#414

[akn9050]

This issue is no more. Facing issue in Exercise 3 task 5 when running simulator web app.

1. In first run it was showing error environment variable PCS_IOTHUB_CONNSTRING not available. This is not described to add for WebService project in lab guide.

2. After adding environment PCS_IOTHUB_CONNSTRING. Popup new error in 2nd run environment varible PCS_STORAGEADAPTER_WEBSERVICE_URL not available. I added this also.

3. In 3rd run getting another error.
   ##Error
   System.NullReferenceException
   HResult=0x80004003
   Message=Object reference not set to an instance of an object.
   Source=Microsoft.Azure.IoTSolutions.DeviceSimulation.Services

4. And in In Exercise 3 task 5.4, when doing get method for http://localhost:9003/v1/simulations/1. Then getting status 500 instead of 200.