WMS MQTT LockBox Url Error after Upgrade from 3.5.2.16 to 3.6.0.241

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #107540
    Black_Box
    Participant
    • Total Post: 6
    • Newbie

    Hi guys,

    a month ago I upgraded the WMS from version 3.5.2.16 to 3.6.0.241.
    But now I have to notice that since this upgrade, the MQTT connection does not work anymore, and also sends error’s.
    In the logfile from the MQTT server I also get the following error message:

    C:\Program Files\DELL\WMS\wmsmqtt\OpenJDK-11.0.10\bin>
    04/14/2022 15:28:34 [6] E:LockBoxKey and Cert Password error. Try again… 2
    14.04.2022 15:28:40 [6] I:API response received as System.Net.HttpWebResponse.
    04/14/2022 15:28:40 [6] I:Received a response from the lockbox url.
    04/14/2022 15:28:40 [6] E:The path contains invalid characters. Program will not continue
    14.04.2022 15:37:34 [6] I:Received API response as System.Net.HttpWebResponse
    04/14/2022 15:37:34 [6] I:Received a response from the lockbox url.
    04/14/2022 15:37:34 [6] E:The path contains invalid characters. Program will not continue

    My root certificate has already been re-deposited in the WMS, but unfortunately this has not been successful either.
    Unfortunately there is no backup of the old version…

    The MQTT.conf has not been modified.
    Here is also the Lockbox_url with https://localhost:9443/lockbox/ which can also be resolved.
    However, with an incorrect certificate.

    Can you help me here?
    Which certificate or Cert Password is requested by LockBoxKey, and where can I store or enter it?

    LG
    Black_Box

    • This topic was modified 2 months, 2 weeks ago by Black_Box.
    #107613
    charteredpotato
    Participant
    • Total Post: 1
    • Newbie

    Did you ever end up finding a solution for this issue?

    We followed the same upgrade path and are having the exact same issue.
    We had hoped 3.6.1 would solve it, but it did not help.

    Thanks

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