Doc Err: P&M Does Not Support Changing a Membership Server from One Root Database to Another... (256286)
The information in this article applies to:
- Microsoft Site Server 3.0
This article was previously published under Q256286 SYMPTOMS
The Site Server documentation states the following:
Personalization and Membership does not support changing a Membership
Server from one root database to another after you have created it, unless
the new database is an exact duplicate of the old one. The root database
stores account information for the elements of each Membership Server
using that Membership Directory, and it stores access control information
for your users. All of this information must be intact in order for
P&M to function properly.
This is incorrect. If the root database is changed to an exact duplicate of the original database, the LDAP instance still does not write to the new database, but in fact, writes to the original database, if the original database is available.
CAUSE
LDAP reads the DSOGrid table entry of the database where it is connecting, and reads and writes to the database specified in the DSOGrid table entry.
RESOLUTION
In the DSOGrid table of the copied database, make sure that the entry for vc_database reflects the new database name. If it does not, LDAP will continue to read and write to and from the database specified by the vc_database entry in the DSOGrid table of the copied database.
| Modification Type: | Major | Last Reviewed: | 3/11/2000 |
|---|
| Keywords: | kbprb KB256286 |
|---|
|