Article ID: 968135 - Last Review: January 20, 2012 - Revision: 1.2

Error message when you try to import a workflow rule in the Turkish version of Microsoft Dynamics CRM 4.0: "System.Data.SqlClient.SqlException: Invalid column name 'isCrmUIWorkflow'"

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

You use a Turkish SQL collation in the Turkish version of Microsoft Dynamics CRM 4.0. When you try to import a workflow rule, you receive an error message that resembles the following:

Crm Exception: Message: Error while importing workflow {466bfd7d-62da-411e-978c-788b132333d6}, ErrorCode: -2147220970, InnerException: System.Data.SqlClient.SqlException: Invalid column name 'isCrmUIWorkflow'.

Back to the top

RESOLUTION

This 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

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (http://support.microsoft.com/kb/824684/LN/ ) Description of the standard terminology that is used to describe Microsoft software updates

For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

887283 (http://support.microsoft.com/kb/887283/ ) Microsoft Business Solutions CRM software hotfix and update package naming standards

Back to the top