HTML Comments:
<!-- stuff -->
ASP.NET Comments:
<%-- stuff --%>
Thursday, April 25, 2013
Friday, April 19, 2013
Restore a Site to the same Content Database with Gradual Site Delete
Looks like in order to restore a site to the same Content Database, one must perform the following steps after deleting the site:
1. get-spdeletedsite -webapplication http://samplesite.com | Remove-SPDeletedSite
2. Central Administration > 'Monitoring' > 'Review job definitions' > 'Gradual Site Delete' (For the appropriate Web Application) > 'Run Now' button.
References:
http://reality-tech.com/2012/04/04/gradual-site-collection-deletion/
1. get-spdeletedsite -webapplication http://samplesite.com | Remove-SPDeletedSite
2. Central Administration > 'Monitoring' > 'Review job definitions' > 'Gradual Site Delete' (For the appropriate Web Application) > 'Run Now' button.
References:
http://reality-tech.com/2012/04/04/gradual-site-collection-deletion/
Thursday, April 18, 2013
Things to try when Content Deployment hangs
FYI - There's this list in Central Administration:
http://server/Lists/Content%20Deployment%20Jobs/AllItems.aspx
Restart the timer service on each web server:
With PowerShell:
Clear the SharePoint Configuration Cache
Adapted from http://blogs.msdn.com/b/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx
Stop the OWSTIMER service on ALL of the MOSS servers in the farm.
C:\ProgramData\Microsoft\SharePoint\Config\GUID\
NOTE: ONLY THE XML FILES, NOT THE .INI FILE: Delete all the XML file in the directory.
Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
After you see XML files appearing, repeat steps 2, 3 & 4 on each server, waiting for XML files to appear before moving to subsequent servers.
Check the ULS Logs
Check the Windows Error Logs
There might be a SQL Server error, for example.
Delete the Destination Site Collection
Delete the destination Site Collection
get-spdeletedsite -webapplication http://samplesite.com | Remove-SPDeletedSite
Central Administration > 'Monitoring' > 'Review job definitions' > 'Gradual Site Delete' http://samplesite.com > 'Run Now' button.
Re-create the site collection with no template.
Delete the Content Deployment Path
Re-create the Content Deployment Path
Re-create the Content Deployment Job
Run Content Deployment Test
Run Content Deployment.
References:
http://blogs.technet.com/b/stefan_gossner/archive/2010/04/08/content-deployment-the-complete-guide-part-9-timerjobs.aspx
http://blogs.msdn.com/b/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx
http://blogs.technet.com/b/stefan_gossner/archive/2009/01/16/content-deployment-best-practices.aspx?PageIndex=2
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
http://server/Lists/Content%20Deployment%20Jobs/AllItems.aspx
Restart the timer service on each web server:
With PowerShell:
$serviceName = "SPTimerV4"
$serverNames = get-content "ServerNames.txt"
foreach ($serverName in $serverNames)
{
write-host "Restarting SharePoint Timer service on" $serverName
$serviceObj = Get-Service -Name $serviceName -ComputerName $serverName -ErrorAction Stop
Restart-Service -InputObj $serviceObj -erroraction stop
}
Clear the SharePoint Configuration Cache
Adapted from http://blogs.msdn.com/b/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx
Stop the OWSTIMER service on ALL of the MOSS servers in the farm.
C:\ProgramData\Microsoft\SharePoint\Config\GUID\
NOTE: ONLY THE XML FILES, NOT THE .INI FILE: Delete all the XML file in the directory.
Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
After you see XML files appearing, repeat steps 2, 3 & 4 on each server, waiting for XML files to appear before moving to subsequent servers.
Check the ULS Logs
Check the Windows Error Logs
There might be a SQL Server error, for example.
Delete the Destination Site Collection
Delete the destination Site Collection
get-spdeletedsite -webapplication http://samplesite.com | Remove-SPDeletedSite
Central Administration > 'Monitoring' > 'Review job definitions' > 'Gradual Site Delete' http://samplesite.com > 'Run Now' button.
Re-create the site collection with no template.
Delete the Content Deployment Path
Re-create the Content Deployment Path
Re-create the Content Deployment Job
Run Content Deployment Test
Run Content Deployment.
References:
http://blogs.technet.com/b/stefan_gossner/archive/2010/04/08/content-deployment-the-complete-guide-part-9-timerjobs.aspx
http://blogs.msdn.com/b/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx
http://blogs.technet.com/b/stefan_gossner/archive/2009/01/16/content-deployment-best-practices.aspx?PageIndex=2
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
Friday, April 12, 2013
Delete Users from Site Collection
/_layouts/people.aspx?MembershipGroupId=0 > Check the user's checkbox > 'Actions' dropdown > 'Delete Users from Site Collection'
Wednesday, April 10, 2013
MCSM SharePoint 2013 Recommended Reading List - Just the Links
Subscribe to:
Posts (Atom)