Network Monitor - Devices stuck on loading

sphyncter · 2014-12-23T23:13:39.000Z

All devices that i have in the Network Monitor are stuck trying to get information.

This was on version 1.0.1 so i decided i’d try to update to 1.0.2 to see if that fixed it up. After the upgrade all of my devices still look like this, just continously polling for information. So i decided to check the Spiceworks Windows services. Restarted the Spiceworks App Server. That seemed to just reset the web services and when it came back all my devices we’re still polling for information. Restarted the Spiceworks Monitoring Service, still nothing. Restarted the Spiceworks Event Processor and got the error ‘Windows could not stop the Spiceworks Event Processor service on the local computer. Error 1053: The service did not respond to the start or control request in a timely fashion’

So i figure that was the service that was stopping my devices from polling. Rebooted the server and everything came good.

Server specs are:

Physical

CPU - 4 core 3.2ghz

RAM - 8GB

OS - Server 2008 64-bit

jaimedelapaz · 2014-12-29T13:30:23.000Z

Hi,

Are you accessing the monitor directly on the server it is installed on or are you accessing it from another machine? Can you ensure the ports listed on this article are not blocked by a firewall:

http://community.spiceworks.com/help/Spiceworks_Network_Monitor#Install

sphyncter · 2014-12-29T21:42:00.000Z

Trying it from a remote PC. Definately not a firewall issue at all of those ports are open.

I would assume it has to do something with that service that crashed out as its been fine ever since.

jaimedelapaz · 2014-12-30T18:24:50.000Z

That may be it. Its odd that it wasnt working before. Keep an eye on it and let me know if you run in to this again.

sphyncter · 2015-01-04T23:54:24.000Z

This has since happened again. Are there any logs i can send through that would help?

timwalker8323 · 2015-01-06T17:47:27.000Z

I have the exact same issue. It worked after the initial install, in fact it worked for a couple of days. Left for the holiday break and now it just “loads” info. I have installed and uninstalled the program and restarted the spiceworks service on the server.

mohammedshajin8199 · 2015-04-30T09:51:18.000Z

I am facing the exact same issue as well. This is a daily occurrence for us now and it will normally work for a while after a reboot. I have updated to the latest version but that has not cured the problem unfortunately

Same problem accessing directly on the server or remotely and all ports are open.

al23592 · 2015-05-07T13:21:30.000Z

I’m having the same issue as well, except restarting services or the computer itself don’t bring it back to normal. It looks like re adding the devices is the only way to get them back.

Daffy-Admin · 2015-07-16T11:45:31.000Z

I just installed the latest (v1.2.197) onto a new Win 2008 R2 virtual that I specifically built for this.

Have had this issue since the install.

Firewall is disabled so ports are not the issue.

Sometimes restarting the services works, sometimes I have to do a full reboot to get it working.

Have noted on several occasions that the Spiceworks Event Processor was down. Nothing was in the event log as to it going down. Looked in the application logs and do not note any errors.

krzysztofturkiewicz2 · 2015-09-22T03:45:27.000Z

I have exact the same issue - any solution ? Its installed on windows server 2012 R2.

brentwarren · 2016-01-04T13:11:02.000Z

Same Issues

fabianberger7759 · 2016-03-03T11:36:08.000Z

I have the same issue → windows server 2012

ricardocorral · 2016-04-26T17:24:16.000Z

I can get it back to working by going to the Task Manager and kill the SpiceworksEventProcessor.exe process, then start the service back on Computer Management > Services.

bishop44 · 2016-06-23T15:27:00.000Z

has this been resolved ?? i just installed and i am getting the same. I thought it was my server (2008r2) but apparently not. I think this will be a great tool once the bugs are eradicated.

hafizyousaf · 2016-07-19T06:06:18.000Z

Same issue till now… Installed the latest version v1.5.111 on Win Server 2008 R2…

The Spiceworks Monitor Service crashes/Stops

markstephenson · 2016-07-22T03:07:53.000Z

same issue here

andybiddle · 2016-07-28T15:21:51.000Z

I made a batch file with the following commands, it’s the only method I’ve found to fix the issue for me. I had to use a “taskkill” for the Spiceworks Event Processor service, it would hang and fail to stop. Reboots did not help, for whatever reason this does. Good luck! (Currently on version 1.5.00111 )

@ECHO OFF
net stop “Spiceworks WsProxy”
taskkill /f /im “spiceworkseventprocessor.exe”
net stop “Spiceworks Monitor Service”
net start “Spiceworks Event Processor”
net start “Spiceworks Monitor Service”
net start “Spiceworks WsProxy”

bishop44 · 2016-07-28T15:30:12.000Z

didn’t work for me. I mean the bat file ran successfully but it did not fix my issue (devices stuck on loading).

The Spiceworks team just needs more development time. I love the concept but the program is just not ready for full dispersion yet. my2cents

dduijvekam · 2016-09-06T12:40:57.000Z

I got the same issue, did not update anything.

jaredfire · 2016-09-09T16:08:16.000Z

Yeah same issue here but generally a restart will resolve the issue. Windows 10 x64 OS monitoring locally.