# vtkSocketCommunicator errors: "Could not receive tag" and "Endian handshake failed"

**URL:** https://discourse.paraview.org/t/vtksocketcommunicator-errors-could-not-receive-tag-and-endian-handshake-failed/3350
**Category:** ParaView Support
**Tags:** vtk
**Created:** [January 16, 2020, 1:31pm UTC](https://discourse.paraview.org/t/vtksocketcommunicator-errors-could-not-receive-tag-and-endian-handshake-failed/3350 "2020-01-16T13:31:06Z")
**Posts on this page:** 1
**Showing post:** 9

<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: [February 15, 2020, 6:46pm UTC](https://discourse.paraview.org/t/vtksocketcommunicator-errors-could-not-receive-tag-and-endian-handshake-failed/3350/9 "2020-02-15T18:46:53Z")

</div>

And I am ever more confused now.

The errors have been launched by pvserver, and both client and sever are little endian; I cannot say which potential bad build was sending a wrong endianness or reading it wrong, though. I sort of think to have launched a `make clean` after each rebuild attempt as a matter of habit.

I reported my previous investigations in [Reverse client-server connection fails with more than one MPI process](https://discourse.paraview.org/t/reverse-client-server-connection-fails-with-more-than-one-mpi-process/3207). **At the server side** I could have skipped doing the `git submodule update` when I cloned the repository the first or other times. Or not having cleaned the build dir.

However, after the git-update-submodule’s, I had to work around another issue **at the client side** , namely [building version 5.7.0 on cluster (2)](https://discourse.paraview.org/t/building-version-5-7-0-on-cluster-2/3489/4). There I certain had a `make clean` at each attempt. So the alternative anwer could be don’t forget to make clean before rebuilding? Please add that to your answer above if applicable: there’s not much recent around about this endian-handshake glitch, and it can be useful for future readers.

Indeed, either way that issue is solved. Thanks for sparring.

---

_[View the full topic](https://discourse.paraview.org/t/vtksocketcommunicator-errors-could-not-receive-tag-and-endian-handshake-failed/3350)._
