WMS 3.5.1 fails to install – Couldn’t not retrieve database details

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #106654
    ahmnoor
    Participant
    • Total Post: 26
    • Regular Joe
    • ★★

    Hello

    We were on WMS 3.1. Upgrade succeed to 3.2.1, then to 3.5, when trying to upgrade to 3.5.1, the below message display before the installation wizard

     

    Any idea what the issue could be?

    #106676
    Chris S
    Participant
    • Total Post: 62
    • Back Stage Pass
    • ★★★★

    Are you one server 2016 or 2019 and use SCCM? I found out wms uses SCCM port and had to change the port in : C:\Program Files\DELL\WMS\Tomcat-9\conf\server.xml.

    I ask Dell what was recommended to change it to and they wouldn’t really give me an answer.

    https://www.dell.com/community/Wyse-Management-Suite/Tomcat-crash-after-windows-update-on-2016/td-p/7308379

    #106677
    Chris S
    Participant
    • Total Post: 62
    • Back Stage Pass
    • ★★★★

    Sorry I read it to fast and didn’t fully read the screen shot you put in there. Ignore my post since I can’t erase it.

    #106681
    sanguinettg
    Participant
    • Total Post: 35
    • Frequent Flyer
    • ★★★

    i had the same issue.  the only thing i could do was un-install WMS completely and re-install 3.5.  Luckily it is a lab box, but all my settings got erased and i am starting from scratch again.  Ruined 3 months of testing setup.

    #106682
    Wulfgari
    Participant
    • Total Post: 28
    • Regular Joe
    • ★★

    If you have a virus scanner on the WMS server, be sure to deactivate it when upgrading!

    #106687
    Jim Lathan
    Keymaster
    • Total Post: 314
    • Jacked into The Matrix
    • ★★★★★★

    When I consult WMS users, I always recommend upgrading without skipping a version, even if the document states you can. Also, make sure that you have no Jobs pending.

    – WMS_3.5.1.exe binary can be used if you are installing Wyse Management Suite for the first time or upgrading from previous versions 3.2/3.2.1/3.3/3.5.

    – If you are using Wyse Management Suite 3.3.1, you must upgrade to 3.5 before upgrading to 3.5.1.

    3.5.0.866, 3.5 15 Nov 2021
    3.3.1.29, 3.3.1 16 Aug 2021
    3.3.0.276, 3.3 05 Jul 2021
    3.2.1.44, 3.2.1 17 May 2021
    3.2.0.780, 3.2 26 Mar 2021
    3.1.1.580, 3.1 HF1 25 Feb 2021
    3.1.559, 3.1 04 Dec 2020

    #106702
    ahmnoor
    Participant
    • Total Post: 26
    • Regular Joe
    • ★★

    Thanks guys. I have tried all, no luck. I re-produced the issue in a fresh server with no AV, clean installation of WMS 3.5, can’t upgrade to 3.5.1. Still getting the database error.

    #106709
    Jim Lathan
    Keymaster
    • Total Post: 314
    • Jacked into The Matrix
    • ★★★★★★

    Do you have pending jobs? If so, make sure to clear by either having outstanding devices check-in or force unregister the device that is outstanding.

    #106712
    ahmnoor
    Participant
    • Total Post: 26
    • Regular Joe
    • ★★

    I raised a case with Dell support and here is the response “When the default installation path is not used, the issue occurs. The engineering team is working on a fix “

    #106839
    ahmnoor
    Participant
    • Total Post: 26
    • Regular Joe
    • ★★

    FYI everyone, Dell released WMS 3.5.2, which fixes the above issue

    Dell Wyse Management Suite version 3.5.2 | Driver Details | Dell US

     

    #106856
    WyseVet
    Participant
    • Total Post: 21
    • Regular Joe
    • ★★

    We have our install set to a D: drive and was able to successfully update from 3.2 to 3.5.2 after using the updated install (3.5.2).

    Went well and no issues. And subnets are now properly sorted! (Sore spot for me since we began with WMS)

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.