You cannot 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 the permission to write to it. Microsoft. Sharepoint. SPE

When using SP1 and Cu of sharepoint2010, the following problems are encountered:

1. You cannot 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 the permission to write to it.
Microsoft. Sharepoint. spexception: the directory does not contain the LDAP: // Cn = Microsoft SharePoint products, Cn = system, Dc = contoso, Dc = COM object.

See http://www.cnblogs.com/kaneboy/archive/2011/07/11/2437080.html

And http://blogs.msdn.com/ B /opal/archive/2010/04/18/track-sharepoint-2010-installations-by-service-connection-point-ad-marker.aspx

2. Another error:

Upgrade timer job is exiting due to exception: system. argumentexception: localstoragepath

Http://blog.bugrapostaci.com/tag/localstoragepath/

Solution:

1. Check the following information in the upgrade log: N
[Owstimer] [spupgradesession] [info] [10/7/2011 10:05:49 am]: searchadmindatabase name = fast_query_ssa_db_3a64d349dc2249679a8be

2. Run get-spenterprisesearchserviceapplication in SP powershell.

3. Find the guid and run

$ SSA = Get-spenterprisesearchserviceapplication-identity 4e6d0c5c-f47b-450e-a637-e8a44aca12ae
$ SSA. Delete ()

4. Run the Configuration Wizard

5. created a new SSA to after Configuration Wizard has run.

 

Every upgrade attemp is one of challage for IT team. So this time we are working on a problem which is occured after Aug 2011 cumulative update.
The symptom is SharePoint Configuration Wizard can not able to complete and finishing with failure.

First of all once we check the pscdiagnostics logs we cocould not able to find something useful:

Configuration of SharePoint products failed. configuration must be saved med in order for this product to operate properly. to diagnose the problem, review the extended error information located at c: \ Program Files \ common files \ microsoft shared \ Web Server Extensions \ 14 \ logs \ releases, fix the problem, and run this Configuration Wizard again

Cool but it say nothing. So we peek that let check "upgrade" logs...
And see some error. localstoragepath. What is actually localstoragepath and why we are getting this error while upgrading. It is definitly something wrong with search dB.

[Owstath] [spupgradesession] [Error] [10:05:49 am]: exception: localstoragepath
[Owstsession] [spupgradesession] [info] [10/7/2011 10:05:49 am]: searchadmindatabase name = fast_query_ssa_db_3a64d349dc2249679a8be...
[Owstimer] [spupgradesession] [Error] [10/7/2011 10:05:49 am]: at Microsoft. Office. server. Search. Administration. searchapi. assertparameter (string parametername, Boolean condition)
At Microsoft. Office. server. Search. Administration. searchapi. updateadmincomponent (string servername, guid serverid, string localstoragepath, Boolean standalone, nullable '1 settingsinregistry)
At Microsoft. Office. server. Search. Upgrade. searchadmindatabasesequence. initializetopologybasedon2007settings ()
At Microsoft. Office. server. Search. Upgrade. searchadmindatabasesequence. postupgrade ()
At Microsoft. Sharepoint. Upgrade. spupgradesession. Upgrade (Object o, Boolean brecurse)

The problem in our scenario is some how psconfig can not update the topology, possible cause for this may be service name changes may be an old Conf. backup restored or even more the server name has changed.

Resolution

1. Checked the upgrade Error Log and notice following information
[Owstsession] [spupgradesession] [info] [10/7/2011 10:05:49 am]: searchadmindatabase name = fast_query_ssa_db_3a64d349dc2249679a8be...

2. Use get-spenterprisesearchserviceapplication cmdlet and list all search service applications. We try to delete the search service application. Unable to delete the service application through GUI hence tried successfully with following powershell command.

$ SSA = Get-spenterprisesearchserviceapplication-identity 4e6d0c5c-f47b-450e-a637-e8a44aca12ae
$ SSA. Delete ()

We had 2 search application more so we deleted all of them.

3. Run the Configuration Wizard

4. created a new SSA to after Configuration Wizard has run.

 

A new improvement in SharePoint 2010 is the support of service connection point (Active Directory marker). This can help it already sionals to track SharePoint 2010 installations in their environment.

To use this new feature, administrator needs to create a container in Active Directory then set the right permission to the container before they implement SharePoint 2010 products in their environment. this can be done through ADSI edit. here're the steps:

1. Start ADSI edit on your domain controller, or use remote administration tool to connect to it from another machine.

2. ExpandSystem.

3. Right click in the white area then chooseNew, object...

4. Create a container.

5. Fill in the container name, by default this shocould beMicrosoft SharePoint Products. You can use other names, but you need to create a group policy for the domain machines to set a string valueContainerdistinguishednameUnder registry key:HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ SharePoint. In this way psconfig can detect the new name and change it accordingly.

6. ClickFinish. The container is created.

 

7. Right click on the container, chooseProperties.

8. ClickSecurity.

9. add the users you want to write to this container, and give them create serviceconnectionpoint objects permission by clicking advanced, then edit the object. when users who cannot write to this container install SharePoint 2010, no new entry will be created. a wise idea wocould be give authenticated users the permission so to track all the objects.

10. install and provision a new SharePoint farm in the environment, and check if the SCP has been created successfully. if everything works, you can find a new guid object under Microsoft SharePoint product container. right click it and select Properties, you can find that the server farm's topology Web Services is recorded here. in this case it ishttps: // sp2010: 32844/topology. SVC

I will post a script for listing all the SharePoint 2010 server names in Script Center later.

UPDATE: The script is here: http://gallery.technet.microsoft.com/ScriptCenter/en-us/af31bded-f33f-4c38-a4e8-eaa2fab1c459