CRM 2015 - Error after update 0.1

Question Status

Suggested Answer
Nicolas COULIN asked a question on 16 Apr 2015 6:41 AM

Hi,

After update 0.1, organization can not be uptaded.

Exception occured during Microsoft.Crm.Tools.Admin.OrganizationDatabaseHotFixer: Error.ActionFailed Microsoft.Crm.Tools.Admin.InstallDatabaseUpdatesAction
InnerException:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.

Any idea ?

Reply
Nicolas COULIN responded on 21 Apr 2015 9:22 AM

Problem with 

Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 

Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

Reply
Andreas Donaubauer responded on 21 Apr 2015 3:42 PM

I have the same Problem with
Microsoft SQL Server 2014 - 12.0.2480.0 (X64) CU6
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600) (Hypervisor)
Sprache: Deutsch (Deutschland)

Reply
Johnny Rossi responded on 21 Apr 2015 3:58 PM

Latest response on our ticket.

“We have identified the issue. The issue has been fixed for Online deployment and for the on-prem fix has not been released yet. We are currently working on it to get a workaround for you.”

Reply
George Rizk responded on 21 Apr 2015 6:46 PM

This must be specific to certain environments.

Where using Server 2012 R2 with SQL 2014 Standard Edition and had no issues upgrading to 0.1.

Our environment is hosted on a HyperV 2012 R2 Server as well.

Prior to that we where running on Server 2008 / SQL 2008 R2 (CRM 2013)

We did make changes to our database when using CRM 2013 as there was a bug at that time causing the Rollup 1 to fail on the RTM release of CRM 2013.

Not sure if they are related bugs but I did notice in your dump you made reference to table: dbupdateinstallinfo

Here was the original issue we had installating Rollup 1 on CRM 2013 RTM with the solution:

community.dynamics.com/.../117857.aspx

Can't wait to hear Microsoft's explanation for this one.

Reply
Eric W. Cahoon responded on 22 Apr 2015 3:28 PM

Unfortunately, we have the exact same issue.  Maybe the below information will be of use to Microsoft

Here's the version info from our SQL box

Microsoft SQL Server 2014 - 12.0.2000.8 (X64)

Feb 20 2014 20:04:26

Copyright (c) Microsoft Corporation

Developer Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )

Reply
Karuna Karan Durai responded on 23 Apr 2015 1:29 AM

Hi Johnny,

Did you get any workaround solution or fix from Microsoft for this issue. Please keep us posted.

Reply
Andreas Donaubauer responded on 23 Apr 2015 5:54 AM

Error when importing a CRM 2013 organization in the same context:

Error.ActionFailed Microsoft.Crm.Tools.Admin.ProvisionOrganizationLanguagesAction

Ungültiger Spaltenname 'AttributeId'.

Ungültiger Spaltenname 'EntityName'.

Die Sicht oder Funktion 'PrincipalSyncAttributeMap' konnte aufgrund von Bindungsfehlern nicht verwendet werden.

Reply
Suggested Answer
Johnny Rossi responded on 23 Apr 2015 8:39 AM

Here is what we were provided to correct this issue.  Keep in mind that this solution was built specifically for our environment and may not match exactly to what others are experiencing.  So use with caution.

1. Make a backup of the file MetadataDiffs.xml from “C:\Program Files\Microsoft Dynamics CRM\Setup\Serviceability\Latest\Actions_Org\Install”

2. Open the file MetadataDiffs.xml from “C:\Program Files\Microsoft Dynamics CRM\Setup\Serviceability\Latest\Actions_Org\Install”

3. Remove the entry about the index “cndx_BusinessDataLocalizedLabel”. This is found at the very end of the file:

   <index Name="cndx_BusinessDataLocalizedLabel">

     <EntityId>4ba1569e-3c9c-4d9f-99ea-b61fb08d7f97</EntityId>

     <IsClustered>1</IsClustered>

     <IsUnique>1</IsUnique>

     <IndexType>6</IndexType>

    <IsPrimaryKey>0</IsPrimaryKey>

     <attributes>

       <attribute AttributeId="d88e1df3-b5b3-42f3-9ffa-007f22951dd4" IsSystemManaged="1" order="0" />

       <attribute AttributeId="bb23d3c8-8d18-40d3-9519-66101a8cae34" IsSystemManaged="1" order="1" />

       <attribute AttributeId="976e1053-5faa-4c3f-be6e-669acfec9d5a" IsSystemManaged="1" order="2" />

       <attribute AttributeId="e81341c4-4d4a-4977-98eb-6597fcde2cc4" IsSystemManaged="1" order="3" />

     </attributes>

   </index>

