Pmadmin.vbs sets the wrong data type for block list registry settings (268164)



The information in this article applies to:

  • Microsoft Site Server 3.0

This article was previously published under Q268164

SYMPTOMS

Pmadmin.vbs sets the wrong registry value data type for account and IP block list settings. In turn, the following settings under the HKLM/System/Currentcontrolset/Service/LDAPSVC/Parameters registry key have no effect:

IPBlackListThreshold

IPBlackListRefreshPeriod

IPBlackListElapseWindow

AccountBlacklistElapseWindow

AccountBlacklistRefreshPeriod

AccountBlacklistThreshold

CAUSE

Pmadmin.vbs sets the registry entries as a data type string (REG_SZ) instead of DWORD (REG_DWORD).

WORKAROUND

Manually set the registry settings to use the proper data type.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Site Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date      Time                 Size    File name     
   ----------------------------------------------------
   07/07/2000  18:44               228,152  Pmadmin.vbs  

				

STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB268164 kbAudDeveloper