Upgrade 9.1.3 to 9.1.4 failed. “Unable to get local issuer certificate”

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #106403
    lolix
    Participant
    • Total Post: 275
    • Jacked into The Matrix
    • ★★★★★★

    All said.

    Yet another certificate thread….

    Where the comprehensive documentation about certificates to install ? (and how to disable them…. Man, I’m on an my own intranet)

     

     

    #106406
    lolix
    Participant
    • Total Post: 275
    • Jacked into The Matrix
    • ★★★★★★

    Forgot to mention that, of course, “CA Validation” is disabled.

    #106421
    brian1020
    Participant
    • Total Post: 259
    • Jacked into The Matrix
    • ★★★★★★

    You went from 9.1.3129 to 9.1.4? If you’re on 9.1.3112 you need to go to 9.1.3129 which was an out of cycle security release. I had no issues upgrading.

    #106428
    RobaHelpdesk
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    I have the same issue with upgrading from 9.1.3112 to both 9.1.3129 & 9.1.4234. I also have this issue when upgrading from WVD 1.2.x to 1.3.x. Seems to be a package error or something?

    With 8.6 we already made an exclusion option in the DHCP with DHCP option 167, CA Validation; FALSE.

    Perhaps this is something like that? Anyhow, friday I have a Teams meeting with a Dell engineer, to see if we can find something about this issue.

    #106429
    brian1020
    Participant
    • Total Post: 259
    • Jacked into The Matrix
    • ★★★★★★

    I use WMS public cloud, what version of WMS are you using?

    #106440
    RobaHelpdesk
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    We are using the on-Premise WMS installation V 3.3.1.29

    … the latest, the greatest …

     

     

    #106441
    lolix
    Participant
    • Total Post: 275
    • Jacked into The Matrix
    • ★★★★★★

    > You went from 9.1.3129 to 9.1.4? If you’re on 9.1.3112 you need to go to 9.1.3129 which was an out of cycle security release.

    That was it. Going through 9.1.3129 solved the problem.

    Thanks !

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