1.5.00111

[peterb99 (Peter B (Spiceworks))]

Advertisement

Close

1.5.00111

Advertisement

Close

Known Issues:

Advertisement

Close

79860 - Blank devices page for certain servers

80161 - “Cannot connect to event service” error message

79702 - SpiceworksEventstoreProcessor service will not stop/restart

Fixes:

80844 - Fix to make historical data component more crash-resilient

80840 - TrayNotifier.exe (tray app) crashes due to unsupported logging level

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

[peter]

will have a go fingers crossed

[las]

Had to remove and re-add ALL the devices (Server, Network and Online) - Fixed some issues.

Had to run SERVICES.MSC and edit Collector Service Restart Tab to have all 3 Options set to Restart.

Not saving SNMP credentials but do save Server credentials.

Network devices still not SNMP GETting anything

[markpimperton (Mark8081)]

Upgraded and now delighted to have a working Devices page! I’ve not played with History at all yet. But, for now, this seems a good update.

[brianfoley]

Monitor service crashes in less than 5 minutes, but hey, the Traymonitor is still working!

Details from Application log:

• System

• Provider

[ Name] .NET Runtime

• EventID 1026

[ Qualifiers] 0

Level 2

Task 0

Keywords 0x80000000000000

• TimeCreated

[ SystemTime] 2016-07-07T14:06:00.000000000Z

EventRecordID 3357

Channel Application

Computer dc-netmon1.infrastructure.local

Security

• EventData

