You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Followed you instructions to LDAPCP to the latest version from version V3.7.0.0. After the upgrade I'm unable to connect to the administration link with the following error:
I run the steps to uninstall:
DisplayName : LDAPCP
Scope : Farm
Id : b37e0696-f48c-47ab-aa30-834d78033ba8
RootDirectory : C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\15\Template\Features\LDAPCP
DisplayName : LDAPCP.Administration
Scope : Web
Id : f8ebe160-61e5-4e90-8759-98458cbe99a4
RootDirectory : C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\15\Template\Features\LDAPCP.Administration
Those directories and files are there so I proceed to the next step to disable:
Get-SPFeature| ?{$_.DisplayName -like 'LDAPCP*'}| Disable-SPFeature -Confirm:$false
Disable-SPFeature : Could not load file or assembly 'ldapcp, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=b275ba6c8c5c2d2d' or one of its dependencies.
The system cannot find the file specified.
At line:1 char:51
+ Get-SPFeature| ?{$_.DisplayName -like 'LDAPCP*'}| Disable-SPFeature
-Confirm:$fa ...
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...tDisableFeature:
SPCmdletDisableFeature) [Disable-SPFeature], FileNotFoundException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletDisableF
eature
Disable-SPFeature : Required parameter URL was not specified for feature
'f8ebe160-61e5-4e90-8759-98458cbe99a4'. The feature was not deactivated.
At line:1 char:51
+ Get-SPFeature| ?{$_.DisplayName -like 'LDAPCP*'}| Disable-SPFeature
-Confirm:$fa ...
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...tDisableFeature:
SPCmdletDisableFeature) [Disable-SPFeature], ArgumentException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletDisableF
eature
I also tried to just disable using Disable-SPFeature
Disable-SPFeature
cmdlet Disable-SPFeature at command pipeline position 1
Supply values for the following parameters:
Identity: LDAPCP
Confirm
Are you sure you want to perform this action?
Performing the operation "Disable-SPFeature" on target "Farm Scope
|b37e0696-f48c-47ab-aa30-834d78033ba8|15".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):y
Disable-SPFeature : Could not load file or assembly 'ldapcp, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=b275ba6c8c5c2d2d' or one of its dependencies.
The system cannot find the file specified.
At line:1 char:1
+ Disable-SPFeature
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...tDisableFeature:
SPCmdletDisableFeature) [Disable-SPFeature], FileNotFoundException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletDisableF
eature
I'm not sure how to proceed from here. Any assistance would be appreciated.
The text was updated successfully, but these errors were encountered:
Hello, unfortunately this happens sometimes, it's like the persisted object that LDAPCP creates and uses to store its config does not belong to LDAPCP anymore.
In this scenario, the only way is to delete that persisted object, so that LDAPCP creates it again. This is possible using stsadm.exe, located in "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN":
Then, return to LDAPCP administration page and LDAPCP will create a new persisted object (config).
Note that deleting the persisted object will also delete the existing configuration.
Hi Yvan,
Followed you instructions to LDAPCP to the latest version from version V3.7.0.0. After the upgrade I'm unable to connect to the administration link with the following error:
I run the steps to uninstall:
Those directories and files are there so I proceed to the next step to disable:
I also tried to just disable using Disable-SPFeature
I'm not sure how to proceed from here. Any assistance would be appreciated.
The text was updated successfully, but these errors were encountered: