Action_SMTPMail fails with error: 'Invalid Callee' or 'MS Action in Progress' (NETIQKB73101)

  • 7773101
  • 15-Jul-2011
  • 12-Sep-2013

Environment

NetIQ AppManager 7.0.x
NetIQ AppManager 8.0
NetIQ AppManager Hotfix 72616
NetIQ AppManager Hotfix 72840
NetIQ AppManager Hotfix 73018
NetIQ AppManager Hotfix 73020

Situation

The Action_SMTPMail job fails with an error: 'Invalid Callee'
MS action in progress from Action_SMTPMail KS.
Action in progress from Action_SMTPMail KS.

Resolution

The Hotfixes listed in the Environment and Cause fields of this article include an updated NQWin32ext.dll file in which the threading model was changed to enhance the ability to run multiple jobs simultaneously.  In certain situations, this change can have an adverse effect on the processing of Actions... specifically with the Action_SMTPMail Knowledge Script.

If you are unsure if you have applied any of the Hotfixes listed in the Environment or Cause fields of this KB to the affected AM Agent(s), you can check the ThreadingModel registry key in the following locations (depending on whether the OS type is 32-bit or 64-bit).  If the Reg_SZ for ThreadingModel is "Apartment" then the NQWin32ext.dll has not been updated on this machine, and thus none of these Hotfixes have been applied to the affected server.  If the value of the Reg_SZ is "Free", then one or more of the listed Hotfixes has been applied.

32 Bit:
HKEY_CLASSES_ROOT\CLSID\{28E4608C-91E6-11D3-85F9-0060979C6D5D}\InprocServer32\ThreadingModel  

64 Bit:

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{28E4608C-91E6-11D3-85F9-0060979C6D5D}\InprocServer32\ThreadingModel

If you find that you have applied one of the listed Hotfixes to the affected AM Agent(s), in the Windows Registry please change the ThreadingModel Reg_SZ from "Free" to "Both".

If this change is required by a broad group of machines you can automate this chagne with the NTAdmin_RegistrySet ks. For configuration of this KS please refer to the AppManager for Windows PDF that comes with the Windows OS module or reviewing the help file within the Operator or Control Center Console.

This change will allow actions to continue to function as normal while you update the Action_SMTPMail knowledge scripts to the appropriate version. After verifying that actions are functioning properly please make sure to update the Action_SMTPMail ks to the latest version.

To permanently update the Action_SMTPMail knowledge script, you may perform the following process:

Install the latest QDB hotfix, AM704_Hotfix7011759 or later, Update the AppManager for Windows OS Module to 7.6.276.0 on the AppManager Repository (QDB) server and propagate the Action_SMTPMail Knowledge Script KS (or manually update if you have renamed copies). The Action_SMTPMail Scripts, may contain different settings based on copies, policies or ad-hoc jobs. Please record the settings prior to propagating the script and properties.

If after propagation of the Action_SMTPMail Knowledge Script, you receive an error stating 'Action in Progress' or 'MS Action in Progress' in the event detail message action tab (which may happen if you have an older Summit Script version of the Action_SMTPMail KS) please contact NetIQ Technical Support and reference this Knowledge Base article.

Cause

The above error message may occur in the following situations:


Scenario 1.  Installating one or more of the following hotfixes on the Management Server where SMTP Mail actions are configured to run (MS based actions)

  1. AppManager for Windows Agent Hotfix 72616
  2. Operator Console Hotfix 72840
  3. Management Server Hotfix 73018
  4. Control Center Hotfix 73020

Scenario 2.  Installing one or more of the following hotfixes on the Agent machines where SMTP Mail actions are configured to run (MC based actions)

  1. AppManager for Windows Agent Hotfix 72616
  2. Operator Console Hotfix 72840
  3. Management Server Hotfix 73018
  4. Control Center Hotfix 73020

Additional Information

Formerly known as NETIQKB73101

 


Feedback service temporarily unavailable. For content questions or problems, please contact Support.