Views:
Behavior:
When using File Cabinet Synchronization across DocuWare different servers, the following error occurs;

“Synchronization job was aborted due to an error. Look into the job summary. 400 Bad request (The content type header is missing. Cannot deserialize the request body.)”
 
Solution:
This error can occur when the DocuWare versions on the synchronized servers are different. By product design, File cabinet synchronization requires that all involved servers use the same version of DocuWare.
Otherwise, conflicts in communication between the servers can occur, resulting in errors.
 
To ensure that File Cabinet synchronization in DocuWare works smoothly, you must ensure that all involved servers use the same version of DocuWare. If you install a new version of DocuWare, make sure all involved servers are updated to the new version before starting File Cabinet Synchronization. If the error has already occurred, you need to investigate the cause by checking the synchronization log. The log typically indicates which server is using the wrong version of DocuWare. Make sure this server is updated to the same version as the other servers. Then, run file cabinet synchronization again to ensure the problem is resolved.

Synchronization between DocuWare Cloud and On-premise systems
If you are using the synchronization between DocuWare Cloud and on-premise, both systems must use the same version.
In some cases, reconfiguring file cabinet synchronization may also be helpful to ensure that all settings are correct. Check the settings on all involved servers and make sure they are correct.
 
KBA is applicable to both Cloud and On-premise Organizations.