Application: MonitorService.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: Spiceworks.Monitoring.Core.Exceptions.ApiTypeNotFoundException at Spiceworks.Monitoring.Core.Services.Persistence.Redis.Repository1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Find(Int64) at Spiceworks.Monitoring.Core.Services.Events.InfluxClient.<GetHdEnabledDevices>b__23_1(Spiceworks.Monitoring.Core.Model.RetentionTimescale) at System.Linq.Enumerable+WhereSelectListIterator2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Linq.Enumerable+WhereEnumerableIterator1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at Spiceworks.Common.CollectionExtensions.ForEach[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable1<System.__Canon>, System.Action`1<System.__Canon>) at Spiceworks.Monitoring.Core.Services.Events.InfluxClient+d__28.MoveNext() at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_1(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

[earmstrong (Eric Armstrong)]

The Traymonitor is working (or appears to be - the amount of time it would take to crash leaves it fairly hard to determine just yet), though I am noticing issues with the Spiceworks Monitor Service crashing as well.

EVENT LOG 1:

• System

• Provider

[ Name] .NET Runtime

• EventID 1026

[ Qualifiers] 0

Level 2

Task 0

Keywords 0x80000000000000

• TimeCreated

[ SystemTime] 2016-07-07T15:53:26.000000000Z

EventRecordID 28502

Channel Application

Computer:

Security

• EventData

Application: MonitorService.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: Spiceworks.Monitoring.Core.Exceptions.ApiTypeNotFoundException Stack: at System.Runtime.CompilerServices.AsyncMethodBuilderCore.b__5(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

EVENT LOG 2:

• System

• Provider

[ Name] Application Error

• EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

• TimeCreated

[ SystemTime] 2016-07-07T15:53:27.000000000Z

EventRecordID 28503

Channel Application

Computer REMOVED NAME

Security

• EventData

MonitorService.exe

1.5.111.0

577d76d1

KERNELBASE.dll

6.1.7601.23418

5708a7e4

e0434352

0000c54f

394

01d1d866f6533941

C:\Program Files\Spiceworks\Network Monitor\collector\MonitorService.exe

C:\Windows\syswow64\KERNELBASE.dll

f12b5b87-445a-11e6-83cd-00155d481a02

I also have a scenario where a SNMP device tells me it times out because of no response in ‘40 seconds’, but it doesn’t attempt to process the request near that long.

Very frequent occurrences of the known bug: 80161 - “Cannot connect to event service” error message

Thank you,

Eric

EDITED: I would like to add, that I have been looking over the server that hosts Spiceworks Network Monitor, and it has been up the majority of the day after the initial hiccup. However, looking over the event logs shows frequent restarts of the Monitoring Service. I did set the server to restart automatically, and I imagine it has not had any further visible problems because it has not crashed 3 consecutive times in the set time frame allotted for said crashes.

[jamesthompson17 (James474360)]

Server alerts and SMTP notifications are ~10 min for 1 min 30 sec ping alerts and monitor dashboard alerts. Tested with several monitored objects and same results. Noticed that if you go into the device’s alerts itself and hit “reset” on the global propagation, this seems to speed up things a bit. But otherwise, extremely slow response time to offline.

[james-wood (Eeyore)]

History is still not showing more than 1 hour of data. I’ve even been deleting and adding back some devices. I believe this is the third release to claim history was fixed

[fernandooliveira4993 (Fernando8522)]

Hello. I’m trying to install on a computer with the following configuration:

Microsoft Windows 7 Professional

Version: 6.1.7601 Service Pack 1 Build 7601

System type: X86-based PC

Intel (R) Core ™ 2 Duo CPU E8400 3.00GHz, 3000 MHz

2 Core (s), 2 processor (s) course (s)

Physical memory (RAM) Installed: 4GB

However, the installation fails and I get this log:

[1198:0D94][2016-07-07T16:14:58]i001: Burn v3.10.1.2213, Windows v6.1 (Build 7601: Service Pack 1), path: C:\Users\fernando\Downloads\SpiceworksNetworkMonitor.exe

[1198:0D94][2016-07-07T16:14:58]i009: Command Line: ‘’

[1198:0D94][2016-07-07T16:14:58]i000: Setting string variable ‘WixBundleLog’ to value ‘C:\Users\fernando\AppData\Local\Temp\Network_Monitor_20160707161458.log’

[1198:0D94][2016-07-07T16:14:58]i000: Setting string variable ‘WixBundleOriginalSource’ to value ‘C:\Users\fernando\Downloads\SpiceworksNetworkMonitor.exe’

[1198:0D94][2016-07-07T16:14:58]i000: Setting string variable ‘WixBundleOriginalSourceFolder’ to value 'C:\Users\fernando\Downloads'

[1198:0D94][2016-07-07T16:14:58]i052: Condition ‘VersionNT > v5.1’ evaluates to true.

[1198:0D94][2016-07-07T16:14:58]i000: Setting string variable ‘WixBundleName’ to value ‘Network Monitor’

[1198:0D94][2016-07-07T16:14:58]i000: Setting string variable ‘WixBundleManufacturer’ to value ‘Spiceworks’

[1198:1140][2016-07-07T16:14:58]i000: Setting version variable ‘WixBundleFileVersion’ to value ‘1.5.111.0’

[1198:0D94][2016-07-07T16:14:58]i100: Detect begin, 2 packages

[1198:0D94][2016-07-07T16:14:58]i000: Setting numeric variable ‘UNUSED01’ to value 1

[1198:0D94][2016-07-07T16:14:58]i000: Setting string variable ‘NETFRAMEWORK45’ to value ‘394271’

[1198:0D94][2016-07-07T16:14:58]i052: Condition ‘NETFRAMEWORK45 >= 378389’ evaluates to true.

[1198:0D94][2016-07-07T16:14:58]i101: Detected package: NetFx45Redist, state: Present, cached: None

[1198:0D94][2016-07-07T16:14:58]i101: Detected package: NetworkMonitor, state: Absent, cached: None

[1198:0D94][2016-07-07T16:14:58]i199: Detect complete, result: 0x0

[1198:0D94][2016-07-07T16:15:02]i200: Plan begin, 2 packages, action: Install

[1198:0D94][2016-07-07T16:15:02]w321: Skipping dependency registration on package with no dependency providers: NetFx45Redist

[1198:0D94][2016-07-07T16:15:02]i000: Setting string variable ‘WixBundleRollbackLog_NetworkMonitor’ to value ‘C:\Users\fernando\AppData\Local\Temp\Network_Monitor_20160707161458_000_NetworkMonitor_rollback.log’

[1198:0D94][2016-07-07T16:15:02]i000: Setting string variable ‘WixBundleLog_NetworkMonitor’ to value ‘C:\Users\fernando\AppData\Local\Temp\Network_Monitor_20160707161458_000_NetworkMonitor.log’

[1198:0D94][2016-07-07T16:15:02]i201: Planned package: NetFx45Redist, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[1198:0D94][2016-07-07T16:15:02]i201: Planned package: NetworkMonitor, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[1198:0D94][2016-07-07T16:15:02]i299: Plan complete, result: 0x0

[1198:0D94][2016-07-07T16:15:02]i300: Apply begin

[1198:0D94][2016-07-07T16:15:02]i010: Launching elevated engine process.

[1198:0D94][2016-07-07T16:15:04]i011: Launched elevated engine process.

[1198:0D94][2016-07-07T16:15:05]i012: Connected to elevated engine.

[10B4:0FDC][2016-07-07T16:15:05]i358: Pausing automatic updates.

[10B4:0FDC][2016-07-07T16:15:05]i359: Paused automatic updates.

[10B4:0FDC][2016-07-07T16:15:05]i360: Creating a system restore point.

[10B4:0FDC][2016-07-07T16:15:24]i361: Created a system restore point.

[10B4:0FDC][2016-07-07T16:15:24]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}, options: 0x7, disable resume: No

[10B4:0FDC][2016-07-07T16:15:24]i000: Caching bundle from: ‘C:\Users\fernando\AppData\Local\Temp{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}.be\SpiceworksNetworkMonitor.exe’ to: ‘C:\ProgramData\Package Cache{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}\SpiceworksNetworkMonitor.exe’

[10B4:0FDC][2016-07-07T16:15:24]i320: Registering bundle dependency provider: {2c5e2c85-5de2-47f9-a5a1-3a28633f4739}, version: 1.5.111.0

[10B4:0FDC][2016-07-07T16:15:24]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}, resume: Active, restart initiated: No, disable resume: No

[10B4:05BC][2016-07-07T16:15:27]i305: Verified acquired payload: NetworkMonitor at path: C:\ProgramData\Package Cache.unverified\NetworkMonitor, moving to: C:\ProgramData\Package Cache{86A5D54C-EE65-48E9-BF78-6D1FF5A3407B}v1.5.00111\NetworkMonitor.

[10B4:0FDC][2016-07-07T16:15:27]i323: Registering package dependency provider: {86A5D54C-EE65-48E9-BF78-6D1FF5A3407B}, version: 1.5.00111, package: NetworkMonitor

[10B4:0FDC][2016-07-07T16:15:27]i301: Applying execute package: NetworkMonitor, action: Install, path: C:\ProgramData\Package Cache{86A5D54C-EE65-48E9-BF78-6D1FF5A3407B}v1.5.00111\NetworkMonitor, arguments: ’ ARPSYSTEMCOMPONENT=“1” MSIFASTINSTALL=“7”’

[10B4:0FDC][2016-07-07T16:15:29]e000: Error 0x80070661: Failed to install MSI package.

[10B4:0FDC][2016-07-07T16:15:29]e000: Error 0x80070661: Failed to execute MSI package.

[1198:0D94][2016-07-07T16:15:29]e000: Error 0x80070661: Failed to configure per-machine MSI package.

[1198:0D94][2016-07-07T16:15:29]i319: Applied execute package: NetworkMonitor, result: 0x80070661, restart: None

[1198:0D94][2016-07-07T16:15:29]e000: Error 0x80070661: Failed to execute MSI package.

[10B4:0FDC][2016-07-07T16:15:29]i318: Skipped rollback of package: NetworkMonitor, action: Uninstall, already: Absent

[1198:0D94][2016-07-07T16:15:29]i319: Applied rollback package: NetworkMonitor, result: 0x0, restart: None

[10B4:0FDC][2016-07-07T16:15:29]i329: Removed package dependency provider: {86A5D54C-EE65-48E9-BF78-6D1FF5A3407B}, package: NetworkMonitor

[10B4:0FDC][2016-07-07T16:15:29]i351: Removing cached package: NetworkMonitor, from path: C:\ProgramData\Package Cache{86A5D54C-EE65-48E9-BF78-6D1FF5A3407B}v1.5.00111\

[10B4:0FDC][2016-07-07T16:15:29]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}, resume: None, restart: None, disable resume: No

[10B4:0FDC][2016-07-07T16:15:29]i330: Removed bundle dependency provider: {2c5e2c85-5de2-47f9-a5a1-3a28633f4739}

[10B4:0FDC][2016-07-07T16:15:29]i352: Removing cached bundle: {2c5e2c85-5de2-47f9-a5a1-3a28633f4739}, from path: C:\ProgramData\Package Cache{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}\

[10B4:0FDC][2016-07-07T16:15:29]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{2c5e2c85-5de2-47f9-a5a1-3a28633f4739}, resume: None, restart initiated: No, disable resume: No

[1198:0D94][2016-07-07T16:15:29]i399: Apply complete, result: 0x80070661, restart: None, ba requested restart: No

Does the computer is not able to support it?

[markwitteveen (Wide-Vean)]

I did a upgrade from a stable 1.5.00108 and every thing is stabel for about 24H.

only historic dat can be viewed for 1 hour for Server WMI and Devices ping only

SNMP not testesd because we can use SNMP v3 only.

I dit a upgrade from a stable 1.4.00261 and every thing is stabel for about 20H.

only historic dat can be viewed for 1 hour for Server WMI and Devices ping only

SNMP not testesd because we can use SNMP v3 only.

[jcaceresfgrlaw]

I fixed all the problems. I reverted back to version 1.4.264. That is the latest stable version. Note: Always keep a copy of the latest stable version just in case.

[sean-c-sw (Sean C (Spiceworks))]

Hey guys,

Try as we may, we’re unable to replicate any more crashes on the collector on our end. We’re a little low on developer resources over here, so here are some options:

If you’re running into issues with a particular device’s metric history

1. Disable historical data for that device (Devices page → Actions → Stop recording history).
2. Wait one minute.
3. Enable historical data for that device (Devices page → Actions → Start recording history).

If you’re running into issues where a particular device isn’t receiving data

Remove and re-add the device.

If you’re running into issues where no data is coming up, especially if you’ve upgraded

Try a clean uninstall + reinstall of Network Monitor.

If you’re running into issues where the monitor service is crashing, and it’s a clean install

Try removing and re-adding devices one-by-one until you’ve found a device that’s problematic.

Any other issue, and you’ve upgraded Network Monitor

Try a clean uninstall + reinstall of Network Monitor.

As always

Network Monitor uses ports 4094 (collector service), 5555 (processor service), 5556 (websockets), 6739 (redis database), 8005 (app server), 8009 (app server), 8080 (web interface), 8086 (historical data), and 8087 (historical data). Make sure there’s no conflict on those ports with another installed application. We really recommend against keeping Network Monitor and any other Spiceworks install (e.g. Help Desk, Inventory) on the same machine, as we’ve experienced conflicts in the past.

[markwitteveen (Wide-Vean)]

@Sean C (Spiceworks)

Hey guys,

Try as we may, we’re unable to replicate any more crashes on the collector on our end. We’re a little low on developer resources over here, so here are some options:

If you’re running into issues with a particular device’s metric history

1. Disable historical data for that device (Devices page → Actions → Stop recording history).
2. Wait one minute.
3. Enable historical data for that device (Devices page → Actions → Start recording history).

If you’re running into issues where a particular device isn’t receiving data

Remove and re-add the device.

If you’re running into issues where no data is coming up, especially if you’ve upgraded

Try a clean uninstall + reinstall of Network Monitor.

If you’re running into issues where the monitor service is crashing, and it’s a clean install

Try removing and re-adding devices one-by-one until you’ve found a device that’s problematic.

Any other issue, and you’ve upgraded Network Monitor

Try a clean uninstall + reinstall of Network Monitor.

As always

Network Monitor uses ports 4094 (collector service), 5555 (processor service), 5556 (websockets), 6739 (redis database), 8005 (app server), 8009 (app server), 8080 (web interface), 8086 (historical data), and 8087 (historical data). Make sure there’s no conflict on those ports with another installed application. We really recommend against keeping Network Monitor and any other Spiceworks install (e.g. Help Desk, Inventory) on the same machine, as we’ve experienced conflicts in the past.

This version is running for about 48H stable.

only problem is the historic data.

I stoped recording a device and started recording again.

After 24H still only 1H data available how can I see the logging is working.

Is it a idea to ad historic option for 2H ore 4H so you can see earlier that this is works.

[markwitteveen (Wide-Vean)]

Did a clean install and it is running stable for 24H now historic data is working oké for me.

[brianfoley]

I’m beginning to think that something happens to the data during an upgrade that was causing the monitor service to crash. When I first installed 1.5, it ran fine for a few days. After the first update, I was getting constant crashes. I just performed a clean uninstall and re-install and it seems to be running now without a crash.

[robertj]

Can we export the config, servers I’m monitoring, to a file and do a clean uninstall/re-install? Or does it have to be setup from scratch to make it clean?

[rbaker1 (Ryan1)]

@JCaceres-FGRlaw

I fixed all the problems. I reverted back to version 1.4.264. That is the latest stable version. Note: Always keep a copy of the latest stable version just in case.

Are you able to put the file in a Dropbox or something so I can try it please? I am new to using network monitor so have only got copies of the last 3 versions!

Thanks

[geoffpearson (geoff1505)]

I’m running this release on a few servers that are all clean 2012 R2 installs, as well as clean installs of this version of Network Monitor. Everything on the dashboard is working perfectly for me, however none of the servers are sending email alerts. I even entered a bogus IP into the online watchlist that has been ‘down’ for over a day and still haven’t received any email.

Is this a bug or is there something I could try on my end to fix this? The servers all have internet access.

[deanstuckmann4255 (dstuck)]

Everything seems to be working - including the 24 hour logs with a clean install of 111.

My thanks to the team that is working hard to get the issues resolved, and taking the time to improve and add features to the product.

Dean

[conwaywharton7098 (Old-Wolf)]

One issue I’ve seen before has reared it’s head again. Sometimes the monitor seems to get stuck sending out emails that something is wrong, even though everything is fine on the monitor page. The latest occurrence was with one of the Online Watchlist items. Even though it is now green, and has been for the last few hours, it is still sending out an offline alert. When it occurred before, I could simply restart the monitor, but, since that no longer works, the only way to fix it seems to be to restart the computer. Deleting the item from the Online Watchlist does not stop the emails. Other than that, it appears to be running smoothly.

Edit - that didn’t work, it still sent out the message after one hour. I’ve deleted the computer from the Online Watchlist to see if that fixes it.