Cannot synchronize for replication

[JakubH]

We use Plastic SCM with one central server. Now, I've tried to install a local server on my machine, because I want to replicate one repository and make a private branch for some experiment in it. But when I set a sync replication, I've got following error message:

Error: There has been an unexpected error "Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.: JAKUBH:8087". For more information check the server log.

Which is strange, because I am successfully connected to both servers from my client.
Version of my local server (and my client) is 4.1.10.397 – Tanger. Version of the central server is 4.1.10.366 – Tucuman. Could it be some incompatibility between those two?

 

[manu]

Ummm they should be compatible.

 

Can you try again? If it fails can you please upgrade the server accordingly? 

[JakubH]

I've updated the central server to the same version (4.1.10.397 – Tanger), but the same error appears after refresh.

 

I am connecting to both servers through Profiles in Preferences, while the connection to the central server is set also in a config file (using the Client configuration wizard). I am able to use both (for example to create a repository, change permissions) except replication.

[manu]

That's pretty strange.

 

Can you please restart the servers and try again?

 

Also try the replication using the command line (cm replicate) with the "--stack" parameter and send to me the full error.

 

Which type of connection are you using? The SSL or the regular one?

[JakubH]

Restart didn't help.

 

I use regular non-SSL connection.

 

The replication using the command line works fine.

But that is not the same operation, is it? I wasn't able to try replication from GUI, because even showing changes didn't work:

[manu]

Can you please try to replicate from a branch?

 

Right click -> Replicate -> .....

 

I'll try to reproduce your situation.

[JakubH]

After completing the replication of main branch from command line, the sync GUI has started working. Now I can replicate other branches from GUI easily.

Our main branch is huge, because of a long history. So maybe that was the problem.

[manu]

Ummmmmm, could be, maybe. I'll try to reproduce it!

 

Thanks for the report!

[JakubH]

This is still happening. I run into it again recently. Making first synchronization from command line fixes it. It behaves like this for our biggest repository only. Other repos works from GUI without problems from the first synchronization.

[manu]

Thanks Jakub, we haven't had time to review it. It's indeed still happening but it will hopefully automatically removed since we are currently removing and improving the client-server communication layer.

[manu]

Fixed!!!!!!!!!!!!!!!!!!!!!!!!

 

Integrated in: 5.4.16.747

 

 

 

[bug] Very rarely the Sync View failed with a "Binary Stream '0'" error. If you were unlucky enough to see one of these, don't worry, you are safe now.
It was a very rare bug, hard to reproduce, that almost nobody suffered. It has been fixed thanks to Unai Landa from Digital Legends ;-).
The wild and crazy bug has been around for about 7 years and it was a problem in the network layer. The server zips every response sent back to the client. When the compression didn't succeed (very rare) the client was eating some header bytes incorrectly, expecting compression to happen. Then the error showed up.
Fortunately, it has been caught and jailed.