Microsoft KB Archive/297869

= SMS administrator issues after you modify the Kerberos MaxTokenSize registry value =

Article ID: 297869

Article Last Modified on 10/19/2004

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Service Pack 2
 * Microsoft Systems Management Server 2.0 Service Pack 3

-



This article was previously published under Q297869



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
After you apply post-Windows 2000 Service Pack 1 (SP1) fixes or Windows 2000 Service Pack 2 (SP2) and modify the Kerberos MaxTokenSize registry value, various Systems Management Server (SMS) administrator issues may occur. The following list provides examples of the types of issues you may experience:  When you create a package from definition, you may receive the following error message:

Description: Wizard internal error: invalid WBEM ExecMethod result. Please exit the Wizard.

HRESULT : 0x800706BF-The remote procedure call failed and did not execute.

 When you try to create a new advertisement, you may receive the following error message:

No properties are available on this object.

 When you enumerate collections, you receive a list of Collection icons, but the collection name may be missing. For example, you may not see the &quot;All Systems&quot; name even though the typical icon is still displayed. When browsing collections within the Advertisement Wizard, you may also receive the following error message:

_com_error exception in MMC Admin UI!





CAUSE
This issue may occur if the value for the MaxTokenSize value for Kerberos is set too high. Typically, this issue occurs when 0xFFFF (hexadecimal) is specified instead of 65535 (decimal).



WORKAROUND
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To work around this issue, set the MaxTokenSize value as a decimal value as directed in the following Microsoft knowledge base article:

263693 Group Policy may not be applied to users belonging to many groups

Additional query words: prodsms

Keywords: kbkerberos kbnetwork kbprb KB297869

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.