UNSOLVED

rtwright68

updated

9 years ago

R

rtwright68

1 Rookie

•

4 Posts

1

30009

June 26th, 2017 10:00

On-premise Dell Wyse Management Suite issues

We have the on-premise WMS installed and configured, can access the login page externally and internally using a fully signed SSL certificate (it is our corporate wildcard certificate).  

The problem occurs when we try to configure the Wyse thin client to connect to the correct address.

We see an error message 7512.  We also sign up for a demo account of the hosted version of WMS and configuring it with the options as outlined permits the thin client to connect to it immediately.

I'm suspecting that there is some kind of redirection issue happening with the WMS on-premise installation, because the setting is configured and adds a :443 at the end (can't see a way to modify that), which when we attempt to bring up the page from a browser, gives us an HTTP status 404 error.

I'm hoping someone can give some insight on this issue.  Not sure if some settings need modified in the Tomcat configuration to properly route the requests? 

  • bbattle

    2 Posts

    24731

    0

    Posted July 18th, 2017 16:00

    We are having an issue getting the software to run at all. Get the same 404 error when going to http://{servername.domain.tld}/ccm-web, type Status report, message /ccm-web, description The requested resource is not available. Cannot connect locally, or outside of the server. We've installed this on 2 Windows Server 2012 servers, attempting to get something to work, and fails with the same error. Tomcat is running, as we can hit http://localhost:8080, and grant rights to the management views through the XML.

  • JK-PBA

    2 Posts

    24730

    0

    Posted August 12th, 2017 22:00

    I have the exact same problem, except I don't understand where you are getting the 404 error.   Do you mean when you point a browser to WMShost.yourdomain.com:443?    I get a default Tomcat is installed page for that. 

    Did you find a solution for this?

  • bbattle

    2 Posts

    24768

    2

    Posted August 14th, 2017 09:00

    Yes, I ended up finding the solution for Dell on this one. They have a bug in their installer code, when creating the Tomcat application for WMS. If you choose the default options, (do not choose custom install), it will install without a problem. I installed this on 2 different servers, one of which was a clean install of Windows Server 2012 R2 and had the same problem. On a whim, I decided to take the defaults on the install and the WMS site popped up. I have other problems with WTOS communications, but that's unrelated to this installation problem.

  • JK-PBA

    2 Posts

    24768

    0

    Posted August 14th, 2017 20:00

    Thank you!   That worked for me too.

  • DELL-Jason G

    6 Operator

    •

    6 Posts

    24768

    0

    Posted October 23rd, 2017 12:00

    I ran into this with another customer.  WMS was installed on Server 2016 using Default settings.  Customer added their own certificate which was valid.  WTOS device had valid time and certificate information.

    Error messages were:

    SSL: error ERR_SSL_NO_CIPHER_MATCH! 

    SSL: unable to setup connection, (err=-7512)

    CCM agent open http error! errno:7512

    Issue was resolved by upgrading the WTOS firmware from 8.1.x to 8.4.108.

  • SCSIgate

    1 Message

    24904

    0

    Posted February 8th, 2018 13:00

    Thanks bbattle. 

    Was having the same 404 troubles with WMS 1.1 install as I initially did the custom install option but selected all embedded databases. Uninstalled it and selected the typical install and the ccm-web console was available after the install.

    Cheers,

  • LiborD

    1 Message

    24719

    0

    Posted March 6th, 2018 04:00

    Had the same issue with 404 displayed after installing Wyse Management Suite 1.1 and default option.

    The issue was with a password for DB - it should not contain any special characters. This is a lame software btw...

  • rongarvin

    3 Posts

    21681

    0

    Posted September 20th, 2018 13:00

    Trying to install WMS 1.2 on Windows Server 2016.  Install finishes and I get the 404 error.  Have checked the DB password is simple and all other suggestions here about not using custom, (didn't anyway).  Looked in c:\inetpub\wwwroot\ and there is no ccm-web directory created at install. all services reported started.

     

    Ron Garvin

    rgarvin@univ-computers.com

  • Aloysious

    2 Posts

    12825

    0

    Posted October 4th, 2018 08:00

    So is there no reply from a dell rep here? I am having this issue on server 2012R2, fresh install and have never selected anything other than default settings, but it always look for this ccm-setup that never gets installed.

    Anyone????

  • DELL-Scott H

    Moderator

    •

    1072 Posts

    •

    5038 Points

    5177

    1

    Posted October 4th, 2018 09:00

    Are you using the WMS 1.2 HF1 installer?

    Have you confirmed there is nothing else installed on the VM that may cause port conflicts?

    Have you confirmed the windows firewall is disabled?

    Do all of the "Dell WMS.." Services start?

    http://downloads.dell.com/wyse/WMS/1.2_HF1/WMS_1.2_HF1.exe

    Does the install complete successfully without errors?  

    After install completes there should be a shortcut on the desktop for "Launch WMS" that will launch a browser to the URL of your WMS Server, such as

         https://dell-wms-pro.delldemo.int/ccm-web

    try replacing the FQDN with the IP of the server

    https://yourip/ccm-web/

    What shows in that page?

    In a new installation that will spawn the initial setup steps. 

     

     


    DELL-Scott H
    #IWork4Dell