Video Screencast Help

NS7 Console loading error

Created: 02 Aug 2013 | 2 comments
Tiboace's picture
Symantec Management Server Error

An error has occurred that prevents the Symantec Management Console displaying correctly.

If this page is shown in place of a page or web part in the Symantec Management Console, navigate back to the page using the menu or tree and continue working. If the problem persists, see your local network administrator.

If this page is shown in place of the Symantec Management Console, one of the following could be the cause:

  • The "Altiris Service" service is not running. Start this service on the server and reload the console.
  • The account used for either the "Altiris Service" or the Notification Server webs is incorrect, disabled or the password for the account has expired. On the Notification Server computer, run "C:\Program Files\Altiris\Notification Server\bin\AeXConfig.exe /svcid user:(user name) password:(password)]", substituting the correct installation path if a non-default location was used, to provide a new account.
  • The name of the Notification Server computer has been renamed. The following steps will need to be taken to correct this:
    • If SQL Server is installed on the same machine as the Notification Server:
    • Open the file [NS INSTALL DIRECTORY]\Notification Server\Config\CoreSettings.config, search for the word 'key=DBServer'. Replace the 'value' attribute of the found XML element from the previous server name to the new server name.
    • If account used for either the "Altiris Service" or the Notification Server webs is a local user (i.e. Not a domain user), you will need to update the account to the new name. You can do so by following the 2nd bullet points on this page.
    • Open Registry Editor, browse to the registry key "HKLM\SOFTWARE\Altiris\express\Notification Server\". Find and replace any value that contains the old server name with the new name.
    • Re-push the agent out to all previously managed machines. (#)
    • Run the Windows schedule named "NS.Package Refresh" to re-validate site/package server packages. To get to the Windows schedules, go to 'Start' > 'Control Panel' > 'Scheduled Tasks'.
    • If you have hierarchy set up, you will need to remove and re-add the renamed server to the hierarchy. To do so, go to the "Hierarchy Management" page under the menu "Settings" > "Notification Server" > "Hierarchy".

In both cases, the Symantec Management Server log and the Windows Event log may contain useful information. The Symantec Management Server log can be accessed on the server by running "Start" menu > "All Programs" > "Altiris" > "Diagnostics" > "Altiris Log Viewer".

(#) If the NS hosted computer has yet been renamed, a better alternative would be to point all NS clients to the new server name first. You can do this by going to the menu "Settings" > "Agents/Plug-ins" > "Targeted Agent Settings". For each policy in the list, select the "Advanced" tab and specifies the new server name under the "Alternative URL for accessing NS" section. By doing this, all the clients will work automatically once the NS server has been renamed.

Operating Systems:

Comments 2 CommentsJump to latest comment

Brandon Morrow's picture

I would check the log viewer when accessing the console. The logs should tell you if its a permission, database, services, or connection issue. Post the errors and warnings if you need some help.

Also is this error happen when you open the console or when you just try to load certain pages/web parts?

ericg2's picture

Have you followed the procedure written in that error message ?  If so please provide how it happened and like Brandon said check your log viewer