IoBroker unter Windows7 64bit installiert einfach nicht

andiandi

Habe ein Windows 7 Pro 64bit auf dem ioBroker drauf soll.

Mit dem Installationsprogramm gehts nicht.

Manuell habe ich zu erst die aktuelle Nodejs LTS-Version (6.x.x) installiert.

Dann Ordner c:\iobroker angelegt.

mittels Admin-Console in den Ordner gewechselt und nom install iobroker eingegebn.

Dann fängt er an und bringt Fehler.

Hier die Ausgabe:

C:\ioBroker>npm install iobroker

> iobroker@1.0.2 install C:\ioBroker\node_modules\iobroker
> node lib/setup.js

npm install iobroker.discovery --production --prefix "C:/ioBroker"
npm install iobroker.admin --production --prefix "C:/ioBroker"
npm install iobroker.js-controller --production --prefix "C:/ioBroker"
npm WARN deprecated tar.gz@1.0.7: ??  WARNING ?? tar.gz module has been deprecat
ed and your application is vulnerable. Please use tar module instead: https://np
mjs.com/tar
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` fail
ed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\media\AppData\Roaming\npm\no
de_modules\npm\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:219:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\media\\AppDat
a\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "r
ebuild"
gyp ERR! cwd C:\ioBroker\node_modules\iobroker.js-controller\node_modules\unix-d
gram
gyp ERR! node -v v6.11.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` fail
ed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\media\AppData\Roaming\npm\no
de_modules\npm\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:219:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\media\\AppDat
a\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "r
ebuild"
gyp ERR! cwd C:\ioBroker\node_modules\iobroker.js-controller\node_modules\ursa
gyp ERR! node -v v6.11.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EACCES 127.0.0.1:9001
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Server._listen2 (net.js:1249:19)
    at listen (net.js:1298:10)
    at net.js:1408:9
    at _combinedTickCallback (internal/process/next_tick.js:83:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules\i
obroker.js-controller\node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-
gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 (node_modules\iobroke
r.js-controller\node_modules\ursa):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 install: `node-gyp re
build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\media\\AppData\\
Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "iobroker.js-control
ler" "--production" "--prefix" "C:/ioBroker"
npm ERR! node v6.11.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! iobroker.js-controller@1.2.0 install: `node iobroker.js setup first`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.js-controller@1.2.0 install script 'node iobroke
r.js setup first'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iobroker.js-controlle
r package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node iobroker.js setup first
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iobroker.js-controller
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iobroker.js-controller
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\ioBroker\node_modules\iobroker\npm-debug.log
Write "iobroker start" to start the ioBroker
npm install https://github.com/arthurblake/node-windows/tarball/f1fd60e93e246966
3b99a9cf3a64086ecedfe1e4 --production --prefix "C:\ioBroker\node_modules\iobroke
r\lib/../../../"
ioBroker service installed. Write "serviceIoBroker start" to start the service a
nd go to http://localhost:8081 to open the admin UI.
To see the outputs do not start the service, but write "node node_modules/iobrok
er.js-controller/controller"
C:\ioBroker
`-- iobroker@1.0.2
  `-- yargs@7.1.0
    +-- cliui@3.2.0
    | +-- strip-ansi@3.0.1
    | `-- wrap-ansi@2.1.0
    +-- decamelize@1.2.0
    +-- get-caller-file@1.0.2
    +-- os-locale@1.4.0
    | `-- lcid@1.0.0
    |   `-- invert-kv@1.0.0
    +-- read-pkg-up@1.0.1
    | +-- find-up@1.1.2
    | | +-- path-exists@2.1.0
    | | `-- pinkie-promise@2.0.1
    | |   `-- pinkie@2.0.4
    | `-- read-pkg@1.1.0
    |   +-- load-json-file@1.1.0
    |   | +-- graceful-fs@4.1.11
    |   | +-- parse-json@2.2.0
    |   | | `-- error-ex@1.3.1
    |   | |   `-- is-arrayish@0.2.1
    |   | +-- pify@2.3.0
    |   | `-- strip-bom@2.0.0
    |   |   `-- is-utf8@0.2.1
    |   +-- normalize-package-data@2.4.0
    |   | +-- hosted-git-info@2.5.0
    |   | +-- is-builtin-module@1.0.0
    |   | +-- semver@5.4.1
    |   | `-- validate-npm-package-license@3.0.1
    |   |   +-- spdx-correct@1.0.2
    |   |   | `-- spdx-license-ids@1.2.2
    |   |   `-- spdx-expression-parse@1.0.4
    |   `-- path-type@1.1.0
    +-- require-directory@2.1.1
    +-- require-main-filename@1.0.1
    +-- set-blocking@2.0.0
    +-- string-width@1.0.2
    | +-- code-point-at@1.1.0
    | `-- is-fullwidth-code-point@1.0.0
    |   `-- number-is-nan@1.0.1
    +-- which-module@1.0.0
    +-- y18n@3.2.1
    `-- yargs-parser@5.0.0

npm WARN enoent ENOENT: no such file or directory, open 'C:\ioBroker\package.jso
n'
npm WARN ioBroker No description
npm WARN ioBroker No repository field.
npm WARN ioBroker No README data
npm WARN ioBroker No license field.

Dutchman

Die Fehler sind normal und ok, ioBroker sollte jetzt laufen und der Admin erreichbar sein?

–-----------------------

Send from mobile device

rantanplan

Hallo andiandi

Meine Installationen sind schon einige Zeit vorbei.

Das angebotene Windows Installationsprogramm funktionierte auf XP 32Bit / Win7 32/64Bit und Win10 64Bit.

Installation jeweils als Admin.

Grüße

Community Forum

NEWS

IoBroker unter Windows7 64bit installiert einfach nicht

Support us

511

32.7k

82.6k

1.3m