search cancel

AlarmNotifier not starting with error "user denied access" after Spectrum upgrade to 10.4.1


Article ID: 202934


Updated On:


CA Spectrum


After the upgrade to Spectrum 10.4.1 on Windows 2016, the AlarmNotifier processes is not starting with error message "user denied access":

The problem is seen even if the following has been checked:

SpectroSERVER is up and running.

The user that is starting the Alarm Notifier is the Spectrum installation user. Before the upgrade all worked fine with the same settings. 

The hostname of the system where the AlarmNotifier is running is correctly added to the $SPECROOT/.hostrc file.



Release : 10.4.1

Component : Spectrum Core / SpectroSERVER / Alarm Notifier


All the files in the Notifier directory had the wrong user rights set. Looks like this was not set the same as it was before during the upgrade process.


Problem due to having the files in the Notifier directory not being owned by the correct Spectrum installation user, which is used to start the Notifier process.
Running "ls -l" command on the Notifier directory should show the files have the wrong user set.

Change that to the correct user and AlarmNotifier starts and works as expected.