Symantec Management Platform (Notification Server)

I was getting Access Denied errors when trying to access the NS Console, "You currently do not have sufficient network access rights to the Notification Server Console". I ran a repair on the NS and the hotfixes with no luck, then repaired every solution with the same result. I tried restoring the database and that didn't work either. I ran NSSetup.aspx setting up a new database, then pointing NS to the old database and that didn't work either.

I called tech support. We worked on this for close to a week. Late one night while working on this from home, I re-read Altiris Knowlegebase article KB3433... again. The Resolution reads:




"Resolution

Open Query Analyzer and select the Altiris database. Type spStringCacheDisable and then run this stored procedure. After it is done, run spStringCacheEnable. After that is done, try to open the Altiris Console. The treeview for the main tabs should take a little while to load since now the string cache needs to reload the information."

Edit: Adjusted link to work properly



While on the phone with tech support, we used this article. However we disabled the string cache then immediately enabled it, like restarting a service. The article is very vague. I tried running SpStringCacheDisable, disabling the string cache. Repairing the Notification Server and applying the SP's and Hotfixes, then running SpStringCacheEnable. Once I did that, http://localhost/Altiris/NS/Install/NSSetup.aspx" everything ran fine.

I just wanted to post this so others won't share my frustration. The link is below.


KB34333

Thanks for this information Dwight, hopefully it will help someone else out.

I had this same error after I was forced to reset my system password, which broke all connections to SQL and threw my Altiris server into a tailspin.  After some tweaking in SQL and on the server itself, I was finally able to get my Altiris Help Desk back up and running as well as the Deployment Console but I was still having the issue outlined above where I couldn't administer the server.  After running the process mentioned, things were back to normal.  THANK YOU!