Bogus Info in PMAdmin /authmode Switch Creates Corrupt Instances This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
This article was previously published under Q187958 SYMPTOMS
If you use the "PMAdmin create instance" command to create a membership
instance and pass bogus information in the /authmode command-line
parameter, PMAdmin creates the instance despite the error messages. The
instance, however, is incompletely configured and is missing an LDAP query
string. As such, LDAP is unable to bind, and you receive Windows NT Events
4107 and 4102 when you try to start the LDAP instance.
CAUSE
PMAdmin does not back out of the instance creation if it receives an error
from the /authmode switch. This causes an incomplete instance to be
created.
RESOLUTION
To resolve this problem, apply the latest Site Server 3.0 service pack.
WORKAROUND
Delete the instance and recreate it using the proper /authmode Boolean
value.
STATUS
Microsoft has confirmed this to be a problem in Site Server version 3.0.
This problem was corrected in the latest Microsoft Site Server version 3.0
U.S. Service Pack. For information on obtaining the service pack, query on
the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