4.Close Deployment Manager

5. Start Deployment Manager

6. Start the organization update from Deployment manager.

7. Run the following query on the organization DB to manually recreate the index.

IF EXISTS (SELECT * FROM sys.indexes WHERE name = 'cndx_BusinessDataLocalizedLabel' AND OBJECT_NAME(object_id) = 'BusinessDataLocalizedLabelBase') DROP INDEX [cndx_BusinessDataLocalizedLabel] ON [BusinessDataLocalizedLabelBase];

IF NOT EXISTS (SELECT * FROM sys.indexes WHERE NAME = 'cndx_BusinessDataLocalizedLabel' AND OBJECT_NAME(object_id) = 'BusinessDataLocalizedLabelBase')

BEGIN TRY

 CREATE UNIQUE CLUSTERED INDEX [cndx_BusinessDataLocalizedLabel] ON [BusinessDataLocalizedLabelBase]([ObjectId] ASC, [ObjectIdTypeCode] ASC, [ObjectColumnNumber] ASC, [LanguageId] ASC) WITH (FILLFACTOR = 80, MAXDOP = 4, SORT_IN_TEMPDB = ON, ONLINE = ON)

END TRY

BEGIN CATCH

 CREATE UNIQUE CLUSTERED INDEX [cndx_BusinessDataLocalizedLabel] ON [BusinessDataLocalizedLabelBase]([ObjectId] ASC, [ObjectIdTypeCode] ASC, [ObjectColumnNumber] ASC, [LanguageId] ASC) WITH (FILLFACTOR = 80, MAXDOP = 4, SORT_IN_TEMPDB = ON)

END CATCH

8. Restore the file MetadataDiffs.xml to its original state using the backup taken at step 1.

Reply
PatrickN responded on 23 Apr 2015 10:22 AM

This workaround worked on my system.

CRM and SQL on the same system. Organization was v7.0.0.3543, Base Language 1033 plus 5 Language Packs.

Microsoft SQL Server Management Studio 12.0.2456.0

Microsoft Analysis Services Client Tools 12.0.2456.0

Microsoft Data Access Components (MDAC) 6.3.9600.17415

Microsoft MSXML 3.0 6.0

Microsoft Internet Explorer 9.11.9600.17498

Microsoft .NET Framework 4.0.30319.34209

Operating System 6.3.9600

Reply
Suggested Answer
Andreas Donaubauer responded on 23 Apr 2015 10:26 AM

I found the following solution:

If the error occurred during import appears Organization,

then run the following script on the organization DB to manually recreate the view:

--------------------------------------------------------------------------------------------------

--

-- base view for PrincipalSyncAttributeMap

--

ALTER view [dbo].[PrincipalSyncAttributeMap]

(

   -- logical attributes

   [OrganizationIdName],

   -- physical attributes

   [PrincipalSyncAttributeMapId],

   [PrincipalId],

   [VersionNumber],

   [MappingName],

   [EntityName],

   [AttributeCRMName],

   [AttributeExchangeName],

   [SyncDirection],

   [DefaultSyncDirection],

   [AllowedSyncDirection],

   [IsComputed],

   [ParentPrincipalSyncAttributeMappingId],

   [ComputedProperties],

   [OrganizationId],

   [AttributeCRMDisplayName],

   [AttributeExchangeDisplayName]

) with view_metadata as

select

   -- logical attributes

   [lk_principalsyncattributemap_organizationid].[Name],

   -- physical attribute

   [PrincipalSyncAttributeMapBase].[PrincipalSyncAttributeMapId],

   [PrincipalSyncAttributeMapBase].[PrincipalId],

   [PrincipalSyncAttributeMapBase].[VersionNumber],

   [PrincipalSyncAttributeMapBase].[MappingName],

   [PrincipalSyncAttributeMapBase].[EntityTypeCode],

   [PrincipalSyncAttributeMapBase].[AttributeCRMName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeName],

   [PrincipalSyncAttributeMapBase].[SyncDirection],

   [PrincipalSyncAttributeMapBase].[DefaultSyncDirection],

   [PrincipalSyncAttributeMapBase].[AllowedSyncDirection],

   [PrincipalSyncAttributeMapBase].[IsComputed],

   [PrincipalSyncAttributeMapBase].[ParentPrincipalSyncAttributeMappingId],

   [PrincipalSyncAttributeMapBase].[ComputedProperties],

   [PrincipalSyncAttributeMapBase].[OrganizationId],

   [PrincipalSyncAttributeMapBase].[AttributeCRMDisplayName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeDisplayName]

