cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 14

NPM 10.4.1 missing custom properties after upgrade

Jump to solution

All,

Has anyone experienced this issue?  I have a ticket open on it, and there is senior admin looking into it, but I thought I'd reach out here as well.

I upgraded my environment from 10.3 to 10.4.1 and everything looked ok when I scanned around.  So, then I upgraded NCM from 7.0 to 7.1.1, which is installed on a different server, but I ran the integration upgrade first on NPM first.  After doing this, certain things started failing, and without going through all the troubleshooting details, I realized that all the Custom Properties were missing on the Web UI pages.  The info is still in the database, but there is a SOAP error when pulling the data.  I suspect this has something to do with the new Custom Properties editor functionality (since none of the fields are listed there).  Even the typical custom properties are missing (City, Department, Comments, etc.); which is why none of the "Groups" are now available.

Any ideas how to solve this?  I've re-installed ("repaired) almost all the components, and ran the config wizard a number of times, with no joy.

Dwyane

Labels (1)
0 Kudos
1 Solution
Level 14

All,

I wanted to come back around on this and let you know what was done with the aid of a VERY helpful Support admin (I believe she is more of a senior support admin, and if she reads this, I don't mean to offend with not knowing your real job title.).  The below process took about 2.5 hours to complete as we verified data in several places in between each step.

So, apparently this has something to do with the new Custom Property Editor and the new NCM 7.1.1 (Dev team is working on it).  The good news is, no data is lost in the NPM DB, it's just not viewable until you work some manual magic.  What we did will likely be painful for someone with a lot of custom properties, luckily, I was only using 3 (City, Department, and Comments).

Steps to correct (I HIGHLY recommend a good backup or .csv exported copy BEFORE trying this!!!):

  1. Using the new Custom Property Editor (Web UI), create a new custom property for each property that is missing, naming them whatever makes sense to you.  I created "Town" for City, "Remarks" for Comments, and "Depart" for Department.  (BUG:  do not use a partial of the original name!!  I can't delete "Depart" right now.)
  2. Using the Orion Database Manager (NPM Nodes table), copy the data from the original columns (City, Department, and Comments) to their new columns (Town, Depart, Remarks).
  3. Using the Orion Database Manager, drop (delete) the original columns from the DB.
  4. Using the new Custom Property Editor, recreate the original columns (City, Department, and Comments).
  5. Using the Orion Database Manager, copy the data back to the correct columns.
  6. Using the new Custom Property Editor, delete the temporary columns (Town, Depart, Remarks).  As I mentioned above, do not use partial names for temporary custom properties, you will not be able to delete it.
  7. (May not be necessary, but doesn't hurt)  From the Web UI Admin settings, go into the NCM settings and synchronize the NCM DB with the NPM DB.

This will likely be a very painful process for someone with lots of custom properties, but at least the data is still in the DB, so it could be worse.

D

View solution in original post

0 Kudos
15 Replies
Level 14

All,

I wanted to come back around on this and let you know what was done with the aid of a VERY helpful Support admin (I believe she is more of a senior support admin, and if she reads this, I don't mean to offend with not knowing your real job title.).  The below process took about 2.5 hours to complete as we verified data in several places in between each step.

So, apparently this has something to do with the new Custom Property Editor and the new NCM 7.1.1 (Dev team is working on it).  The good news is, no data is lost in the NPM DB, it's just not viewable until you work some manual magic.  What we did will likely be painful for someone with a lot of custom properties, luckily, I was only using 3 (City, Department, and Comments).

Steps to correct (I HIGHLY recommend a good backup or .csv exported copy BEFORE trying this!!!):

  1. Using the new Custom Property Editor (Web UI), create a new custom property for each property that is missing, naming them whatever makes sense to you.  I created "Town" for City, "Remarks" for Comments, and "Depart" for Department.  (BUG:  do not use a partial of the original name!!  I can't delete "Depart" right now.)
  2. Using the Orion Database Manager (NPM Nodes table), copy the data from the original columns (City, Department, and Comments) to their new columns (Town, Depart, Remarks).
  3. Using the Orion Database Manager, drop (delete) the original columns from the DB.
  4. Using the new Custom Property Editor, recreate the original columns (City, Department, and Comments).
  5. Using the Orion Database Manager, copy the data back to the correct columns.
  6. Using the new Custom Property Editor, delete the temporary columns (Town, Depart, Remarks).  As I mentioned above, do not use partial names for temporary custom properties, you will not be able to delete it.
  7. (May not be necessary, but doesn't hurt)  From the Web UI Admin settings, go into the NCM settings and synchronize the NCM DB with the NPM DB.

This will likely be a very painful process for someone with lots of custom properties, but at least the data is still in the DB, so it could be worse.

D

View solution in original post

0 Kudos

I take it that this problem only occurs if you have both NPM and NCM.  Upgrading NPM to 10.4.1 alone does not cause this problem?

0 Kudos

hdoan,

You are correct.  This issue appears to be something with NPM 10.4.0 (and .1) when installed with (or integrated with) NCM.  There was a big SQL script to correct it, as JakeE indicated, but NPM 10.4.2 has the fix built in.  So anyone that has this issue can just install the latest NPM and it should be corrected.  I think it is mostly something to do with how NCM manages its custom properties, and was over writing the NPM properties...or maybe wasn't sync'ing correctly.  I'm not 100% certain, really...I'm just a lowly, network engineer and I could still ping the server...so, everything else was over my head. 

I'm not so sure if NPM 10.4.2 has the fix built in. I upgraded NPM to 10.4.2 and NCM to 7.1.1 last week and have this issue. Have a support case open right now, waiting for an answer.

0 Kudos

Has anyone had this problem with NPM 10.5 and NCM 7.1.1?

0 Kudos

I've only had 10.5 installed for a couple days, but I don't see this issue with these modules integrated at this time.  I've also been debating whether or not to install NCM 7.2 RC (I could really benefit from the EOL report), but I haven't done so yet.

D

0 Kudos

Thanks, deverts.

I did not know that 10.4.2 was already GA!

0 Kudos

The job title of the person that supported me is actually Applications Engineer; and she deserves the respect of me correcting the above statement.

0 Kudos

I resolved my issue with support (and possibly an engineer, I am unsure of his title) today,  it involved running a few queries, a big SQL script against the database, and then the config wizards on my poller and addtl website boxes.

0 Kudos
Level 9

I upgraded from NPM10.2.2 to 10.4.1 and NCM 7.0.2 to 7.1.1 last week and am suffering the same problem with my custom properties.  The values still seem be there, but are not displayed.

0 Kudos

This is the same thing that happened to me on one of hte two instances I upgraded to 10.4.1 over the weekend.  The data is still all there (thankfully), but I cannot add an new data to the custom fields.  When i attempt to edit an existing node, all of the Custom Property fields are missing there as well.

0 Kudos

I have a small test install, as I'm concerned about data loss in my production environment.

I created a test custom property on and found you can no longer display Custom Properties as a column in the Manage Nodes spreadsheet type view, nor can you sort by them on the left dropdown.

This is a big hit to usefulness.


update: bug or other problem in my install prevented custom properties from being displayed.  I submitted a support request and completed the work with them this morning.

0 Kudos

JakeE, can you provide more detail about why you say you can no longer display CPs as a column in Manage Nodes or sort in the group by? In the below images you can see where I can select a CP, add it to the columns, and group by. Maybe you are talking about something else but please let me know. CP1.PNG

CP2.PNG

CP3.PNG

0 Kudos

For my issue, none of my custom properties were in either of those location like yours Mavturner.   After I worked with support, they now show up like that.  It is not a reduction in functionality, it was a problem on my installation.

0 Kudos

I had the same issue happen in the upgrade to 10.2. We found no fix but to put them back in via a sql update command

0 Kudos