Exported XML fails to import into Personalization citing a duplicate include or exclude

Version 1

    Verified Product Versions

    Environment Manager 8.4Environment Manager 8.3Management Center 8.3Management Center 8.2

    Introduction

    You may find that when importing a previously exported version of your Personalization configuration, the console comes up with an error as below:

     

    UserName [DOMAIN\USERNAME]

    Exception {System.ServiceModel.FaultException}

    Path already on include or exclude list

     

    This error comes up in a dialogue box which also contains a server stack trace.

     

    Detail

    This issue is caused by a duplicate include being specified in the XML file for either a registry or file / folder location. You can find what path is being flagged by:

     

    1. Open Windows Event Viewer (eventvwr.exe)
    2. Expand the path Applications and Services Logs > AppsenseServer > EnvironmentManager > Personalization > Admin
    3. You will find Errors logged to signify the failure to import. Find an entry that looks like this:

     

    (1) [ProfileService.DataAccess.Repository] Command parameters :

    @creationTime:

    @creationUser:DOMAIN\USERNAME

    @include:True

    @modifiedTime:

    @modifiedUser:DOMAIN\USERNAME

    @parentFK:d3bc9294-b502-4f4f-afd3-00ca8b4190b8

    @pathPK:218d1c4d-9728-4554-8e3c-d8ff6651c025

    @type:0

    @path:HKEY_CURRENT_USER\Software\Avaya\Avaya one-X Communicator

    @parentSourceSystemId:0

    The @path variable shown there is the duplicate include that causes the import to fail

     

    To ensure your XML can be imported successfully simply open the .XML file in your favourite text editor and find all occurrences of that path. Duplicates are those occurrences of a path element that show twice under a single <ApplicationGroup>, <Application>, <CustomItem> or <SettingItem> and will cause this behaviour.