# "vtkSocketCommunicator::GetVersion() returns different values on the two connecting processes"

**URL:** https://discourse.paraview.org/t/vtksocketcommunicator-getversion-returns-different-values-on-the-two-connecting-processes/3347
**Category:** ParaView Support
**Tags:** vtk
**Created:** [January 16, 2020, 9:21am UTC](https://discourse.paraview.org/t/vtksocketcommunicator-getversion-returns-different-values-on-the-two-connecting-processes/3347 "2020-01-16T09:21:35Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![XavierStuvw](https://discourse.paraview.org/user_avatar/discourse.paraview.org/xavierstuvw/32/2619_2.png) [@XavierStuvw](https://discourse.paraview.org/u/XavierStuvw)
#### Post date: [January 16, 2020, 1:33pm UTC](https://discourse.paraview.org/t/vtksocketcommunicator-getversion-returns-different-values-on-the-two-connecting-processes/3347/4 "2020-01-16T13:33:59Z")

</div>

Thanks for pointing out that the message in itself is an issue. Hopefully it will be fixed soon. Since deciphering that message has no purpose, the [vtkSocketCommunicator errors: "Could not receive tag" and "Endian handshake failed"](https://discourse.paraview.org/t/vtksocketcommunicator-errors-could-not-receive-tag-and-endian-handshake-failed/3350) are then the candidate troublemakers.

---

_[View the full topic](https://discourse.paraview.org/t/vtksocketcommunicator-getversion-returns-different-values-on-the-two-connecting-processes/3347)._