Fix Setup Issues
Important
LDAPCP Classic is deprecated. Migrating to LDAPCP SE is safe and easy.
This procedure will:
- Clean artifacts that were not correctly removed by SharePoint.
- Fully and properly uninstall the solution.
After it is commpleted, LDAPCP can be safely re-installed as if it was done for the 1st time.
Remove LDAPCP claims provider
Important
Always start a new PowerShell process to ensure using up to date persisted objects and avoid nasty errors.
Execute all the operations below on the server running the central administration.
This commands removes the SPClaimProvider object from the SharePoint farm:
Manually create the missing features
This step will recreate the missing folders of features that were physically removed from the filesystem, but not removed from SharePoint configuration database.
- Identify LDAPCP features still installed
Usually, only LDAPCP farm feature is listed:
- Recreate missing feature folder if needed.
For each feature listed above, check if its “RootDirectory” actually exists in the file system of the current server.
If it does not exist:
- Create the “RootDirectory”. Based on output above, it would be “LDAPCP” in folder “16\Template\Features”
- Use 7-zip to open LDAPCP.wsp and extract the feature.xml of the corresponding feature
- Copy the feature.xml into the “RootDirectory”
- Deactivate and remove the features
- Once all features are uninstalled, delete the “RootDirectory” folder(s) that was created earlier.
Delete the LDAPCP persisted object
LDAPCP stores its configuration is its own persisted object. This stsadm command will delete it if it was not already deleted:
Remove the LDAPCP solution
Close PowerShell.