I tried the following methods all of which have failed
Running the .msi installer via the GUI from the Node site (no option given for running as admin)
Running the .msi installer via comandline as admin
Running choclatey installer as admin
Here is the choclatey output as seen in the log
Downloading nodejs.install 64 bit
from 'https://nodejs.org/dist/v5.10.1/node-v5.10.1-x64.msi'
Installing nodejs.install...
[ERROR] Running msiexec with /i "C:\Users\user1\AppData\Local\Temp\chocolatey\nodejs.install\5.10.1\nodejs.installInstall.msi" /quiet was not successful. Exit code was '1603' Error Mess
age:
.
At C:\ProgramData\chocolatey\helpers\functions\Start-ChocolateyProcessAsAdmin.ps1:92 char:10
+ throw <<<< $errorMessage
+ CategoryInfo : OperationStopped: ([ERROR] Running...or Message:
.:String) [], RuntimeException
+ FullyQualifiedErrorId : [ERROR] Running msiexec with /i "C:\Users\tcastonzo\AppData\Local\Temp\chocolatey\nodejs.install\5.10.1\nodejs.installInstall.msi" /quiet was not successful.
Exit code was '1603' Error Message:
.
The install of nodejs.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\nodejs.install\tools\chocolateyInstall.ps1'.
See log for details.
Chocolatey installed 0/1 package(s). 1 package(s) failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures:
- nodejs.install
PS C:\GitProjects\reporting> choco install nodejs.install
Installing the following packages:
nodejs.install
By installing you accept licenses for the packages.
I had same problem with Win-7 with node-v6.10.3-x64.msi and node-v6.10.3-x86.msi installers.
Solution:
Download the Zipped version; When extracting, note the file that causes error.
Then, using Explorer, drill down to the target folder, created an empty file, then copy the content of archived file into the new, empty file.
I think the FQ path to destination is too long. Following is the error message I received.
! C:\Users\......\Downloads\node-v6.10.3-win-x64.zip: Cannot create node-v6.10.3-win-x64\node_modules\npm\node_modules\npm-registry-client\node_modules\npmlog\node_modules\gauge\node_modules\string-width\node_modules\is-fullwidth-code-point\node_modules\number-is-nan\package.json
! The system cannot find the path specified.
Since support for windows 7 ended for Nodejs .I found the manual installment easier.
see this comment from github: https://github.com/nodejs/node/issues/33000#issuecomment-644530517
Do follow the same steps with the binary zip file from : here
I the exact same error in Windows 10.
After launched my shell, making sure I was running as administrator, it worked.
Related
I tried Install-Package nodejs, which seems to have done something:
PS C:\WINDOWS\system32> Install-Package nodejs
The package(s) come(s) from a package source that is not marked as trusted.
Are you sure you want to install software from 'chocolatey'?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): y
Name Version Source Summary
---- ------- ------ -------
nodejs.install 11.10.0 chocolatey Node JS - Evented I/O for v8 JavaScript.
nodejs 11.10.0 chocolatey Node JS - Evented I/O for v8 JavaScript.
Then when I try to run the node command, it fails:
PS C:\WINDOWS\system32> node
node : The term 'node' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ node
+ ~~~~
+ CategoryInfo : ObjectNotFound: (node:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
How do I do it properly with PackageManager, so that the command is then available?
Not sure if this other question is related: Chocolaty packages not installing via OneGet/PackageManagement in Windows 10?
As that other question suggests, I tried setting Set-ExecutionPolicy Unrestricted, the uninstalling and reinstalling nodejs, but the result is the same.
I do see that after install the following files exist:
C:\Chocolatey\lib\nodejs.11.10.0\nodejs.11.10.0.nupkg
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg\legal\LICENSE.txt
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg\legal\VERIFICATION.txt
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg\tools\chocolateyInstall.ps1
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg\tools\node-v11.10.0-x64.msi
C:\Chocolatey\lib\nodejs.install.11.10.0.nupkg\nodejs.install.11.10.0.nupkg\tools\node-v11.10.0-x86.msi
which makes me think that maybe it expects me to run the installer manually after?
My goal is to simply install anything I need on a new Windows machine from a script, without having to download/install them all manually with GUIs.
I was able to reproduce this, but also was able to resolve it. The issue is that the node executable isn't on the PATH after installing with Install-Package. However, this does make some sense as the current PowerShell process won't pick up outside changes to environment variables until it is relaunched.
Chocolatey's refreshenv command works sometimes but not always, and after installing nodejs with Install-Package, refreshenv did not work to refresh the PATH variable. What did work was launching a new PowerShell session and running the node command, which ran the executable successfully:
> node
Welcome to Node.js v16.7.0.
Type ".help" for more information.
>
choco.exe can sometimes mask this but usually Chocolatey won't generate shims for executables placed by EXE or MSI installers (unless the package maintainer forcibly creates them).
Tip: In case you are in a situation where you need to call the binary from the same process that installed the package (e.g. during a chef-client run where refreshenv isn't an option), use the fully-qualified path to the executable to invoke the newly-installed software.
Additionally, don't use the Chocolatey OneGet provider in real automation; it's not yet stable and looks like it hasn't seen any development activity in five years at this time of writing. From the README.md:
NOTE: Seeking maintainers to help finish this Provider. Please inquire on the issues list or on Gitter (see the chat room below). Thanks!
There is an alternative listed in the same README:
NOTE: For now, you may be more interested in using the ChocolateyGet provider as a stop gap solution until this provider is ready. See https://github.com/jianyunt/ChocolateyGet for details
I tried this and it seems to work, but I would still recommend using the official choco.exe binary. It's easy to install and you'll get the best support when using it. It's also telling that configuration management solutions (such as Chef's chocolatey_package resource) continue to make use of the binaries and will generally list installing the client as a prerequisite, even though technically the PackageManagement module could be used as a native solution instead.
It worked for me:
winget install nodejs
i have followed the instruction in previous posts but still cannot get user-secret to work.
I'm trying to install it on my IIS server. I run everything in this path:
C:\inetpub\wwwroot\myapp\wwwroot>
dnvm use 1.0.0-rc1-update1 -p
dnu commands install Microsoft.Extensions.SecretManager --overwrite
the installation passes and I get the message:
The following commands were installed: user-secret
but them when i run:
user-secret -h
I get the following error:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Framework.SecretManager.CommandOutputProvider..ctor(IRuntimeEnvi
ronment runtimeEnv)
at Microsoft.Framework.SecretManager.Program..ctor(IRuntimeEnvironment runtim
eEnv)
needless to say - no UserSecrets folder is created...
can you help?
thanks!
Just try to restart Visual Studio and Developer Command Prompt for VS2015.
It worked for me.
dnx v. 1.0.0-rc1-final
Microsoft.Extensions.SecretManager v. 1.0.0-rc1-final
I'm trying to get ltib installed , for installation of some packages that I need.
I've gotten to the point of installation where I do
./ltib
and it gives me this error in the host_config.log
Build path taken because:no prebuilt rpm
Can't get: rpm-4.0.4.tar.gz at ./ltib line 851
Died at ./ltib line 2557
traceback:
main::check_rpm_setup:2557
main::host_checks:1541
main:562
....
and then it says :
These packages failed to build:
rpm-fs
Build failed
I have rpm on this installation of debian linux. I even downloaded rpm-4.0.4.tar.gz and placed it in the same directory as ./ltib
Has anyone encountered this error before?
Another question: Do I need internet connection for installation of ltib? (I downloaded the tar from the website)
this issue has been solved, you need to change line 12 in rpm.spec file which is located /dist/lfs-5.1/rpm.
change
Source : %{name}-%{version}.tar.gz"
to:
Source : http://rpm.org/releases/historical/rpm-4.0.x/rpm-4.0.4.tar.gz
i think some files are missing on bitshrine.org server. You can apply same solution for other missing files.
I keep getting errors when trying to read a sas7bdat file in R studio. My R studio is running on a Linux Redhat Server. I've tried to install the different versions of the sas7bdat package.
Installed the 0.1 version
install.packages("~/sas7bdat_0.1.tar.gz", repos = NULL, type
="source")
library(sas7bdat)
read.sas7bdat({file})
unknown host 9.0301M2 please report bugs to sas7bdatRbugs#gmail.com
Installed the 0.2 version (http://biostatmatt.com/archives/1712)
install.packages("~/sas7bdat_0.2.tar.gz", repos = NULL, type =
"source")
library(sas7bdat)
read.sas7bdat({file})
Error in read.sas7bdat("/home/raffie/all.sas7bdat") :
unknown host 01M2Linu please report bugs to sas7bdatRbugs#gmail.com
Installed the 0.3 version (from cran)
install.packages("~/sas7bdat_0.3.tar.gz", repos = NULL, type =
"source")
library(sas7bdat)
read.sas7bdat({file})
found 0 row size subheaders where 1 expected please report bugs to
sas7bdatRbugs#gmail.com
The same errors appear when I called the commands in RStudio running in Windows, with the respective versions of the package installed. However, when I installed the package using the install_github("sas7bdat","BioStatMatt) command, I was then able to read sas7bdat files. But the same cannot be said when I tried to install the package using the install_github command on the Linux server RStudio. The error was:
> install_github("sas7bdat","BioStatMatt")
checking for file '/tmp/Rtmpu0f5Xu/devtools3ce32ba1e1fd/sas7bdat-master/DESCRIPTION' ... OK
preparing 'sas7bdat':
checking DESCRIPTION meta-information ... OK
installing the package to build vignettes
creating vignettes ... ERROR Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'sas7bdat.tex' failed. LaTeX errors: ! LaTeX Error: File `ltcaption.sty' not found.
Type X to quit or to proceed, or enter new name. (Default extension: sty)
! Emergency stop.
l.9 \setlength
{\extrarowheight}{2pt}^^M ! ==> Fatal error occurred, no output PDF file produced! Calls: -> texi2pdf -> texi2dvi Execution halted
Error: Command failed (1)
I think the version on Github is the only version that can work for me currently (the sas7bdat-master version). This is because it works when I use it in Windows.
Link: https://github.com/BioStatMatt/sas7bdat
However, only the .zip file is available. I tried to convert it to a .tar.gz file, and then install the package (the RStudio on Linux server can only install .tar.gz packages). The following error was found:
Error in untar2(tarfile, files, list, exdir, restore_times) : unsupported entry type ‘’
What can I do about this? Are the errors I'm getting mainly because my RStudio running on a Linux Redhat server (x86_64) can only read .tar.gz packages? The command read.sas7bdat works in the RStudio running in my windows 7 PC, when I used install_github command.
I got the following error message during the installation of the program :
"1: ALLUSERS property is not 1 - this MSM cannot be used for a per-user or fallback-to-user install 2: 2"
Binaries for installation were compiled by Install Shield v 12.
Could anyone help me, please?
Your setup program includes a merge module that only supports machine-wide installations. If your program contains the installation scope dialog box (Install for: All users on this computer / Just for me), select the first option. If it doesn't, run it from the command line using:
msiexec /i YourSetup.msi ALLUSERS=1