Error: "The application is not registered with AMS. Please make sure that all services required for this application have been started," or Dr. Watson error message referencing "Msgsys.exe."

Article:TECH99313  |  Created: 2001-01-24  |  Updated: 2008-01-03  |  Article URL http://www.symantec.com/docs/TECH99313
Article Type
Technical Solution


Environment

Issue



You see the error message "The application is not registered with AMS. Please make sure that all services required for this application have been started." when trying to configure AMS from Symantec System Center. You may also see a Dr. Watson error message referencing "Msgsys.exe."

In the Windows Event Viewer, you see one or more of the following error messages:

Source: Intel Alert Handler
Event ID (0) Unable to register with the message system!

Source: Central Quarantine
Event ID (34056) Error initializing Quarantine AMS Events.

Source: Symantec Quarantine
Event ID (9)
Communications error with Immune System [Critical error getting latest blessed sequence number NetworkCriticalError, system error [The operation completed successfully ].
IcePack shutting down


Cause



Here are some case notes from a customer with this issue: #4011102301 _____________________________________________________________________________ NAV CE 7.5 NT4 Terminal Server SP6a User had AMS working before User was running 'Terminal Services' User has been having issues with AMS2 When user brings up 'configure AMS' "The application is not registered with AMS. Please make sure that all services required for this application have been started." - had user stop Terminal Services - had user retry to open 'configure AMS' "The application is not registered with AMS. Please make sure that all services required for this application have been started." - had user reinstall on top of AMS2 - had user restart machine - had user 'configure' AMS2 "The application is not registered with AMS. Please make sure that all services required for this application have been started." - had user make sure 'Alert Originator' is started - had user stop all four Intel Services, and also stop the Norton AntiVirus Server service ; - had user Change the NT Service Logins from the System Account to the local NT Administrator account ; - had user restart those five services, ok - had user check IRPstacksize - it's IRPstacksize is at 11 - had user switch to remote server same error, hourglass after choosing 'Configure' - had user uninstall SSC from Add/Remove - when user was uninstalling, error "Application error has occured 'NscTop.exe" - had user manually uninstall SSC, per KB #2000090514113248 - had user reinstall SSC - had user reinstall Management snap-in - had user install SSC add-ons - had user 'configure AMS' in SSC same error, hourglass after choosing 'Configure' Had user take a look at 'event viewer' - returns following errors - event ID (0) - unable to register with the message system - error initializing (34056) quarantine AMS events Reproducible Steps: ___________________________ - had user reinstall AMS2 - had user restart - had user open AMS2 via SSC, then 'configure' opened - then user opened up 'quarantine console' properties, to 'alerting', to 'configure' - error dr. watson 'msgsys.exe' - went user got back to 'configure' open, - error "The application is not registered with AMS. Please make sure that all services required for this application have been started." ___________________________ - had user enter central quarantine properties - alerting - made sure he's not using a UNC path - had user type in IP address, same error - Intel - user stops service, then starts the services error "too many posts were made to a - semaphor" error "service initialization failed - internal error - messaging system is unavailable" ___________________________________________ NOTES FROM TESTING ***Certainly an issue with having 'Central Quarantine' installed as well - msgsys - is integral to the display of the alert actions - if 'msgsys' is stopped, it is not easily restarted - amsadmin - shows multiple instances in Task Manager, does not close out when you exit - manually shutting down 'msgsys' results in this error: - error '298 - too many posts were made to a semaphore' - check out 'ams2inst.log' *** - check out 'ctinst' in '\NAV\AMS2\WINNT\' - try reinstalling here - possibly 'register' 'msgsys.dll'? 'regsrv32' - check out 'process viewer' and see if 'msgsys.exe' is loaded still when 'end task' - you can stop 'msgsys.exe' by stopping these in order, 'intel pds services' 'nav server' 'quarantine agent' 'central quarantine' if you stop all 'Intel PDS', and 'Central Quarantine / agent', 'NAV Server' will start it. Also, 'quarantine agent / central quarantine' alone, will start it, if other services are stopped _________________________________________________________ - msgsys.exe 'NT4Srv' 14,336 bytes - version - 6.0.201.0940 E 'installing Quarantine Server later' - msgsys.exe '2KPro' 14,336 bytes - version - 6.0.201.940 _________________________________________________________ Errors when 'msgsys.exe' is not in 'TaskList': Trying to start associated services: Win2000 Source: Intel Alert Handler Event ID (0) Unable to register with the message system! Source: Central Quarantine Event ID (34056) Error initializing Quarantine AMS Events. Source: Symantec Quarantine Event ID (9) Communications error with Immune System [Critical error error getting latest blessed sequence number NetworkCriticalError, system error [The operation completed successfully. ] ]. IcePack shutting down WinNT Source: Service Control Manager Event ID: 7023 The Intel File Transfer service terminated with the following error: Too many posts were made to a semaphore. ///Have we tried - min sys requirements - ie5.01 or above - is nt4 terminal server supported, even if terminal services is not running? - steps - check min sys requirements - when error pops up - check to see if 'msgsys.exe' is loaded - check 'file size' and version' - try 'ctiinst' installer for 'CBA' applications - user uninstalled all ssc snap-ins - left quarantine server - tried to access from Terminal Server - 'msgsys.exe' - Terminal Server is not recognized - as action computer

Solution



Symantec Tech Support has only seen this problem on NT 4 Terminal Server edition (with or without Terminal Services running), running the Quarantine and/or AMS Server and SSC. You can also get a Error 4097 from Dr. Watson (memory access error) when configuring AMS alerts on a terminal server.

You may be able to solve this problem by reinitializing the Msgsys.exe executable. Msgsys.exe displays the alert actions when you click Configure AMS. This can only be done by stopping services in a certain order, and then restarting them.

You can stop Msgsys.exe by stopping the following services in the order given:
  1. Intel Alert Handler
  2. Intel Alert Originator
  3. Intel File Transfer
  4. Intel PDS
  5. Norton AntiVirus Server
  6. Symantec Quarantine Agent
  7. Symantec Central Quarantine
After all these services are stopped, you can reinitialize the Msgsys.exe by starting these services in the order given:
  1. Norton AntiVirus Server
  2. Symantec Quarantine Agent
  3. Symantec Central Quarantine

As a possible workaround, move the Central Quarantine or AMS Server to another computer where SSC is not installed, or manage Quarantine and AMS server from a different (non-Terminal Server) computer.




Supplemental Materials

SourceETrack
Value360838

Legacy ID



2001052408250148


Article URL http://www.symantec.com/docs/TECH99313


Terms of use for this information are found in Legal Notices