Spiceworks won't restart

dalecampbell · 2015-07-06T11:35:55.000Z

I recently (within the last 7-10 days) updated to the latest version of Spiceworks. It ran great with no issues over those last 7-10 days. However, during the course of this past weekend, the server my installation resides on had to be rebooted and now Spiceworks will not come back up. The service says it started and is running but I can’t connect to it from any other workstation and when I attempt to launch the Spiceworks Desktop on the server it just sits and spins, never coming up. Any ideas of what I should try to resolve this? I’ve already attempted to reinstall Spiceworks (latest version) but that did nothing. Should I just attempt a roll-back?

workaholic1 · 2015-07-06T11:53:33.000Z

Have you set the service to restart? I remember seeing (in Windows) there is an option to restart the server after the third attempt has failed. You could try that once to see if there is something wrong with SW. I had one upgrade that was causing some problems and I ended up rolling back to an older version, restoring the backup and upgrading it to the latest. Good luck!

dalecampbell · 2015-07-06T13:41:41.000Z

I already have the Spiceworks service set to automatically start when the server starts (if rebooted) and the service is also set to restart the service after any failures (and restart after 3 minutes of any failure). It’s still not working.

matts · 2015-07-06T15:33:57.000Z

Did IIS happen to get started on the machine in question? I’ve seen this happen. Windows Updates roll through, IIS gets turned back on is will bind to ports 80 & 443 at OS start. Then Spiceworks tries to come up, and can’t get access to those ports.

Check that out, and see if the ports Spiceworks is supposed to be using are free and available.

dalecampbell · 2015-07-06T16:14:39.000Z

We don’t have IIS on this server.

matts · 2015-07-06T16:47:55.000Z

Can you do a netstat -nao command on the Spiceworks server?

Is anything running on the ports Spiceworks is running on?
If so, can you match up the PIDs with the PIDs in the task manager?

dalecampbell · 2015-07-06T17:38:34.000Z

These are the only things I see listed for port 80 when I run netstat -nao.

I see nothing mentioning port 443.

TCP 0.0.0.0:80 [::]:0 LISTENING 4

TCP [::]:80 [::]:0 LISTENING 4

matts · 2015-07-06T17:57:19.000Z

PID 4 is IIS. Well, it’s SYSTEM, but it’s IIS.

Check to see if it’s up and running on there. I know that sounds like crazy-talk, but I swear it’s not (I’m sure all crazy people say that).

Microsoft will sneak it onto servers without telling you, and then turn it on without telling you.

Check it out and let me know what you find.

dalecampbell · 2015-07-07T10:47:57.000Z

I looked again and can see nothing that looks like IIS running and none of the PIDs in Task Manager show PID 4. I’m at a loss. I tried uninstalling Spiceworks and reinstalling just for kicks and that didn’t resolve anything either.

matts · 2015-07-07T16:30:06.000Z

When you checked the Task Manager, did you look at the processes for all users?

PID 4 runs as SYSTEM, and normally runs on Session ID 0. You can’t terminate it in Task Manager; you’ll need to find the stop the Internet Information Services service, or remove the Web Server role from the box.

dalecampbell · 2015-07-07T16:57:03.000Z

My manager and I worked on this some more and finally discovered a different service causing the issue. It wasn’t IIS but something else. We just changed several services to Manual instead of Automatic, then restarted the server, and bingo. Spiceworks is back up and running again. Thanks for your help. While your solution wasn’t exactly what we used, it did give us a direction to head and look at things.