1

1.5.00108

Known Issues:

79860 - Blank devices page for certain servers

80161 - “Cannot connect to event service” error message

79702 - SpiceworksEventstoreProcessor service will not stop/restart

Fixes:

79839 - Invite New User modal shows First Name in the Last Name field

80319 - Historical Data view only shows 1 hour of data

80363/80364 - 1.4 → 1.5 Upgrade Issue fixes

80654 - No historical data for ping-type devices

Grab the latest version here ( Stay Ahead of Cyber Threats: Monitoring the Monitors Explained - Spiceworks )

10 Spice ups
2

Thanks!

3

woot!

4

I upgraded from 1.5.00105 (Fresh Install) and the one issue I was seeing (80654) is fixed! Nice!

1 Spice up
5

Did update from clean install 1.5.00105 to 1.5.00108

History llooks ok 24h

INF003_history_24hr.PNG
INF003_history_24hr.PNG800×252 22.4 KB

De monitor service stops again.

SpiceWorks_Monitor_Service_stops.PNG

Ping device not added and tested yet.

We cannot use SNMP security only allows SNMP v3

2 Spice ups
6

Wide-Vean, can you send over your logs so that we can take a look at 'em?

I’ll PM you with instructions.

7

Yes I can please sent me what you need an how to send total log dir is 1.3GB

8

Tray icon also crashes

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: TrayNotifier.exe

Problem Signature 02: 1.5.108.0

Problem Signature 03: 577694cf

Problem Signature 04: TrayNotifier

Problem Signature 05: 1.5.108.0

Problem Signature 06: 577694cf

Problem Signature 07: 84

Problem Signature 08: 67

Problem Signature 09: System.ArgumentException

OS Version: 6.1.7601.2.1.0.272.7

Locale ID: 1043

Additional Information 1: 25f1

Additional Information 2: 25f13065d97317b3c95d50810c178eb6

Additional Information 3: 128d

Additional Information 4: 128d2833516b224cae069b4094689f69

Read our privacy statement online:

If the online privacy statement is not available, please read our
privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

9

I’ve upgraded from the previous version to 1.5.00108 and have the following issues:

  1. The tray icon crashes

  2. Spiceworks Monitor Service keeps stopping and has to be constantly restarted

  3. Dashboard charts do not update after spiceworks monitor service crashes

I saw similar reports like this in previous versions as well.

2 Spice ups
10

Mostly ok but cannot change the password on the account used for window servers and cannot add new as it wont let me type a password, then says password box cannot be blank…genius!!!

1 Spice up
11

I really want to use Network Monitor but, even at the perfect price (you gotta love free), it’s feeling, well, flaky. Each new release seems to cause new problems for a few people.

Is this in the nature of network monitoring software? I’ve not used anything else so I wonder if even paid apps have these issues?

2 Spice ups
12

FYI for backup of our setup

ok fresh install on a win7 pro VM and i use the migrate tool from support for network monitor.Head to :

Can I move my installation to a different machine?

link is migrate

13

Hey everyone - sorry for the issues again; thanks to Wide-Vean, I’ve found one edge case that slipped through and would likely be the source of monitor service crashes.

I’ve committed a fix that the team will look at when they get back into the office tomorrow, as well as one that’ll address the TrayNotifier.exe crashes.

If you want to solve TrayNotifier.exe crashes now, it’s a simple workaround:

  1. Go to your Network Monitor install directory.

  2. In the collector folder, open MonitorService.exe.config.

  3. Look for the following line:

    <level value="WARN" />

  4. Replace it with this:

    <level value="INFO" />
3 Spice ups
14

I changed the setting TrayNotifier.exe and this works.

15

I’ve also made the changes to the MonitorService.exe.config file as instructed and this seems to fix the TrayNotifire crash issue but not the monitor service. This service still continuously stops after a few seconds and has to be manually restarted after which it stops again. I am confident you guys will sought this issue out as you always have. Keep up the good work!

16

Yesterday the monitor
services was crashing within 10 minutes.

I did a reboot of the Server.

Monitor services worked the whole night until I started the browser to see the monitoring this morning.

When I use a browser to see the monitoring the service went down but started again.

The memory is very high the vm has 6GB memory and it is a dedicated monitor server.

INF003_Memmory_last_24h.PNG
INF003_Memmory_last_24h.PNG800×182 15.6 KB

The application swevenstore.exe is using a lot of memory

INF003_high_mem.PNG

Also the CPU is spiking between 5% and 78%

17

Can also confirm changing config file works!

18

Can I report that the 24 hour display is still only showing 1 hour’s worth of history

1 Spice up
19

I’ve already posted this here: Network Monitor 1.5 Not working

But having been using the Network Monitor since its release I have had to revert back to version 1.4.00264 which was the last stable version.

Sadly, in my experience, v1.5xxxx does not work. It would run and load the dashboard complete with the list of Servers, Switches and Online Watchlists but all of the graphs would be empty.

Uninstalling 1.5.00108 and replacing it with 1.4.00264 has made it all work again.

I’m really hoping for a fix for this soon because I do like the idea of the monitor recording history.

20

phgannon, did you manage to restore your old data after reverting to the last stable version? If so, how did you accomplish that? - Thanks in advance!