This article was originally posted on the FIM Forum by Steven Klem.
A downloadable PDF is available at Technet Gallery:
The presentation is online available at Office Mix: https://mix.office.com/watch/ovmzg51c0fcf
Viewing the object type in the Portal returns an error:
“There’s an error in the <Resource Type Name> display configuration. Please contact your system administrator.”
The Resource Management Portal detected an error using the Resource Control Display Configuration (RCDC). This prevented the portal from displaying the object as expected and the portal switched over to Admin View. The failure is due to a incorrect configuration file. The file does not validate against the configuration file schema. Verify that the configuration file is valid XML and matches the configuration file schema. Either upload a new file or modify the existing file in the Resource Management Portal directory. Afterward, reset IIS.
The Resource Management Portal detected an error using the Resource Control Display Configuration (RCDC). This prevented the portal from displaying the object as expected and the portal switched over to Admin View.
The failure is due to a incorrect configuration file. The file does not validate against the configuration file schema.
Verify that the configuration file is valid XML and matches the configuration file schema. Either upload a new file or modify the existing file in the Resource Management Portal directory. Afterward, reset IIS.
Fixing this problem on a system where it is not practical to re-migrate the configuration to a blank FIMService database, this is when we recommend contacting support.
FIM Support has a product group provided option that is unsupported except through support
The FIM product group is investigating a long-term fix to this problem
Any change to one of these attributes will cause the RCDC to be replaced
Check the policy “Change.xml” file for any Deletes and Adds for default RCDC objects
Text search by Name or GUID (see slide “Default RCDCs”)
<ImportObject> <TargetObjectIdentifier>urn:uuid:cc802776-9127-400d-aee2-1b43d538d01e</TargetObjectIdentifier> <ObjectType>ObjectVisualizationConfiguration</ObjectType> <State>Delete</State> </ImportObject> cc802776-9127-400d-aee2-1b43d538d01e Default GUID for RCDC “Configuration for User Editing”
<ImportObject>
<TargetObjectIdentifier>urn:uuid:cc802776-9127-400d-aee2-1b43d538d01e</TargetObjectIdentifier>
<ObjectType>ObjectVisualizationConfiguration</ObjectType>
<State>Delete</State>
</ImportObject>
cc802776-9127-400d-aee2-1b43d538d01e
Default GUID for RCDC “Configuration for User Editing”
All attributes defined in the join rule must match for the object to be updated rather than replaced. If the objects are not found to match according to the join rule defined, the object in the Target system will be deleted, and the object from the Source system will be added as a Create operation.
Each Create operation creates a new unique GUID for use as the Resource Guid of the newly created object.
<SourceObjectIdentifier>urn:uuid:cc802776-9127-400d-aee2-1b43d538d01e</SourceObjectIdentifier> <ObjectType>ObjectVisualizationConfiguration</ObjectType> <State>Create</State> <Changes> … <ImportChange> <Operation>None</Operation> <AttributeName>DisplayName</AttributeName> <AttributeValue>_sjkConfiguration for User Editing</AttributeValue> <FullyResolved>true</FullyResolved> <Locale>Invariant</Locale> </ImportChange>
<SourceObjectIdentifier>urn:uuid:cc802776-9127-400d-aee2-1b43d538d01e</SourceObjectIdentifier>
<State>Create</State>
<Changes>
…
<ImportChange>
<Operation>None</Operation>
<AttributeName>DisplayName</AttributeName>
<AttributeValue>_sjkConfiguration for User Editing</AttributeValue>
<FullyResolved>true</FullyResolved>
<Locale>Invariant</Locale>
</ImportChange>
Display Name Changed, but it could also have been any of the other three attributes in the Join rule:
Any errors or warnings returned in the PowerShell window are not written anywhere else.
Copy and paste all errors and warnings from the PowerShell window into a text file.
Do this for each .ps1 run so we have a record
The reason we want to keep these files is for troubleshooting in case a problem crops up. These files are very helpful to have when calling support to troubleshoot this type of problem.
Configuration Migration Deployment Guide
Originally published on the FIM forum:
Other related articles: