Riivan Posted August 31, 2020 Report Share Posted August 31, 2020 So I didn't have an issue pushing to our Plastic server until recently, but any time I try to Checkin I get that error. "There has been an unexpected error 'Incorrect hash length: 16.' For more information check the server log." I've scoured the net for any information on it and haven't been able to find anything. Was wondering if other more knowledgeable folks had seen this? I've tried: restarting the server and my machine uninstalling entirely and reinstalling the same version uninstalling and reinstalling the latest version deleting the workspace and pulling it down again Thanks in advance, I don't know enough about all this to be able to parse what is happening to know what steps to try next. Link to comment Share on other sites More sharing options...
calbzam Posted September 1, 2020 Report Share Posted September 1, 2020 Hi, We would need to review the full debug server log to better understand the problem. Are you using a commertial license or free Plastic version? Regards, Carlos. Link to comment Share on other sites More sharing options...
Riivan Posted September 1, 2020 Author Report Share Posted September 1, 2020 Not a problem. We're using a commercial license. Below is the section of our log that I got from the devs containing the error. 2020-08-25 13:34:43,283 Matt GHSWIMS03 ERROR Checkin - Checkin changes cannot be processed. Error:Incorrect hash length: 16 at DatalayerFs.Serializers.RevisionHash.GetHashBytes(String hash) at DatalayerFs.Serializers.RevisionWriter.WriteRevisionData(List`1 revs, IMemoryMappedStorageFile file) at DatalayerFs.Transactions.TransactionWriter.WriteRevisions(List`1 revs, TransactionFiles transactedFiles) at DatalayerFs.BlockDataStore.Codice.CM.Data.IBlockDataStore.SaveRevisions(RepId repId, List`1 revInfos, List`1 referenceRevisions, Int64 replicationLogId, IOperationProgress progress) at ou.a(RepId A_0, List`1 A_1) at gh.a(List`1 A_0) at gh.a(TreeChangedNode A_0, TreeNode A_1) at gh.a(TreeChangedNode A_0, TreeNode A_1, Int64& A_2) 2020-08-25 13:34:43,298 Matt GHSWIMS03 ERROR Operations - OnError catching exception [Incorrect hash length: 16] - Plastic server version: 8.0.16.3899 2020-08-25 13:34:43,298 ERROR PlasticProto.ConnectionFromClient - conn 4776. Error in ProcessMethodCall for method CheckInChangedTree. There has been an unexpected error "Incorrect hash length: 16". For more information check the server log. 2020-08-25 13:38:18,640 Matt GHSWIMS03 ERROR Checkin - Checkin changes cannot be processed. Error:Incorrect hash length: 16 at DatalayerFs.Serializers.RevisionHash.GetHashBytes(String hash) at DatalayerFs.Serializers.RevisionWriter.WriteRevisionData(List`1 revs, IMemoryMappedStorageFile file) at DatalayerFs.Transactions.TransactionWriter.WriteRevisions(List`1 revs, TransactionFiles transactedFiles) at DatalayerFs.BlockDataStore.Codice.CM.Data.IBlockDataStore.SaveRevisions(RepId repId, List`1 revInfos, List`1 referenceRevisions, Int64 replicationLogId, IOperationProgress progress) at ou.a(RepId A_0, List`1 A_1) at gh.a(List`1 A_0) at gh.a(TreeChangedNode A_0, TreeNode A_1) at gh.a(TreeChangedNode A_0, TreeNode A_1, Int64& A_2) Link to comment Share on other sites More sharing options...
calbzam Posted September 1, 2020 Report Share Posted September 1, 2020 Hi, - It may be a problem with the database. Every user from any workspace is experiencing the issue? Do you have backups or the repo replicated somewhere? - Not sure if it would be doable to share the repo database with us to evaluate it? support@codicesoftware.com What is the repo size? Regards, Carlos. Link to comment Share on other sites More sharing options...
Riivan Posted September 1, 2020 Author Report Share Posted September 1, 2020 I'm checking to see if we can share the repo database. But at the moment it is just me having the issue. And I can't checkin changes to any of our projects. Link to comment Share on other sites More sharing options...
calbzam Posted September 1, 2020 Report Share Posted September 1, 2020 Ok, so other users checkin in agains your same repo are not facing the problem? In that case, it seems more like a local problem (in your local installation/configuration) so sharing the database with us may not be useful. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now