Derived model configuration can’t be created by one provider based on another provider’s configuration that has been derived from a model configuration provided by Microsoft

Symptoms

The problem occurs in the following scenario:1. An ER first provider did the following: 1.1 Downloaded MS model configuration from a repository; 1.2 Created the first provider’s configuration deriving it from the MS one; 1.3 Uploaded the MS and first provider model configurations to a repository. 2. An ER second provider did the following:

2.1 Downloaded the first provider’s model configuration from a repository. The MS model configuration downloaded automatically; 2.2 Tried to create the second provider’s configuration deriving it from the first provider’s one.

Resolution

This package contains the code modifications that allows the creation of a derived model configuration based on a configuration that has been introduced by another provider as a derived version of the MS configuration.

More information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.