Client/server version hash mismatch

ParaView Support
1

Hi,
I use a workstation in my job that was recently upgraded to Debian 12 (bookworm). Paraview got upgraded to version 5.11.0. After the upgrade, I downloaded the Windows binaries on my own machine (same version), but upon connecting I obtain the client/server version hash mismatch. Any ideas what the problem might be?

Edit: Even downloading Linux binaries in WSL2 and running it from there gives the same issue.

2

please share the exact error you are having.

Paraview got upgraded to version 5.11.0

How was this version of ParaView installed ? Using debian package manager ?

3

This is the message I get:

(  26.410s) [pvserver        ]vtkSocketCommunicator.c:486    ERR| vtkSocketCommunicator (0x56394cafc180): Client/server version hash mismatch.
(  26.410s) [pvserver        ]vtkTCPNetworkAccessMana:324    ERR| vtkTCPNetworkAccessManager (0x56394c5c7c20):
**********************************************************************
Connection failed during handshake. vtkSocketCommunicator::GetVersion()
 returns different values on the two connecting processes
 (Current value: 100).
*********************************************************************

How was this version of ParaView installed ? Using debian package manager ?

Yes.

4

What is the output of pvserver --version on debian and paraview --version on your windows ?

5 
 pvserver --version
paraview version 5.11.0

ParaView version on Windows is 5.11.0 as well. Could be a packaging problem?

Edit: If I use the binaries from paraview.org on the workstation the connection opens successfully.

6

It could be that the Debian packages (which I assume you’re using) are using some other VTK. There’s really not an easy way to tell though.

7

Yes, interestingly even the python-vtk repo package does not actually work, giving issues upon import. I will try to bring it up with their maintainer. Thank you!