02/23/2012 22:21:15 8 INF Creating service connection point for this farm …
02/23/2012 22:21:16 8 WRN Failed to add the service connection point for this farm
02/23/2012 22:21:16 8 INF Entering function StringResourceManager.GetResourceString
02/23/2012 22:21:16 8 INF Resource id to be retrieved is ServiceConnectionPointNotCreatedEventLog for language English (United States)
02/23/2012 22:21:16 8 INF Resource retrieved id ServiceConnectionPointNotCreatedEventLog is Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
02/23/2012 22:21:16 8 INF Leaving function StringResourceManager.GetResourceString
02/23/2012 22:21:16 8 WRN Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=yoursubdomain,DC=domain,DC=ch doesn’t exist in the directory.
at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
02/23/2012 22:21:44 8 INF Entering function TaskCommon.TraceToPsconfigLogAndUpgradeManagerLog
02/23/2012 22:21:44 8 INF Not spawing off the upgrade job, but rather running upgrade synchronously by calling SPFarm.Local.Upgrade() for inplace upgrade
02/23/2012 22:21:44 8 INF Leaving function TaskCommon.TraceToPsconfigLogAndUpgradeManagerLog
02/23/2012 22:30:42 8 ERR Task upgrade has failed with an unknown exception
02/23/2012 22:30:42 8 ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors. Review the upgrade log file located in D:\Sharepoint\14.0\LOGS\Upgrade-20120223-221942-92.log. The number of errors and warnings is listed at the end of the upgrade log file.
If you encounter this fault, check in advance your configuration:
If it is empty have a look at your active directory with AdsiEdit.msc.
In fact, there was no SCP (Service Connection Point) on our AD. It has gone forgotten at the first installation. Nevermind, you can create this SCP manually.
CN=Microsoft Sharepoint Products,CN=System,DC=subdomain,DC=yourdomain,DC=ch
It is advantageous to use the standard path so that will certainly not be overlooked if somebody else create a SCP for a new sharepoint farm. If your Active Directory administrator insist to use a custom container you can define it in the registry. For that create a new key called ContainerDistiguishedName in
Well, let’s do it:
- open AdsiEdit.msc
- connect, usually with Default naming context
- navigate to CN=system or what the admin says
- create a new object as container, called Microsoft SharePoint Products
- Delegate the security option of this container. Delegate Authenticated User with write and read permisson. I know, thats a security issue, but makes sharepiont admin’s life much easier for further farm installations.
- Now create a SCP with sharepoint powershell:
$TopURI = get-SPTopologyServiceApplication | select URI
Set-SPFarmConfig -ServiceConnectionPointBindingInformation $TopURI
If you did it correctly, you will see a new entry. If you do it for many farms, you can identify it at the attribute ServiceBindingInformation.