WMS upgrade to 3.5 fails on MongoDB version

Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • #106482
    lolix
    Participant
    • Total Post: 271
    • Jacked into The Matrix
    • ★★★★★★

    “Current remote MongoDB is 4.2.12. WMS requires 4.2.16”

    I don’t remember having installed MongoDB separately from WMS, did I ?

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

    Not in any of my experience. I’ve made many WMS test servers and the database is in the main upgrade or install file.

    #106556
    lolix
    Participant
    • Total Post: 271
    • Jacked into The Matrix
    • ★★★★★★

    Thanks for your reply, that was I thought.

    Did you succeed to upgrade to WMS 3.5 ?

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

    I have not yet. But I will post here my results when I get a chance.

    #106599
    epa80
    Participant
    • Total Post: 208
    • Jacked into The Matrix
    • ★★★★★★

    Not sure this has anything to do with your upgrade, but we’re getting ready to upgrade our WMS from 3.3 to 3.5. Our Dell SE sent us this step to do ahead of time, as it’s something they’ve seen cause 3.5 upgrades to fail.

    In my lab instance the “LocalRepository” value was blank and I just had to add the repository path to the reg value and I was all set…

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

    Sorry I didn’t get back to you but, I did upgrade one of my test servers with no problems.

    #106601
    lolix
    Participant
    • Total Post: 271
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    I just checked the “localrepository” entry. It is not blank and refers to valid location.

    Please someone who performed the upgrade share a md5 checksum of the installer to make sure we’re talking about the same installer.

    My WMS_3.5.exe MD5 is  335fb180996af4e5e7f34e6564f694c4

    (use CertUtil -hashfile <path to file> MD5)

    #106647
    IT D
    Participant
    • Total Post: 4
    • Newbie

    I installed WMS 3.5 on a different server and copied the files located in “C:\Program Files\DELL\WMS\MongoDB\bin” to our production server and restarted it.  Once it loaded up, I checked the mongod.txt file and it said it loaded db version v4.2.16 (4.2.12 previously).  I then checked the web interface and it worked just fine.  Finally, I ran the WMS 3.5 installer on my production server and it went through and installed.

    Thankfully, WMS 3.5.1 installed right on top of that with no additional modifications.  I also ran a log4j scan from Nessus after the install and it came back clean.

    #106658
    [email protected]
    Participant
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    Hello, I ran into problems when doing the upgrade like IT D mentions to do.
    I can’t find the file “mongod.txt” either??
    Please advise.
    thanks a lot
    Peter

    #106659
    IT D
    Participant
    • Total Post: 4
    • Newbie

    That should be located here:

    C:\Program Files\DELL\WMS\MongoDB

    #106660
    [email protected]
    Participant
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    Ok, you mean “mongod.log”?
    Because in that file I can see an entry “db version v4.2.16”

    #106661
    IT D
    Participant
    • Total Post: 4
    • Newbie

    Yep, it’s just a log file to show that it properly loaded the new version.

    #106662
    [email protected]
    Participant
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    The update to v3.5.0.866 went fine, no errors.
    But now the webpages are no longer available??
    Both don’t work anymore 🙁
    https://wyseserver.domainname.be/ccm-web
    https://wyseserver.domainname.be/ccm-web/admin

    #106664
    vinz
    Participant
    • Total Post: 55
    • Back Stage Pass
    • ★★★★

    Look for “Dell WMS: MongoDB” and “Dell WMS: Tomcat Service” services.

    They may be not started

    It is often the case for me after a WMS update and a server reboot, I have to start these services manually

    #106665
    [email protected]
    Participant
    • Total Post: 37
    • Frequent Flyer
    • ★★★

    Both services are started.

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