Updating extensions on my laptop today, and it bombed.

Uncaught node.js Error

Error: stream.push() after EOF
at readableAddChunk (_stream_readable.js:142:15)
at IncomingMessage.Readable.push (_stream_readable.js:123:10)
at HTTPParser.parserOnBody (_http_common.js:132:22)
at Socket.socketOnData (_http_client.js:272:20)
at Socket.EventEmitter.emit (events.js:98:17)
at Socket.Readable.read (_stream_readable.js:366:10)
at Socket.socketCloseListener (_http_client.js:194:10)
at Socket.EventEmitter.emit (events.js:120:20)
at TCP.eval [as close] (net.js:459:12)

Hello Steve,
This error is most probably caused by a time-out from the DMXzone server. Please restart the Extension Manager and try again

I too get this error. Uncaught node.js Error

TypeError: Object #<Object> has no method 'resetItem'
at eval (file:///Applications/DMXzone%20Extension%20Manager.app/Contents/Resources/app.nw/js/extensions.js:200:12)
at eval (/Applications/DMXzone Extension Manager.app/Contents/Resources/app.nw/node_modules/async/lib/async.js:254:17)
at eval (/Applications/DMXzone Extension Manager.app/Contents/Resources/app.nw/node_modules/async/lib/async.js:151:21)
at eval (/Applications/DMXzone Extension Manager.app/Contents/Resources/app.nw/node_modules/async/lib/async.js:251:21)
at eval (/Applications/DMXzone Extension Manager.app/Contents/Resources/app.nw/node_modules/async/lib/async.js:615:34)
at eval (/Applications/DMXzone Extension Manager.app/Contents/Resources/app.nw/node_modules/async/lib/async.js:151:21)
at Object.eval [as oncomplete] (fs.js:97:15)


Even after a day and a reboot later

I will note that I'm on Yosemite beta so I'm not surprised or upset by it. Just letting you know. Thanks. (I think I had successfully updated a few when I first installed the beta but not 100% sure).

I have the following error as well:

Uncaught node.js Error

Error: err >= 0
at exports._errnoException (util.js:676:20)
at ChildProcess.spawn (child_process.js:973:11)
at exports.spawn (child_process.js:753:9)
at Registry.get (C:\Users\PATRICK\AppData\Local\Temp\nw36048_8798\node_modules\winreg\lib\registry.js:332:14)
at eval (C:\Users\PATRICK\AppData\Local\Temp\nw36048_8798\lib\dreamweaver.js:163:11)
at eval (fs.js:258:14)
at Object.eval [as oncomplete] (fs.js:97:15)

More problems with the DMXzone extension manager today, but a different node.js error this time, when trying to apply the update that the extension manager says is available.

Uncaught node.js Error

TypeError: undefined is not a function
at ClientRequest.eval (C:\Users\Steve\AppData\Local\Temp\nw3492_18832\lib\updater.js:45:19)
at ClientRequest.EventEmitter.emit (events.js:98:17)
at Socket.socketOnData (_http_client.js:277:9)
at Socket.EventEmitter.emit (events.js:98:17)
at readableAddChunk (_stream_readable.js:156:16)
at Socket.Readable.push (_stream_readable.js:123:10)
at TCP.onread (net.js:509:20)

As it is described in the announcement:
Note: If you receive an error upon updating your DMXzone Extension Manager for Dreamweaver, please do a full reinstall by downloading the latest version from DMXzone.

I've done that before. So, when I do this again today, it will be the 3rd time I've installed this extension manager from the latest version on the site...

If you see any errors, please modify the EM shortcut by adding /debug like in the following screenshot:

This will start the developer console - please send us the errors that appear there in the console to

Before I installed the latest version, I ran debug mode. I got this one error in the console.

Error copying files to dreamweaver undefined dreamweaver.js:61

I have now installed the new extension manager.

Restarting did not help

Sorry Ian,
Could you please be a little more detailed?

Uncaught node.js Error

TypeError: undefined is not a function
at ClientRequest.eval (/Applications/DMXzone Extension Manager.app/Contents/Resources/app.nw/lib/updater.js:45:19)
at ClientRequest.EventEmitter.emit (events.js:98:17)
at Socket.socketOnData (_http_client.js:277:9)
at Socket.EventEmitter.emit (events.js:98:17)
at readableAddChunk (_stream_readable.js:156:16)
at Socket.Readable.push (_stream_readable.js:123:10)
at TCP.onread (net.js:509:20)

On Mac OS 10.9.4

Hello Steven,
As it is described in the announcement:
Note: If you receive an error upon updating your DMXzone Extension Manager for Dreamweaver, please do a full reinstall by downloading the latest version from DMXzone.

Teodor...
Sorry was not too specific. Going a bit fast. Tried to install by clicking on message that comes up when entering Extension Manager. This only caused Extension Manager to crash/close. Restarted Extension Manager. Update message appears on opening, click on it and same problem = crash/close. Did another restart but cancel opening message to do Update. Tried to update from inside Extension Manager (red button under System), but this too crashed/closed. Solved it by downloading new EM and installing it manually following the wizards prompts. So now ok. I have screen shots of the two different error messages if you want me to send them.

I did a fresh install from the site. This is now what I am getting.

And now when I open dreamweaver I get a ton of errors and I can't get rid of this popup making dreamweaver not usable.

Downloaded and installed latest version and still has the following errors:

Uncaught node.js Error

Error: err >= 0
at exports._errnoException (util.js:676:20)
at ChildProcess.spawn (child_process.js:973:11)
at exports.spawn (child_process.js:753:9)
at Registry.get (C:\Users\AppData\Local\Temp\nw1032432_26885\node_modules\winreg\lib\registry.js:332:14)
at eval (C:\Users\AppData\Local\Temp\nw1032432_26885\lib\dreamweaver.js:166:11)
at eval (fs.js:258:14)
at Object.eval [as oncomplete] (fs.js:97:15)

For Patrick - please look at:
www.dmxzone.com/support/22670/topic/59789/

For all others: all those uncaught errors are very different, please download and do a full install of the latest DMXzone Extension Manager 1.02

If you still receive an uncaught exception error, please report it in a new topic with details when it comes up.

I'm closing this topic as errors need to be reported separately.