WinkDk
1 Nickel

Dell Wyse Management Suite 1.3 on-premise http404 error

Hi Everyone,

Got a strange error all of a sudden. The error seems to have appeared after restarting our on-prem server.

Whenever i try to go on to https://[ServerName].[DomainName].local/ccm-web/ i just end up at either a blank white page, or with a error 404 code. Depends on the use of http / https.

Detailed description:
This error (HTTP 404 Not Found) means that Internet Explorer was able to connect to the website, but the page you wanted was not found. It’s possible that the webpage is temporarily unavailable. Alternatively, the website might have changed or removed the webpage.

Services running:
Dell WMS: MatiaDB
Dell WMS: memcached
Dell WMS: MongoDB
Dell WMS: MQTT Broker
Dell WMS: Tomcat Service

Does Dell WMS not use Mosquitto anymore? As i see it's still mentioned in the documentation for version 1.3-

Anyways I would normally think that an Error 404 comes down to either a service not running or a missing page file.

Went on to check IIS as well

Nothing supprised me here really. Application pools were online and the sites were running. Keep in mind that i do run a MBAM site on the same server as well, that hasn't had any IIS issues before or after this.

I was also able to hit the IIS on both port 80 and 8443, so it doesn't seem to be an issue either.

Any suggestions?

 

 

0 Kudos
2 Replies

Re: Dell Wyse Management Suite 1.3 on-premise http404 error

You mention IIS.   WMS does not leverage IIS, and if you want them to co-exist on the same server you would have to be careful that the ports dont conflict. 

I suggest you disable IIS services, reboot and test again.

0 Kudos
WinkDk
1 Nickel

Re: Dell Wyse Management Suite 1.3 on-premise http404 error

Yes, it was just to clearfy that we do run both on the same web server.
IIS for Bitlocker and Tomcat (apache) for WMS, if i'm not mistaken.

They currently do co-exsist, and have done so since the installation of Dell WMS, without any problems until now.

Even though port bindings and such shouldn't have been changed recently, that would be my last resort to check.

Yeah, couldn't hurt to test it. Ill hopefully get around to it a bit later today.

 

Thanks

0 Kudos