Hi, the following notices are occasionally observed after execution of a .dmupgrade package. What do they mean and is it safe to ignore them and assume that the upgrade was installed correctly?
10.10.1.47 Notice Property Created with type Service and id 12 uses the same id that is already used by property Created with type Element
10.10.1.47 Notice Property Created by with type Service and id 13 uses the same id that is already used by property Created by with type Element
10.10.1.47 Notice Property Modified with type Service and id 14 uses the same id that is already used by property Modified with type Element
10.10.1.47 Notice Property Modified by with type Service and id 15 uses the same id that is already used by property Modified by with type Element
10.10.2.47 Notice Property Created with type Service and id 12 uses the same id that is already used by property Created with type Element
10.10.2.47 Notice Property Created by with type Service and id 13 uses the same id that is already used by property Created by with type Element
10.10.2.47 Notice Property Modified with type Service and id 14 uses the same id that is already used by property Modified with type Element
10.10.2.47 Notice Property Modified by with type Service and id 15 uses the same id that is already used by property Modified by with type Element
10.10.4.47 Notice Property Created with type Service and id 12 uses the same id that is already used by property Created with type Element
10.10.4.47 Notice Property Created by with type Service and id 13 uses the same id that is already used by property Created by with type Element
10.10.4.47 Notice Property Modified with type Service and id 14 uses the same id that is already used by property Modified with type Element
10.10.4.47 Notice Property Modified by with type Service and id 15 uses the same id that is already used by property Modified by with type Element
Hi,
The upgrade was installed correctly.
During the upgrade there is a check happening for duplicate properties, see this RN here . Duplicate properties will be removed automatically. There is also a check for the ids, as these need to be unique.
In this case, there were 4 duplicates found. If you open "C:\Skyline DataMiner\PropertyConfiguration.xml" you'll see this being present:
<Property id="12" type="Service" name="Created"
<Property id="13" type="Service" name="Created by"
<Property id="14" type="Service" name="Modified"
<Property id="15" type="Service" name="Modified by"
<Property id="12" type="Element" name="Created"
<Property id="13" type="Element" name="Created by"
<Property id="14" type="Element" name="Modified"
<Property id="15" type="Element" name="Modified by"
This is not correct as the id is not unique. This is a problem that was already present before the upgrade, but has been made more visible with the RN that something is wrong.
Manual intervention will be needed to correct this. We have chosen not the automatically adapt this during the update as we are not aware of items that might be relying on the property id (e.g. a QAction, Automation script, Visio drawing,... that could be having this property id fixed).
The advise to fix this faulty situation is to:
-Stop the DMA
-First take a copy of the PropertyConfiguration.xml as backup in case something would go wrong you can quickly use the old file again
-Look in the xml what the maximum id is (note: these are not ordered in the xml)
-Adapt either the Service or Element items that are duplicate and change the id to a new one that is greater than the maximum id so it becomes unique again
-Save the PropertyConfiguration.xml
-Start the DMA and verify that no issues pop up
Regards,
Hello Bing,
From what I know, those notices are occurred if there are 2 properties with the same name and ID but with different property types (e.g. element and service in your case).
You may verify this via "C:\Skyline DataMiner\PropertyConfiguration.xml" and you should see the Ids 12, 13, 14 & 15 are being created with same name and ID but with different property types.
Suspect that the new upgrade action RemoveDuplicateProperties generates these notices.
To resolve this, I believe manual intervention is needed.
It will be best to check with our software colleague on how to resolve the issue.
Currently, if I am not mistaken, there is a release note RN34021,RN37596 to fix the issue.