from [PrincipalSyncAttributeMapBase]

   left join [OrganizationBase] [lk_principalsyncattributemap_organizationid] with(nolock) on ([PrincipalSyncAttributeMapBase].[OrganizationId] = [lk_principalsyncattributemap_organizationid].[OrganizationId])

GO

--------------------------------------------------------------------------------------------------

Wait for the netxt error "Error.ActionFailed Microsoft.Crm.Tools.Admin.ProvisionOrganizationLanguagesAction" and

then run the following script on the organization DB to manually recreate the view:

--------------------------------------------------------------------------------------------------

--

-- base view for PrincipalSyncAttributeMap

--

ALTER view [dbo].[PrincipalSyncAttributeMap]

(

   -- logical attributes

   [OrganizationIdName],

   -- physical attributes

   [PrincipalSyncAttributeMapId],

   [PrincipalId],

   [VersionNumber],

   [MappingName],

   [EntityTypeCode],

   [AttributeCRMName],

   [AttributeExchangeName],

   [SyncDirection],

   [DefaultSyncDirection],

   [AllowedSyncDirection],

   [IsComputed],

   [ParentPrincipalSyncAttributeMappingId],

   [ComputedProperties],

   [OrganizationId],

   [AttributeCRMDisplayName],

   [AttributeExchangeDisplayName]

) with view_metadata as

select

   -- logical attributes

   [lk_principalsyncattributemap_organizationid].[Name],

   -- physical attribute

   [PrincipalSyncAttributeMapBase].[PrincipalSyncAttributeMapId],

   [PrincipalSyncAttributeMapBase].[PrincipalId],

   [PrincipalSyncAttributeMapBase].[VersionNumber],

   [PrincipalSyncAttributeMapBase].[MappingName],

   [PrincipalSyncAttributeMapBase].[EntityTypeCode],

   [PrincipalSyncAttributeMapBase].[AttributeCRMName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeName],

   [PrincipalSyncAttributeMapBase].[SyncDirection],

   [PrincipalSyncAttributeMapBase].[DefaultSyncDirection],

   [PrincipalSyncAttributeMapBase].[AllowedSyncDirection],

   [PrincipalSyncAttributeMapBase].[IsComputed],

   [PrincipalSyncAttributeMapBase].[ParentPrincipalSyncAttributeMappingId],

   [PrincipalSyncAttributeMapBase].[ComputedProperties],

   [PrincipalSyncAttributeMapBase].[OrganizationId],

   [PrincipalSyncAttributeMapBase].[AttributeCRMDisplayName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeDisplayName]

from [PrincipalSyncAttributeMapBase]

   left join [OrganizationBase] [lk_principalsyncattributemap_organizationid] with(nolock) on ([PrincipalSyncAttributeMapBase].[OrganizationId] = [lk_principalsyncattributemap_organizationid].[OrganizationId])

GO

-------------------------------------------------------------------------------------------------------

Reply
Suggested Answer
Aron R responded on 23 Apr 2015 11:39 AM

Johnny, Thanks for your fix. It worked for me.

Reply
Eric W. Cahoon responded on 23 Apr 2015 11:48 AM

Thank you for sharing this information.  After following the steps, I was able to successfully update the database(s).

Reply
Baris Kanlica responded on 24 Apr 2015 3:44 AM

It worked for me.

Thanks Johnny

Reply
mscrmba responded on 24 Apr 2015 3:48 AM

So Nicolas does Johnny's fix work for you?

Reply
domsaunders responded on 24 Apr 2015 3:50 AM

Worked for me as well.. Thanks!

But - the I cannot see the new navigation working, which was one of the main reasons for wanting to upgrade!  Has anyone else got the new navigation working as per: www.preact.co.uk/.../new-navigation-for-microsoft-dynamics-crm-2015 ?

Reply
Suggested Answer
Scott Durow (MVP) responded on 16 Apr 2015 3:00 PM

This appears to be a problem that many people are encountering- you will need to contact Microsoft support who hopefully will have a fix soon.

Reply
Suggested Answer
Johnny Rossi responded on 23 Apr 2015 8:39 AM

Here is what we were provided to correct this issue.  Keep in mind that this solution was built specifically for our environment and may not match exactly to what others are experiencing.  So use with caution.

