Is it 10.5.2 or 10.5.1?! whichever, it's causing issues ..

Brendan Broughton
Brendan Broughton Active Partner
Third Anniversary 100 Comments 100 Up Votes 25 Likes
edited April 2020 in Platform

Can you please correct your version numbering, it's a bit confusing... and I think it's causing issues with the client versions that are connecting, and that in turn is causing things in the screens to break.

 

This is on a client's BOARD server. It was installed before the latest 10.5.1 (?) was released...

 

In one spot it's 10.5.1.1.27596, but in the other it's 10.5.1.27596

 

image

Yet when we connect to their server with our client, it tells us we're running 10.5.2.  There' a 10.5.2?!

image

 

But from what I've seen the latest available v10 is a 10.5.1, released here

 

Even if you look at the latest 10.5.1 installers available in the link above, the package inside quite clearly says 10.5.1.2.##

image

 

but if I look at the client I am currently connecting to the above 10.5.1.1.27596/10.5.1.27596 server, it tells me it's running ...10.5.2..which from what I've seen/read hasn't even been released.

 

image

 

Why did I notice this... because a chart that displays and refreshes without issue...like this..

image

 

Now shows NOTHING if you enter the layout and simply click 'OK'..without actually changing ANYTHING at all in the layout!

image

 

I noticed the 10.5.2 version which was surprising, so though perhaps they had upgraded without letting us know, and there was an issue with it... but after digging deeper they hadn't upgraded, as shown by the first image above.

 

And considering these charts were only built/finalised yesterday it seemed  a bit strange to break today!  But they were built in the morning, and in the afternoon we updated our server to 10.5.1.2 (or 10.5.2), which upgraded my client accordingly.

 

So it seems that whatever this 10.5.2 is, well that client will still connect to a 10.5.1 server.. and I'm guessing that is why our charts are all breaking when we try to amend them.

 

Why did we upgrade? Because support said they couldn't replicate a different issue on the latest version..so we upgraded to see if that fixed it...it didn't..and now we have more.

Answers

  • Dear Brendan,

     

    thanks for the detailed description.

    The confusion on the versions that you see is only due a different naming convention between the Client (10.5.2) and the Server (10.5.1.2). But that should not be causing problems. I suggest you to troubleshoot this via the ticket you already opened, and eventually update this post, so that everyone can share the solution of such a case.

     

    Thanks for your collaboration
    Davide

  • Dear Brendan,

     

    as you know, we are still working on this case on the dedicated ticket. However, let me update my reply in order to prevent potential misleading rumors about two statements of yours.


    1) Your guess "So it seems that whatever this 10.5.2 is, well that client will still connect to a 10.5.1 server.. and I'm guessing that is why our charts are all breaking when we try to amend them." is wrong: that does not affect at all the rendering of a chart. The compatibility check between the Win Client and Board Server is done at the time of authentication, and if it goes through, a potential version incompatibility between Client and Server cannot be a reason for the problem you are claiming


    2) In your screenshot, you display the Board Server version 10.5.1.27596 installed, but you show the Board Server setup of 10.5.1.2.28670. The two are not the same Board Server version. Let's see if the problem is there.

     

    Best Regards

    Davide

  • Hi Davide, Thanks for clarifying the first point.

     

    Regarding the second, I'm aware they're not the same server. Our customer has the 27596 version installed. WE have 28670 installed, so when I first connected to 28670 my Winclient updated accordingly and when it did the version says 10.2. The point I was making there is the confusion over the 10.2 showing when there is no V10.2 (the latest being 10.1.28670).