Windows CLI Installer fails


#12

@ZinggJM, I stopped using nodejs to install CLI on my Win10x64 laptop which has one USB3 and one USB2 connector. As @ScruffR said, I ONLY use the windows CLI installer and it works every time. Make sure to get the latest version.


#13

You may have noticed, that I tried exactly that. And it worked on one notebook, and now also on a second one. But it doesn’t work on my new MINIX. I only tried to use nodejs (npm) to get more information.

I still would like to know if this is related to missing USB 2.0 And your support should also care about that.


#14

@ZinggJM, no one who has responded to you, including the Elites, work for Particle. We are all volunteers. My laptop’s USB2 is ONLY used for a wireless mouse adapter. I run all my Particle devices from two USB3 powered hubs. As for the installation, it would seem like a permissions or firewall issue. I use Bitdefender AV which also has blocked the full installation until I “allowed” the installer to modify files. So it may be your AV, your Windows firewall, your router, your windows permissions, the folder you are installing from, etc. The serialport@6.2.0 error has popped up in the past with various systems. If you want assistance, I suggest you change your tone and your approach.


#15

I understand that this sentence can be misunderstood. Sorry for that. I do not need help, as I have the workaround using one of the other notebooks. But I thought I should report what I think I have found out.

With the above sentence I meant there will be other users with new desktops or notebooks without USB 2.0 coming.

When I write in bold I try to emphasise the important points. I didn’t want to be rude.


#16

@ZinggJM, I’m still not convinced that the issue is the USB3-only environment. However, it does beg for some testing by others who have similar testing if possible. Until others can duplicate the issue, it is not a “reportable” bug IMO. I will poke the Particle folks to see if they have any insights.


#17

Thanks for reporting the issue @ZinggJM and thanks for helping to understand what’s going on @ScruffR and @peekay123

We’ll keep an eye out for additional users having issues with laptops without USB 2.0.


#18

This error from npm is because you don’t have node-gyp configured so npm doesn’t know how to compile the binaries required for the particle-cli.

One way to fix this is documented here: https://github.com/nodejs/node-gyp#option-1

Install all the required tools and configurations using Microsoft’s windows-build-tools using npm install --global --production windows-build-tools from an elevated PowerShell or CMD.exe (run as Administrator).


GxEPD2_PP : Particle Display Library for SPI E-Paper Displays
#19

I tried to install Particle CLI on a new small box PC (CSL 18012) with Windows 10 pro that has a USB 2.0 connector. Installation with Windows CLI Installer failed also. So USB 3.0 only is not the cause.

The installation was on a fresh installation of Windows 10 pro 1803, with Windows Defender only, pre-installed Antivirus SW uninstalled. I did run the installer with run as Administrator.

Is there any prerequisite for installing with Windows CLI installer, such as Java or python?

Do I need to allow internet access for some component in Windows Defender?
(With Arduino IDE I used to get a pop-up box requesting network access for Java).

You may see a Windows Defender SmartScreen warning when running the Windows CLI Installer if you are one of the first people to run the installer after a new release.

I didn’t get that.


#20

Is there any prerequisite for installing Particle CLI with Windows CLI installer, such as Java or python?


#21

@ZinggJM, no, there is no prerequisite. However, I have installed using “Run as Administrator” on my Win10x64 Home system. I also had to include the OpenSSL directory (created by the installer) in the PATH. The PC in question is a Gole 1 handheld PC with 4GB of RAM, 64GB of SSD, one USB3 and one USB2 port.


#22

@peekay123, thank you. I just run the installer again, run as administrator. It failed, but reported ok.

This is my path after the installation:

C:\Users\ZinggJ>path
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Users\ZinggJ\AppData\Local\Microsoft\WindowsApps;C:\OpenSSL-Win32\bin;C:\Users\ZinggJ\AppData\Local\particle\bin;

this is in the error.log:

2019/01/04 17:49:43 Manifest version 0.3.3-d3120d4, Installed version 0.3.3-d3120d4
2019/01/04 17:49:43 particle: Adding dependencies…
2019/01/04 17:50:26 done
2019/01/04 17:50:26 particle: Installing plugins…
2019/01/04 17:50:28
2019/01/04 17:50:28 !
2019/01/04 17:50:28
2019/01/04 17:50:28 ! exit status 3221225477
2019/01/04 17:50:28 particle: Installing plugins (retrying)…
2019/01/04 17:50:28
2019/01/04 17:50:28 ! Error installing package.
!
! Try running again with GODE_DEBUG=info to see more output.
2019/01/04 17:51:23 Time since last update 1m40.3727377s, update in block
2019/01/04 17:51:23 particle: Installing plugins…
2019/01/04 17:51:23
2019/01/04 17:51:23 !
2019/01/04 17:51:23
2019/01/04 17:51:23 ! exit status 3221225477
2019/01/04 17:51:23 particle: Installing plugins (retrying)…
2019/01/04 17:51:23
2019/01/04 17:51:23 ! Error installing package.
!
! Try running again with GODE_DEBUG=info to see more output.
2019/01/04 17:53:41 Time since last update 3m58.9411817s, update in block
2019/01/04 17:53:41 particle: Installing plugins…
2019/01/04 17:53:42
2019/01/04 17:53:42 !
2019/01/04 17:53:42
2019/01/04 17:53:42 ! exit status 3221225477
2019/01/04 17:53:42 particle: Installing plugins (retrying)…
2019/01/04 17:53:42
2019/01/04 17:53:42 ! Error installing package.
!
! Try running again with GODE_DEBUG=info to see more output.
2019/01/07 15:51:45 Time since last update 70h2m2.7374615s, update in block
2019/01/07 15:51:45 particle: Installing plugins…
2019/01/07 15:51:46
2019/01/07 15:51:46 !
2019/01/07 15:51:46
2019/01/07 15:51:46 ! exit status 3221225477
2019/01/07 15:51:46 particle: Installing plugins (retrying)…
2019/01/07 15:51:46
2019/01/07 15:51:46 ! Error installing package.
!
! Try running again with GODE_DEBUG=info to see more output.

