Friday, 2 September 2011

A simple fix

Last week we had an incident raised, the problem was simple. Users where exporting the results of a advanced find query as a pivot tables and it was either failing to load the data on the Excel spreadsheet or it was failing to update. The users received this error:
[Microsoft][ODBC SQL Server Driver][SQL Server] Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.  Rerun the transaction.
After a bit of searching I found this KB article. I read through it, looked at our advanced find query and confirmed that it had similar date filters and I thought: problem solved. A simple change to the registry and Bob's your uncle. Not quite. You see, there is a note to the KB
Note: You will need to install Microsoft Dynamics CRM for Microsoft Office Outlook to export new dynamic Microsoft Office Excel worksheets because CRMTicket based authentication is used instead of integrated authentication.  Worksheets that were exported prior to the introduction of the UseWebQueryForLiveExport registry key will continue to pull data over integrated authentication which requests data directly from the SQL server hosting the Microsoft Dynamics CRM database.  You must re-export the dynamic Microsoft Office Excel worksheets to take advantage of the performance gains.
Say what now? Install Microsoft Dynamics CRM for Microsoft Office Outlook for each user? That's ok, after all we only have several hundred users that might be affected by this issue. Why is this not the first thing that's in the solution to this issue? What the .....?

I know I should have read the note, but a major modification like this cannot be simply added as a little by the way. Sometimes, I wonder...

No comments:

Post a Comment