NetXMS Support Forum

I am trying to upgrade from version 2.0.7 to 2.1. I am on Windows Server 2008 R2 with MSSQL. I have done the following steps:
1. nxdbmgr check (no errors)
2. run installer with /silent (no errors)
3. NetXMS Core starts (no errors)
4. NetXMS Management Console starts (no errors)

I run into an issue where I select to view alarms on a device and the table (in Management Console) is blank. If I look directly into the table, there are alarms that should be shown. The other odd thing is the Templates. I have a "Windows" template that I have added DCI's to and after the upgrade there is another "Windows" template which seems to be the default that would be installed with Core. So I end up with two "Windows" templates.

The following troubleshooting steps were done with the same result as the above:

1. Upgraded to 2.0.8 then to 2.1
2. Detached netxms_db, created a new db, performed upgrade, attached prior netxms_db and ran nxdbmgr.exe upgrade -t. I did not see any errors and it said it completed successfully.
3. Deleted all rows from "alarms" table prior to upgrade

Right now I am cloning my 2.0.7 environment so that I can work on the issue without impacting my production monitoring. I think my next step will be to export the database without collected data, initialize, import the database without collected data, then upgrade.

If there are any suggestions, please let me know. I'll update if I find anything.

Hi

V2.1 introduced alarm categories. Please check the new system right 'View all alarm categories' for your user(s)

regards
Dani

PERFECT!! Thank you! I checked the "View all alarm categories" and can now see the alarms.

Do you have any ideas on the "Windows" template? Or perhaps I'll post a new topic ... ?

If I edit it, after restarting the Core service, the "Windows" template goes back to default.
If I delete it, after restart, it comes back with the default settings.

I can't help with the 2. question. I would suggest to open a seperate topic.

Hi,

default templates re-imported from file system on server startup. You can disable this behavior by setting server configuration parameter ImportConfigurationOnStartup to 0.

Best regards,
Victor

Got it thank you. I'll put this over on my other thread that I started.