C:\Users\ZinggJ\AppData\Local\particle\node_modules

is empty.


#23

@ZinggJM, I have NEVER seen such hassles running the installer! I suspect something is blocking the plugin downloads, either in windows or on your router. I had issues with the Nodejs npm installation before the Windows CLI installer came out. After that, I have never had an issue.


#24

I don’t think it is the router, as I have successfully installed on a notebook on the same network.

It is hard to diagnose, if there are no useful logfiles around. Once I new where to look for blocked port accesses, but this was on Windows 2000 or Windows 7…


#25

@ZinggJM, check out this post… another user was having problems with the CLI installer that turned out to be blocked network traffic. I did some testing with Wireshark to determine the server(s) that the CLI installer contacts:


#26

@ninjatill, thank you for your answer. Unfortunately I am not clever enough to understand what I could do. Or is this an explanation why it doesn’t work? TCP port 443, isn’t this a standard port? Or do I need to allow some application to use that port in Windows Defender? I am my own network administrator, so I can’t ask anybody else for help.


#27

Things to check:

  1. can you do a nslookup for binaries.particle.io?
    c:\> nslookup binaries.particle.io

image

  1. can you do a nslookup for registry.npmjs.org?
    c:\> nslookup registry.npmjs.org

image

  1. can you ping binaries.particle.io and do you get a response?
    c:\> ping binaries.particle.io

  2. can you ping registry.npmjs.org and do you get a response?
    c:\> ping registry.npmjs.org

  3. If all the above works successfully, can you enter https://binaries.particle.io into a browser and get this result?:
    image


#28
Microsoft Windows [Version 10.0.17763.195]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\ZinggJ>nslookup binaries.particle.io
Server:  UnKnown
Address:  192.168.2.104

Non-authoritative answer:
Name:    binaries.particle.io
Address:  195.186.210.161


C:\Users\ZinggJ>nslookup registry.npmjs.org
Server:  UnKnown
Address:  192.168.2.104

Non-authoritative answer:
Name:    registry.npmjs.org
Addresses:  2606:4700::6810:1223
          2606:4700::6810:1623
          2606:4700::6810:1323
          2606:4700::6810:1a23
          2606:4700::6810:1b23
          2606:4700::6810:1923
          2606:4700::6810:1523
          2606:4700::6810:1823
          2606:4700::6810:1123
          2606:4700::6810:1723
          2606:4700::6810:1023
          2606:4700::6810:1423
          104.16.18.35
          104.16.21.35
          104.16.19.35
          104.16.25.35
          104.16.26.35
          104.16.24.35
          104.16.22.35
          104.16.27.35
          104.16.16.35
          104.16.20.35
          104.16.17.35
          104.16.23.35


C:\Users\ZinggJ>ping binaries.particle.io

Pinging binaries.particle.io [195.186.210.161] with 32 bytes of data:
Reply from 195.186.210.161: bytes=32 time=24ms TTL=240
Reply from 195.186.210.161: bytes=32 time=22ms TTL=240
Reply from 195.186.210.161: bytes=32 time=24ms TTL=240
Reply from 195.186.210.161: bytes=32 time=17ms TTL=240

Ping statistics for 195.186.210.161:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 24ms, Average = 21ms

C:\Users\ZinggJ>ping registry.npmjs.org

Pinging registry.npmjs.org [104.16.23.35] with 32 bytes of data:
Reply from 104.16.23.35: bytes=32 time=22ms TTL=54
Reply from 104.16.23.35: bytes=32 time=44ms TTL=54
Reply from 104.16.23.35: bytes=32 time=15ms TTL=54
Reply from 104.16.23.35: bytes=32 time=21ms TTL=54

Ping statistics for 104.16.23.35:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 44ms, Average = 25ms

C:\Users\ZinggJ>

Latest versions of various Particle tools are kept here.


#29

In my mind, you just ruled out networking problems including DNS, TCP/IP connectivity and TLSv1.2. So, this does not rule out that Windows Defender or Windows Firewall is blocking the CLI application. I would try to temporarily disable both those services while running the installer as admin again.


#30

I tried this, and got the same result. I will uninstall and repeat this test tomorrow.


#31

I uninstalled Particle CLI and OpenSSL, increase PageFile size and switched off Windows Defender and Firewall. I run Windows CLI installer again as administrator, with the same result.

In C:\Users\ZinggJ\AppData\Local\Temp I see a new file aria-debug-7804.log with content:

2019-01-08 13:29:17.917|00008248|
C:\build\aria-cpp-v1\clienttelemetry\src\LogManagerImpl.cpp(626): class Microsoft::Applications::Telemetry::ILogger *__thiscall Microsoft::Applications::Telemetry::LogManagerImpl::Initialize(const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const struct Microsoft::Applications::Telemetry::LogConfiguration &) WARNING: Invalid in-ram queue size (20971520), adjusted to max ram queue size

I have no idea if this is related to the issue.