Pages

Wednesday, March 18, 2015

Configure Content deployment in SharePoint for copying one site collection to another site collection

Content deployment in SharePoint

Content deployment in SharePoint for to deploy content from one site collection to another site collection. In most cases it will be good to use content deployment from Staging to production or Production to staging for to apply few changes in the pages and contents.

The below items only can be moved to destination site collection when using content deployment

1. Web pages( like master pages, custom pages, styles etc…)

2. Resources

3. Lists and libraries

And importantly the below items cant be moved when using content deployment

1. Features

2. Programs and assemblies

3. Configuration files/information

I have configured content deployment using the below steps

  •  Create a site collection using empty template in the destination server
  •  Activate content deployment feature at source site collection and then deactivate unsupported feature the source site collection based on the content deployment result
  • Configure and create content deployment path and job
  • Schedule or run the job

1. Site collection creation:

Create a site collection in the destination server using empty template like below screen

clip_image002

2. Deactivate un supported feature in the source site collection:

a. Activate the “content deployment source feature” at site collection level in the source site

clip_image003

b. Then deactivate all unsupported feature using Disable-spfeature power shell command which are listed in “Content Deployment Source Status”

clip_image004

clip_image005

3. Configure and create content deployment path and job

a. Go the destination server and open the central admin site->General application settings->configure content deployment

b. Then select”Accept incoming deployment jobs” in the Accept content deployment job section and select “Do not require encryption” in the connection security section and thenk Click Ok to save the settings.

clip_image006

clip_image007

c. Now go to the Source server, go to central admin-> General application settings->Configure content deployment paths and jobs

clip_image008

d. Select New path and filled up the below required details and save it

1. Source site collection

2. Connect the destination server central admin site using windows integrated authentication.

3. Destination site collection and click ok to Save it.

clip_image009

image

e. Schedule a job for the created path using New Job option and don’t forget to select Entire site collection in the new job creation.

clip_image013

4. Content deployment Job:

You can run the job manually or the job will run based on the scheuled. Of course the job should be success and do workaround to fix the issue if the job got failed.

clip_image016

Also you can get the alert mail about the status of job if you configured it.

clip_image018

5. You can validate once the job got succeeded in the destination site collection.

clip_image020

Monday, March 16, 2015

one or more issues preventing successful content deployment export were detected on this site collection

When I was setup new content deployment path in the SharePoint server 2013 from the staging server(source server), I got “ one or more issues preventing successful content deployment export were detected on this site collection” error message.

clip_image002

Resolution:

I have disabled all features using “Disable-feature” Power Shell command which were listed in the content Deployment source status in the source site collection.

clip_image004

clip_image005

Friday, March 13, 2015

Native Error While Restoring SharePoint Site

When I was restore the SharePoint site backup file from one SharePoint farm environment to another SharePoint farm and got the following error message “Restore-Spsite: <nativehr>0x8007003</nativehr><nativestack></nativestack>”

clip_image002

Cause:

1. It might be SharePoint version not unique between source and destination.

2. Backup file may be corrupted or backup not happened properly

Resolution:

For my case, SharePoint version not unique between source and destination SharePoint Farm, So I have install appropriate SharePoint patches in the destination server to keep the unique versions and was able to restored the site successfully.

The HTTP request was forbidden with client authentication scheme ‘Negotiate’ in SharePoint 2013

When I was try to restore the site collection backup file in the SharePoint server, got the following error message “ Restore-spsite : the HTTP request was forbidden with client authentication scheme ‘Negotiate’ “.

clip_image001

Also noticed below event logs in the SharePoint server

1. An exception occurred when trying to issue security token. The HTTP request was forbidden with client authentication scheme ‘Negotiate’

clip_image003

2. The Execute method of job definition Microsoft.office.server.userprofiles.LMTPRepopulationJob threw an exception.

clip_image005

And got the “An unexpected error has occurred” error message when I browse user profile service application page in central admin

clip_image007

Cause

Based on the SharePoint logs, Event logs and errors messages. It seems there is having some issue in the user profile service in the SharePoint server.

Resolution:

By re-creating user profile service with synchronization resolved the issue and able to restore the site. The steps are below

1. Delete the existing user profile service application and stop the user profile service and UPS synchronization service

2. Then start the user profile service and then re-create new user profile service application

3. Start the user profile synchronization service and do the full AD synchronization.

Wednesday, March 11, 2015

The trust relationship between this workstation and the primary domain failed in SharePoint 2013

When I navigate to configure Managed account under General Security to add SharePoint service account in SharePoint 2013 central admin, got the following error message “The trust relationship between this workstation and the primary domain failed”

clip_image002

Cause:

There is connectivity issue between AD/DNS and SharePoint server

Resolution:

Finally found that someone removed Primary DNS server IP address in the SharePoint server and added the appropriate Primary DNS server and ran the below command re-register the DNS which resolved the domain failed issue.

image

Monday, March 2, 2015

Requested registry access is not allowed in SharePoint 2013

When I try to register SharePoint Service account in SharePoint central admin, got the following error message “Requested registry access is not allowed”.

After Goggled, found that need to provide access to following registry key “HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\Secure\FarmAdmin” for the central admin application pool account from one of the