Symantec Management Platform (Notification Server)

Hello,

I'm trying to do an upgrade from Symantec Management Platform 7.1 SP1 to SP2 using KB article TECH177513 "Upgrading to ITMS 7.1 SP2 - Best Practices" but the install failed. After this happened, old version of SMP is unistalled, but the new one is not in place, so I have to restore NS server from backup.
I found this type of events in the Symantec Installation Manager logs:

<event date="Mar 01 14:33:52 +00:00" severity="2" hostName="BRMDM" source="Altiris.NS.Configuration.AltirisTransactionalFile.LogWarning" module="SymantecInstallationManager.exe" process="SymantecInstallationManager" pid="5996" thread="11" tickCount="63072296"><![CDATA[Failed To Save File :C:\ProgramData\Symantec\SMP\Settings\CoreSettings.config will retry!]]></event>

<event date="Mar 01 14:33:52 +00:00" severity="1" hostName="BRMDM" source="Altiris.NS.Configuration.ConfigurationSettings.NotifySettingWatchers" module="SymantecInstallationManager.exe" process="SymantecInstallationManager" pid="5996" thread="11" tickCount="63072296"><![CDATA[Failed to refresh SettingWatcher

It seems, that SIM had a problem create file C:\ProgramData\Symantec\SMP\Settings\CoreSettings.config. User account I used for installation is local administrator and has a full access rights to C:\ProgramData\Symantec\SMP\Settings folder.

Thank for help.

You need to log on to the server as the application identity and run the install or repair as the application identity.  Is this what you did?

Also, if you restored from backup, I am confused why it might matter if SIM had a problem creating CoreSettings.config.  Didn't you restore from backup?

I guess I'm confused whether the problem now is getting the restored NS to work, or the NS works but you now need to proceed with SP2 and last time it failed on CoreSettings.config.  As mentioned, if you're ready to try the install of SP2 again, log on to the server as the application identity and run it through SIM.

Try opening it but remember you need to be running the editor as Administrator to save any changes.

Yes, I used different local admin acount then the application identity. I tested upgrade on my lab before I did upgrade the production server and everything works fine. Any way, I will try to run upgrade as the application identity and will report back.

After the SIM failed to do the upgrade to SP2, the NS does not work. When I restored it from backup, NS server works OK.

Thank you.

I already log on to the NS server as the application identity, run the upgrade in SIM, but it failed again with the same error 

It may be the problem.

Don't know if its UAC problem or something, but sometimes its not enough for the appidentity to be in the local admin group to access folders on our NS. We have to set  the appidentity permissions seperate in the ACL even so its member of local admins. Maybe it's worth a try. You could also try to restore a backup file of coresettings if exists.