Error message when you try to automatically deploy agents in MOM 2005: "A specified logon session does not exist. It may have already been terminated"

Article ID: 912998 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/ )
Description of the Microsoft Windows registry
Expand all | Collapse all

SYMPTOMS

When you try to automatically deploy agents by using a Microsoft Operations Manager (MOM) 2005 Management Server that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1), you receive the following error message:
- Error Code: -2147023584
Error Description: A specified logon session does not exist. It may have already been terminated.
Additionally, the Task Status view in the MOM Operator console contains Warning event number 9899. The description for this event contains the error message.

Additionally, the following event may be logged in the Application event log:

Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: MOM Server
Event ID: 21038
Date: <Date>
Time: <Time>
User: <USerName>
Computer: <Computer>
Description: The MOM Server was unable to establish a connection to the remote computer fif-27.fif.co.id with specified account : fif\ncc1701z. This will cause failure to configure Microsoft Operations Manager agent. Error Code: 1312 Error Description: A specified logon session does not exist. It may already have been terminated.

Back to the top | Give Feedback

CAUSE

This problem occurs if the following conditions are true:
  • The Network access: Do not allow storage of credentials or .NET Passports for network authentication policy is enabled and applies to the Management Server. (This policy is an Active Directory directory service policy.)
  • You have applied hotfix 895195 to the Management Server. Or, the Management Server is running MOM 2005 SP1.
Back to the top | Give Feedback

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps on the Management Server:
  1. Click Start, click Run, type gpedit.msc, and then click OK.
  2. Under Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then expand Security Options.
  3. In the Policy pane, right-click Network access: Do not allow storage of credentials or .NET Passports for network authentication, click Properties, click to select Disabled, and then click OK.
  4. Click Start, click Run, type regedit, and then click OK.
  5. Locate and then right-click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
  6. Verify that the disabledomaincreds value is set to 0.
  7. Restart the computer.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

The Management Server uses Windows Credential Manager to store the credentials of the account that is specified to perform agent installation. If the Network access: Do not allow storage of credentials or .NET Passports for network authentication policy is enabled and applied to the Management Server, Credential Manager cannot store the agent installation account credentials.
Back to the top | Give Feedback

Properties

Article ID: 912998 - Last Review: October 27, 2006 - Revision: 2.1
APPLIES TO
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbtshoot kberrmsg kbbug kbprb KB912998
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top