Current FW Model not going into effect

[AnEngelsen]

None of the desktop clients are updating to the latest FileWave "model". For example, the current model is 1424. All clients are reporting that their current model is 1421. 

I have verified that none of the clients are in a “locked” state.

For me, this issue became noticeable immediately after being upgraded to FWServer v14.9.0

 

Edited November 10, 2022 by AnEngelsen
Fix spelling mistake

[sean_a]

on-prem or cloud?

what FW version were you on prior to upgrade?

if on-prem, what troubleshooting steps have you done (i.e., restart server services, reboot server)?

 

[sean_a]

that’s right - you said in slack you were on 14.8.0, so presumably ports are not a variable.

[AnEngelsen]

Good Morning @sean_a,

Our FileWave server is hosted by FileWave. (Cloud hosted)

[Josh Levitsky]

I do wonder about ports because in 14.9.0 we went to NATS from ZMQ for the client -> server and client -> boosters as per https://fwkb.atlassian.net/wiki/spaces/KB/pages/80052238/ZeroMQ+replacement+with+NATS so that makes me think it could be port related perhaps but good there is a support case. 

[AnEngelsen]

@Josh LevitskyIt doesn't appear to be a TCP port issue.

[AnEngelsen]

This issue is resolved in the v14.9.1 build of FileWave Server.

[Pierre-Nicolas]

I'd like to take the opportunity to thank you for participating to the early access program - this was indeed an issue on our side which could not be reproduced in our internal labs but being able to witness it live helped tremendously investigating and finding a fix.

Thanks !