Hi,
We have a strange problem enabling the language pack. The language pack is installed on the CRM 365 version 8.2.1. But when enabling we have the following error:
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Expected a component that is marked as Deleted to contain other instances that are not deletedDetail:
<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
<ActivityId>24d0afe9-6331-457a-a07f-97a0166633d3</ActivityId>
<ErrorCode>-2147160060</ErrorCode>
<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />
<Message>Expected a component that is marked as Deleted to contain other instances that are not deleted</Message>
<Timestamp>2017-10-14T08:51:00.3070736Z</Timestamp>
<ExceptionRetriable>false</ExceptionRetriable>
<ExceptionSource i:nil="true" />
<InnerFault i:nil="true" />
<OriginalException i:nil="true" />
<TraceText i:nil="true" />
</OrganizationServiceFault>
The trace log is also does not have enough detail to handle it. Did anyone else encountered this error?
*This post is locked for comments
Ok I did it. For anybody else who is running into this error:
A little description:
go into sql manager and run the following command against your crm-database:
select * from MetadataSchema.Attribute WHERE ComponentState = 3 or ComponentState = 2
If you get any result run:
delete from MetadataSchema.Attribute WHERE ComponentState = 3 or ComponentState = 2
This is the first query you run.
Now you change the "MetadataSchema.Attribute" -Table with the next table:
--> MetadataSchema.AttributeLookupValue then:
--> MetadataSchema.AttributePicklistValue and so on...
Can you explain maybe in step-by-step, how you did this?
Kind regards
Marcel
This may occur for others. You could use this solution:
This solution is not a supported method, so take a full backup of your DBs before committing changes.
This error occurs because exceptions occur in the installation or un-installation process of the language pack. To overcome this issue check all table of metadataschema such as attributes, localizedlabels, ...
If any record with componentstate of 2 or 3 exist, it could cause this error. Delete all records with the condition of componentstate = 2 or 3. Then publish customizations and do an IISRESET. Then you could enable the language pack without error.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156