1. Make a backup of the file MetadataDiffs.xml from “C:\Program Files\Microsoft Dynamics CRM\Setup\Serviceability\Latest\Actions_Org\Install”

2. Open the file MetadataDiffs.xml from “C:\Program Files\Microsoft Dynamics CRM\Setup\Serviceability\Latest\Actions_Org\Install”

3. Remove the entry about the index “cndx_BusinessDataLocalizedLabel”. This is found at the very end of the file:

   <index Name="cndx_BusinessDataLocalizedLabel">

     <EntityId>4ba1569e-3c9c-4d9f-99ea-b61fb08d7f97</EntityId>

     <IsClustered>1</IsClustered>

     <IsUnique>1</IsUnique>

     <IndexType>6</IndexType>

    <IsPrimaryKey>0</IsPrimaryKey>

     <attributes>

       <attribute AttributeId="d88e1df3-b5b3-42f3-9ffa-007f22951dd4" IsSystemManaged="1" order="0" />

       <attribute AttributeId="bb23d3c8-8d18-40d3-9519-66101a8cae34" IsSystemManaged="1" order="1" />

       <attribute AttributeId="976e1053-5faa-4c3f-be6e-669acfec9d5a" IsSystemManaged="1" order="2" />

       <attribute AttributeId="e81341c4-4d4a-4977-98eb-6597fcde2cc4" IsSystemManaged="1" order="3" />

     </attributes>

   </index>

4.Close Deployment Manager

5. Start Deployment Manager

6. Start the organization update from Deployment manager.

7. Run the following query on the organization DB to manually recreate the index.

IF EXISTS (SELECT * FROM sys.indexes WHERE name = 'cndx_BusinessDataLocalizedLabel' AND OBJECT_NAME(object_id) = 'BusinessDataLocalizedLabelBase') DROP INDEX [cndx_BusinessDataLocalizedLabel] ON [BusinessDataLocalizedLabelBase];

IF NOT EXISTS (SELECT * FROM sys.indexes WHERE NAME = 'cndx_BusinessDataLocalizedLabel' AND OBJECT_NAME(object_id) = 'BusinessDataLocalizedLabelBase')

BEGIN TRY

 CREATE UNIQUE CLUSTERED INDEX [cndx_BusinessDataLocalizedLabel] ON [BusinessDataLocalizedLabelBase]([ObjectId] ASC, [ObjectIdTypeCode] ASC, [ObjectColumnNumber] ASC, [LanguageId] ASC) WITH (FILLFACTOR = 80, MAXDOP = 4, SORT_IN_TEMPDB = ON, ONLINE = ON)

END TRY

BEGIN CATCH

 CREATE UNIQUE CLUSTERED INDEX [cndx_BusinessDataLocalizedLabel] ON [BusinessDataLocalizedLabelBase]([ObjectId] ASC, [ObjectIdTypeCode] ASC, [ObjectColumnNumber] ASC, [LanguageId] ASC) WITH (FILLFACTOR = 80, MAXDOP = 4, SORT_IN_TEMPDB = ON)

END CATCH

8. Restore the file MetadataDiffs.xml to its original state using the backup taken at step 1.

Reply
Suggested Answer
Andreas Donaubauer responded on 23 Apr 2015 10:26 AM

I found the following solution:

If the error occurred during import appears Organization,

then run the following script on the organization DB to manually recreate the view:

--------------------------------------------------------------------------------------------------

--

-- base view for PrincipalSyncAttributeMap

--

ALTER view [dbo].[PrincipalSyncAttributeMap]

(

   -- logical attributes

   [OrganizationIdName],

   -- physical attributes

   [PrincipalSyncAttributeMapId],

   [PrincipalId],

   [VersionNumber],

   [MappingName],

   [EntityName],

   [AttributeCRMName],

   [AttributeExchangeName],

   [SyncDirection],

   [DefaultSyncDirection],

   [AllowedSyncDirection],

   [IsComputed],

   [ParentPrincipalSyncAttributeMappingId],

   [ComputedProperties],

   [OrganizationId],

   [AttributeCRMDisplayName],

   [AttributeExchangeDisplayName]

) with view_metadata as

