Hi to everybody,
I've installed centreware web without any problems. The web-config appliction can be used and does not show any error.
But the web interface is not working. Only:
HTTP Error 503. The service is unavailable
How can I verify if all the required services are up and run correctly? in the services.mcs there isn't any service that call centrewareweb... only sql server instances, and these are correctly running.
The windows firewall is not enabled.
Any idea? Any trouble shooting guide?
The CentreWareWeb verision is 6.5.19
the SQL server is 2017 - 14.0.1000.169
the OS is Windows Server 2019 version 1809 (OS BUILD 17763.199)
Anybody can hel me??
Thanks fo helping.
This could be an authentication error. I do have a link to the our troubleshooting from Xerox.com that you can search the issues.
We also had the same issue in the UK and only with some of our sites.
No browser would work either locally or via a support server. Ping would work. Sometime you could connect to the homepage but Admin login would not work.
Virgin Media pushed through new MTU settings throughout the network. The intermittent working of our Xeroxes seems to be due to the packet MTU size changing on the Broadband. This is controlled on the Virgin Media Broadband side and not us. When the MTU size changes/increases slightly, the webpage loads albeit slowly thus various factors can affect the change of MTU primary, one being the quality on the line, distance from exchange etc.
Installing new FTTP lines and upgraded modems should resolve this issue for us.
Were you able to resolve this issue?
According to the software requirements for the latest version of CentreWare, Windows Server 2019 is not listed as a compatible OS. We're looking to upgrade our server to 2019, but don't want to do it if it's going to cause problems we can't resolve.
This issue was just via connecting to the homepage of the printers. Yes, we upgraded the BB lines and installed the newer modems that came with them. It was a painful 11 weeks. It wasn't the server or broswer levels causing the issue because some sites connecting were working fine. Our XDM was running from Windows 2012r2. The issue we saw was via any web browsers. You could ping the printer, you just couldn't connect to the homepage, or if you could, the admin & password wouldn't work, even if a local NVM factory reset was done on the printer.