LDAPCP Solution deploy error about ldapcp

[Yvand]

It looks like SPClaimProvider object was not deleted, can you check if this command returns it:

Get-SPClaimProvider -Identity "LDAPCP"

If so, you can remove it:

Get-SPClaimProvider -Identity "LDAPCP" | Remove-SPClaimProvider

Please let me knw if it worked, if so I'll add these steps to Fix-setup-issues page

[MontanaMT]

When I run the command it doesn't find any custom claims providers and I am on getting the error on one server.

[Yvand]

How do you reproduce the error, and what is the exact error message?

[MontanaMT]

The error happens when I redeploy the solution using Central admin. One server errors with The definition specifies a claim provider with a name already in use. I can force the solution to deploy but then the claimprovider never shows up.

[Yvand]

Solution deploys globally on all servers, it should not work on some and fail on others.

• How many SharePoint servers do you have?
• On how many servers do you have an error?
• On servers reporting the error:
  • Are those servers running SharePoint service “Microsoft SharePoint Foundation Web Application”?
  • Do they have "LDAPCP" folder created in folder C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\FEATURES ?

[MontanaMT]

I was finally able to get back into the test environment and I still can't get the $trust.claimprovidername to work. I get an error of Claim provider with name LDAPCP does not exist.

I finally got it working by going back to your original code. One of your developers changed the code to change the name on $trust.ClaimProviderName = "LDAPCP" to something he recognized. I got that code to work once but not after that. Is to ok to leave the LDAPCP there?

[Yvand]

On the server that thows this error, can you run this

Get-SPFeature -Identity "LDAPCP"

If it finds the feature, can you run this:

Get-SPFeature -Identity "LDAPCP" | Enable-SPFeature