select

   -- logical attributes

   [lk_principalsyncattributemap_organizationid].[Name],

   -- physical attribute

   [PrincipalSyncAttributeMapBase].[PrincipalSyncAttributeMapId],

   [PrincipalSyncAttributeMapBase].[PrincipalId],

   [PrincipalSyncAttributeMapBase].[VersionNumber],

   [PrincipalSyncAttributeMapBase].[MappingName],

   [PrincipalSyncAttributeMapBase].[EntityTypeCode],

   [PrincipalSyncAttributeMapBase].[AttributeCRMName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeName],

   [PrincipalSyncAttributeMapBase].[SyncDirection],

   [PrincipalSyncAttributeMapBase].[DefaultSyncDirection],

   [PrincipalSyncAttributeMapBase].[AllowedSyncDirection],

   [PrincipalSyncAttributeMapBase].[IsComputed],

   [PrincipalSyncAttributeMapBase].[ParentPrincipalSyncAttributeMappingId],

   [PrincipalSyncAttributeMapBase].[ComputedProperties],

   [PrincipalSyncAttributeMapBase].[OrganizationId],

   [PrincipalSyncAttributeMapBase].[AttributeCRMDisplayName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeDisplayName]

from [PrincipalSyncAttributeMapBase]

   left join [OrganizationBase] [lk_principalsyncattributemap_organizationid] with(nolock) on ([PrincipalSyncAttributeMapBase].[OrganizationId] = [lk_principalsyncattributemap_organizationid].[OrganizationId])

GO

--------------------------------------------------------------------------------------------------

Wait for the netxt error "Error.ActionFailed Microsoft.Crm.Tools.Admin.ProvisionOrganizationLanguagesAction" and

then run the following script on the organization DB to manually recreate the view:

--------------------------------------------------------------------------------------------------

--

-- base view for PrincipalSyncAttributeMap

--

ALTER view [dbo].[PrincipalSyncAttributeMap]

(

   -- logical attributes

   [OrganizationIdName],

   -- physical attributes

   [PrincipalSyncAttributeMapId],

   [PrincipalId],

   [VersionNumber],

   [MappingName],

   [EntityTypeCode],

   [AttributeCRMName],

   [AttributeExchangeName],

   [SyncDirection],

   [DefaultSyncDirection],

   [AllowedSyncDirection],

   [IsComputed],

   [ParentPrincipalSyncAttributeMappingId],

   [ComputedProperties],

   [OrganizationId],

   [AttributeCRMDisplayName],

   [AttributeExchangeDisplayName]

) with view_metadata as

select

   -- logical attributes

   [lk_principalsyncattributemap_organizationid].[Name],

   -- physical attribute

   [PrincipalSyncAttributeMapBase].[PrincipalSyncAttributeMapId],

   [PrincipalSyncAttributeMapBase].[PrincipalId],

   [PrincipalSyncAttributeMapBase].[VersionNumber],

   [PrincipalSyncAttributeMapBase].[MappingName],

   [PrincipalSyncAttributeMapBase].[EntityTypeCode],

   [PrincipalSyncAttributeMapBase].[AttributeCRMName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeName],

   [PrincipalSyncAttributeMapBase].[SyncDirection],

   [PrincipalSyncAttributeMapBase].[DefaultSyncDirection],

   [PrincipalSyncAttributeMapBase].[AllowedSyncDirection],

   [PrincipalSyncAttributeMapBase].[IsComputed],

   [PrincipalSyncAttributeMapBase].[ParentPrincipalSyncAttributeMappingId],

   [PrincipalSyncAttributeMapBase].[ComputedProperties],

   [PrincipalSyncAttributeMapBase].[OrganizationId],

   [PrincipalSyncAttributeMapBase].[AttributeCRMDisplayName],

   [PrincipalSyncAttributeMapBase].[AttributeExchangeDisplayName]

from [PrincipalSyncAttributeMapBase]

   left join [OrganizationBase] [lk_principalsyncattributemap_organizationid] with(nolock) on ([PrincipalSyncAttributeMapBase].[OrganizationId] = [lk_principalsyncattributemap_organizationid].[OrganizationId])

GO

-------------------------------------------------------------------------------------------------------

Reply
Suggested Answer
Aron R responded on 23 Apr 2015 11:39 AM

Johnny, Thanks for your fix. It worked for me.

Reply
Suggested Answer
Abdullah Celik responded on 30 Jun 2015 6:44 AM

worked for me too. Thanks.

Reply
Suggested Answer
Oana Nitescu responded on 26 Aug 2015 10:33 AM

Hi Karan,

The fix will be shipped with Update 0.2

Meanwhile you can open a case with us and you will get the COD (Critical On Demand) containing it.

Reply