KNOWN ISSUE: Collection membership cache change monitoring is not functioning due to inability to run as service account. This is okay during installation

book

Article ID: 156990

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

Warning message reported in SMP logs:
 
"Warnings","9/5/2012 2:54:13 PM","Collection membership cache change monitoring is not functioning due to inability to run as service account.  This is okay during installation.","Altiris.NS.ItemManagement.CollectionMembershipCache.ImpersonateMonitoringThread","AeXSVC.exe","*"
 
This also causes problem with assigning computers to Jobs/Tasks when popup window appears with message:
"After scoping and filtering no computers are left assigned to this task".
 
If an installation is not in progress, this is a condition that must be resolved in order for the product to function correctly.

"Warnings","9/5/2012 2:54:13 PM","Collection membership cache change monitoring is not functioning due to inability to run as service account.  This is okay during installation.","Altiris.NS.ItemManagement.CollectionMembershipCache.ImpersonateMonitoringThread","AeXSVC.exe","*"

Cause

This issue has multiple causes:

  1. Casing of the domain portion of the application identity's credential does not match the case returned by the .NET security API.
  2. Multi-part domain name used to set up the app id credential. For example: typing "domain.local\Altiris" during setup. The .NET security API only returns the NETBIOS domain name as "domain"
  3. When the DNS domain name does not match the NETBIOS domain name. For example: using corpdom\Altiris during setup, when the NETBIOS domain name is just corp. The .NET security API we use returns the NETBIOS domain name, which must match the domain used during setup or impersonation will fail.

 

Resolution

As a workaround, you can run AeXConfig.exe [/svcid user:<user name> password:<password>] and use the NETBIOS domain name in the domain portion of the domain\username pair, and use the same casing for the domain as returned by running "whoami" at a command prompt.

These issues are resolved in ITMS 7.1 SP2 MP1 Rollup v3. See HOWTO81832


Applies To

Symantec Management Platform 7.1 SP2, 7.1 SP2 MP1
ITMS 7.1.2