When using a class rule to automatically assign SharePoint Target Sites, it is possible to end up with multiple databases targeting the same site URL, and thus the same SharePoint site.  This is perfectly legal as far as our tool is concerned and is sometimes very useful, but it may or may not be what you intended.  In the most extreme case, you could have several entire QuickPlaces (each with multiple lists and sub-rooms) all being merged into a single SharePoint site. 

In particular, the default Class Rule for QuickPlace sites uses Application Name to generate Relative URLs for the corresponding Site Creation plans.  Thus, if two QuickPlaces have the same name (or names that differ only by the case of the characters) this could result in the above condition.  Possible workarounds are: 

• Manually override the Target Site URLs for the conflicting QuickPlaces and all of its descendants.  
• Change the class rule to use something other than Application Name to generate Relative URLs (for example, Replica Id or File Name are more likely to yield unique values)
• Create an alternate Class Rule and carefully apply the alternate one to the conflicting QuickPlaces.