Error synchronizing CRM for Outlook client
If you get a generic “A SQL Error has occurred” when synchronizing your CRM for Outlook client, then you should likely run a CRM platform trace to get a better error message in order to aid your troubleshooting. There are plenty of articles describing how to do that (including the hard way, and the easy way), so I won’t go into detail here.
Today I came across an issue while preparing for some user training. I was connecting to a test environment of somewhat dodgy pedigree, so the fact that synchronization didn’t work first time didn’t shock me.
I ran the platform trace while I forced a sync on the workstation, and ultimately came up with this error message:
Crm Exception: Message: The entity with a name = ‘subscriptionmanuallytrackedobject’ was not found in the MetadataCache., ErrorCode: –2147217150
I knew that that table was introduced to the database as part of the massive changes associated with Rollup 7, and I had RU7 on the server and client, so was surprised by the error.
A quick look at the tables in the database revealed that the subscriptionmanuallytrackedobject table did not exist in this organization’s database. I checked other org databases in this deployment, and they did have the table. As mentioned earlier, this demo database has a cloudy past and so my best guess is that the organization came from a pre-RU7 deployment and was imported to my RU7 deployment. During the import, the new database objects were not created.
So the solution was to re-apply RU7 to the server (no un-installation required; just re-run the setup) and this went through and fixed the database up. My synchronization immediately completed the next time I ran it.
Make A Comment: ( 1 so far )
One Response to “Error synchronizing CRM for Outlook client”
CRM Cost Comparison Expert
March 3rd, 2011
Loving the new Outlook Client. Much better and clearly integrated than before. MS finally got it right.