1

I recently removed the previous version from my monitoring machine, rebooted and deleted the folders under Program Files. Downloaded v 1.5.96, installed, added our official wilcard certificate and rebooted again.

After this the page loaded fine, but I was unable to add any devices - error message said it couldn’t connect to the collector. Checked out the services, and sure enough - the Spiceworks WsProxy was not started.

Now I cannot seem to get it running either - all I get it is Error 1067: The process terminated unexpectedly.

Any ideas?

3 Spice ups
2

Hey Henrik,

Sorry to hear about the issues with the service. What OS are you hosting NM on? Is it Windows 10?

3

Win 7, SSD and 4 GB RAM. The machine is used for monitoring only.
Is it possible that the certificate creates these kind of issues? In the previous version I used the default certificate…

4

Today I removed the non-working installation. Rebooted and installed again, followed by yet a reboot. This time all services was running smoothly, and no errors as I added the devices from scratch. Puh!
I know there was a tool to export all devices and credentials, is that posted somewhere? Hopefully I can export\import next time, it’s a tideous job to re-build the whole environment for every time something breaks during an upgrade…

5

Henrik,

Huh…well, I’m glad you found a work-around! The tool to export the data isn’t finished just yet. Its something I am personally pushing to get done, as we definitely realize how much of a pain it can be to have to set everything up from scratch. The steps are at the bottom of the following page: https://community.spiceworks.com/support/network-monitor/docs/setup

1 Spice up
6

Thanks, Peter!! Just what I was looking for.

BTW: Under the Known issues section there is mentioning of the Remote Collector - what has that got to do with anything?

7

Glad I could help :slight_smile:

That’s just awkward wording. Something like this would make it slightly more clear and easy to understand:

“There’s a known bug that happens occasionally concerning the Network Monitor being unable to connect to the devices it is monitoring after a migration (using the script). The current fix is to edit the credentials after importing and saving. You don’t actually have to change anything, just “edit” them and re-save.”

1 Spice up
8

Yeah, thought so. As you actually have a function called Remote Collector in the standard Spiceworks app, it can get confusing…

9

Yep, that’s a typo; sorry about that. The technical writer probably got confused because a portion of the code in Network Monitor is known as the “collector”. Easy mistake to make.