Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
    • Feature Suggestions
  • Swag Shop
  • Downloads
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Upgrade notices

Solved895 views22nd January 2024upgrade
1
Bing Herng Chong [SLC] [DevOps Advocate]1.10K 19th January 2024 0 Comments

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

Bing Herng Chong [SLC] [DevOps Advocate] Selected answer as best 22nd January 2024

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
3
Min Thant Aung [SLC] [DevOps Advocate]719 Posted 19th January 2024 0 Comments

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.

Min Thant Aung [SLC] [DevOps Advocate] Answered question 19th January 2024
You are viewing 1 out of 2 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin