Page cannot be displayed

christophero · 2014-08-28T16:31:14.000Z

It is supposed to run on port 8080 on the server right? I installed a clean Server 2012 VM, installed updates, and installed Spiceworks Monitor beta, and I verified the services are running, but all I get is “This page cannot be displayed” either from the server or another machine.

scottalanmiller · 2014-08-28T16:33:03.000Z

On the local machine do a telnet localhost 8080

christophero · 2014-08-28T16:38:39.000Z

Nope, connect failed there too

shortcircuit · 2014-08-28T16:50:59.000Z

Where did you install to? It has been mentioned that if installed somewhere other than default that the result is what you are seeing.

Also did you try using port 8443(https) as well?

christophero · 2014-08-28T16:53:45.000Z

Went with the defaults, it put it in c:\program files\spiceworks\network monitor.

Just tried 8443 and same thing.

christophero · 2014-09-02T15:43:22.000Z

Hmm, I don’t know what else to do. Found the install.log file, it didn’t tell me anything new. Made sure Windows Firewall was disabled, still nothing

curtsundell7291 · 2014-09-10T18:43:06.000Z

I saw this as well, and found that the service is crashing as soon as it is started. Running on a Server 2012 Standard VM. I’m going to try uninstalling and installing/running in compatibility mode for 2008R2, but would love to find out why the service won’t stay up. I’m assuming that’s the root of the problem I’m having with the app being unavailable.

p-kenward · 2014-09-11T07:22:35.000Z

I had a fresh install of 0.4.2 on Server 2008 R2 fail to create the Spiceworks App Server service. The MSI log file in my temp folder showed that it didn’t have permissions to create the service. I opened an administrator command prompt and ran the failed command (which was in the msi log file) and it then created the service fine. Restarted the other services and I was then able to log in and it has been working for 3 days now. Not sure if it’s the same issue, but thought i’d share the fix if it was.

christophero · 2014-09-11T11:14:04.000Z

Well, Beta 2 did finally install for me, and it ran when I first opened it, but I added 3 servers and 1 switch and now I can’t open it again, it gets stuck on the pepper screen

babbitt · 2014-09-11T14:21:58.000Z

Hey ChristopherO, Do you have some time today to screenshare with me to troubleshoot this?

christophero · 2014-09-11T14:32:56.000Z

Sure, PM sent.

curtsundell7291 · 2014-09-12T15:33:48.000Z

Thanks for the pointer, Paul. I checked the logs, but unfortunately nothing I can act on like that. I’m still in the situation where the installation is successful, but the app service won’t run. I’ve run through the options of setting compatibility, but it appears I’ll just have to try another server.

ottehoman2 · 2014-11-13T21:39:56.000Z

SOLVED: %uFEFF%uFEFF%uFEFF%uFEFFin my case, I had changed my AD password, and so the service could not start, or rather not login.

Solution:Start-menu>“services” and select the Services cogs in the list. Find the Spiceworks service, and right-click, select Properties. Then change the stored password to your new AD password.

Solved it for me, ymmv. Access as usual via http://server.ad.domain:9675/

Otte