Currently salesforce support fixes this object by object if you open a support case. The support team told me that this is due to a bug in the Contacts object which causes contact registration to fail on depending objects (and even contacts object itself). According to salesforce a bugfix will be part of the next release (Edit: which will be on 23rd January 2017).

Currently salesforce support fixes this object by object if you open a support case. The support team told me that this is due to a bug in the Contacts object which causes contact registration to fail on depending objects (and even contacts object itself). According to salesforce a bugfix will be part of the next release (Edit: which will be on 27th January 2017 (Release Notes: January 2017 Release)).

Currently salesforce support fixes this object by object if you open a support case. The support team told me that this is due to a bug in the Contacts object which causes contact registration to fail on depending objects (and even contacts object itself). According to salesforce a bugfix will be part of the next release.

Currently salesforce support fixes this object by object if you open a support case. The support team told me that this is due to a bug in the Contacts object which causes contact registration to fail on depending objects (and even contacts object itself). According to salesforce a bugfix will be part of the next release (Edit: which will be on 23rd January 2017).