Select the product you need help with
Error message when you try to go offline in the Microsoft Dynamics CRM 4.0 client for Outlook with Offline Access: "Failed move data for entity"Article ID: 951179 - View products that this article applies to. SYMPTOMSWhen you try to go offline in the Microsoft Dynamics CRM 4.0 client for Microsoft Office Outlook with Offline Access, you receive the following error message:
Failed move data for entity 'Entity_Name' during action action {Action_Number}, countRows={Row_Number}.
Impossible d'insérer une ligne de clé en double dans l'objet '%1!' avec un index unique '%2!'.
CAUSEThis problem occurs because Microsoft Dynamics CRM 4.0 uses single quotation marks to parse the index name from the SQL Server error message that you receive when you have duplicate objects. However, SQL Server error messages in some languages contain additional single quotation marks. RESOLUTIONThis problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949256
(http://support.microsoft.com/kb/949256/
)
Microsoft Dynamics CRM 4.0 updates and hotfixes
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
938065
For more information about software update terminology, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/938065/
)
Error message when you try to go offline in the Microsoft Dynamics CRM client for Outlook: "Failed move data for entity"
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
887283
(http://support.microsoft.com/kb/887283/
)
Microsoft Business Solutions CRM software hotfix and update package naming standards
Properties |



Back to the top








