Start a Conversation

Unsolved

Closed

E

10 Posts

1297

May 5th, 2023 06:00

WDA Update failed

Hello,

We have a few Dell Wyse 5070 with WES and since Update of WMS to version 4.0 every device shows not conform in WMS because of Hash value.

The provided solution is to update the WDA to a newer Version. From version 14.4.1.5 to newest version.

But i can't distribute the new App to the Wyse Devices. (Download_Failed

(Protocol Error : ERROR_SERVER_NOT_REACHABLE))

 

In the dashboard, i can see some errors like: Failed to connect to WMS server https:// LOCAL.NAME:443 . Current WMS server https:// PUBLIC.NAME:443

 

i tried to change the provided name in MongoDB, when i found this thread: "WMS Server Name Change"

 
But the error still appears an the job ends in an timeout.
 
I checked the firewall, but the ports are open. (443, 1883,  etc)
 
Does anyone has a suggestion, what i can do, to solve this?
 
How can i tell the Thin Client, to use the right address? In WDA is the correct address.
 
And how can i get the Update to work properly?
 
(We have only free WMS, no Pro Support)
 
Thanks

3 Apprentice

 • 

712 Posts

May 5th, 2023 06:00

If you have changed the name in the DB, unregister a device, and re register a device.  Does it reflect the new name you wish to have it communicate with?

10 Posts

May 5th, 2023 07:00

in the logs on the Thin Client i can see the new Name but MQTT still fails and Job runs into a timeout.

or where can i verify this?

3 Apprentice

 • 

712 Posts

May 5th, 2023 08:00

From the device, unregister it from WMS, then register it again.  Does it work after that?

10 Posts

May 8th, 2023 00:00

unfortunately not.

The Device still wants to connect with the local name. This says the WMS event log.

In the logs from the Device is the new address registered.

Are there other possibilities, why i cant push the WDA Update to the Devices or is this the
problem? (failed to connect to MQTT)

10 Posts

May 8th, 2023 03:00

i can see the WDA Update message on the Thin Client, but it ends in a failure with Protocol Error - Server not reachable. (shown in WMS)

 

10 Posts

May 8th, 2023 04:00

and i can see in the thin Client log:

Download url https://LOCAL.ADDRESS:443/ccm-web/image/app/tc?fileName=WDA_14.6.8.1_Unified.exe , Downloading WDA_14.6.8.1_Unified.exe failed : Result : FAILURE

 

they still tries to download from the local.name, not the provided name.

This happens after i changed the name in the MongoDB and re-registered the Device.

 

i dont understand where to change the local.name on the Thin Client?? the given name in WDA and provided by the Server are correct.

 

10 Posts

May 8th, 2023 05:00

every entry where the local.name was used in bootstrapProperties collection in the mongo DB.

Where can i change the local Repo address?

 

 

(WMS Local repo:

  1. Update the stratus app URL from the bootstrapProperties collection in the mongodb.

 

{

    "_id" : ObjectId("5a165f75e880aaa3492487e2"),

    "name" : "stratusapp.server.url",

    "value" : "https://:443/ccm-web",

    "isActive" : true,

    "committed" : true

}

)

 

This was the comment in the other thread i found..... but don't know where to change? i also changed the strautsapp.server.url to the new name in bootstrapProperties collection.

 

i did reboot and changed certificate too

 

memcached name was localhost... is this correct?

3 Apprentice

 • 

712 Posts

May 8th, 2023 05:00

What steps did you use to change URL's in DB?

 

WMS Core Services:

  1. Update the bootstrapProperties collection in the mongodb
    • db.bootstrapProperties.update({name:"mqtt.server.url"},{$set: {value:"tcp:// :1883"}})
    • db.bootstrapProperties.update({name:"stratusapp.server.url"},{$set: {value:"https:// :443/ccm-web"}})
    • db.bootstrapProperties.update({name:"stratus.external.mqtt.url"},{$set: {value:"tcp:// :1883"}})
    • db.bootstrapProperties.update({name:"Memcached.Servers"},{$set: {value:" :11211"}})
  2. Save Changes
  3. Reboot server
  4. Update the certificate if still using the self-signed cert generated during install with the old name, otherwise HTTPS CA Validation will fail

3 Apprentice

 • 

712 Posts

May 8th, 2023 08:00

What do your DB records look like?  What did you change it from and to?

I did some testing and mine are below.

Netbios name of server is WMS-Std

DB properties

buffalobound_0-1683559087379.png

buffalobound_1-1683559099213.png

Added Pro Key

Change External URL to external.company.com

 

buffalobound_2-1683559132010.pngbuffalobound_3-1683559143720.png

buffalobound_4-1683559154991.png

 

 

10 Posts

May 8th, 2023 23:00

okay, i changed the stratusapp.server.url and mqtt.server.url to external.company.com too.

i will try to use the NetBios name.

 

unfortunaly we don't have Pro Key, just free Version of WMS.

 

but i will try the suggested changes and give feedback.

10 Posts

May 9th, 2023 00:00

Download_Failed(Protocol Error : ERROR_SERVER_NOT_REACHABLE)

 

the log says:

09.05.2023 09:11:12.233 I 17168 1 Download url https://local.NAME:443/ccm-web/image/app/tc?fileName=WDA_14.6.8.1_Unified.exe , Downloading WDA_14.6.8.1_Unified.exe failed : Result : FAILURE

 

again... i have no idea what else i can do

 

i get the message, but nothing happens.

 

Wyse2-WDA Update.png

3 Apprentice

 • 

712 Posts

May 9th, 2023 05:00

So, is the name in the log, the name you want it to use? local.name? 

Can the device ping the name and does it resolve to the proper IP? 

10 Posts

May 10th, 2023 04:00

No, the name in the log on the Thin Client is the NetBios Name of the Server. How can i change this?

I think this is the reason why i can't let him download the WDA Update over an App Policy.

 

 

3 Apprentice

 • 

712 Posts

May 10th, 2023 07:00

Can you share, or DM me a screenshot of what your DB Table looks like (as I did) for those entries? Are you using autodiscover (DHCP or DNS_SRV) or manual setup for your clients?

10 Posts

May 10th, 2023 23:00

send you a DM with my DB Table.

no autodiscover, just manual setup.

 

No Events found!

Top