Search

Migrate or Move Sharepoint Content and Config Db from one server to other (SQL 2005 To SQL 2008)

To migrate or move all SharePoint databases or config db (content and Configuration) from SQL 2005 To SQL 2008 for SharePoint 2007

Steps:

  1. Note down SSP Settings
    1. Central Admin -> Shared Services Administration
    2. Take Print out of the page
    3. Central Admin->SSP->Search Administration->Content Sources
    4. Take Print out of the page
    5. Note Down Content Access account
    6. Central Admin -> SSP->user Profile properties -> view user profile properties
    7. Take print out of the page
    8. Note down all web applications and associated databases
      1. Central Admin -> Operations ->Perform a backup
      2. Take print out of the page
      3. Stop the farm
      4. Take back up of all content databases
      5. Restore content databases to the new server (except WSS_Search)

 

Attach Content Databases to web applications

 Below procedure will be used for Admin Content database as well

Go to STSADM

stsadm –o deletecontentdb –url  http://url –databasename “databasename”  -databaseserver “oldserver”

stsadm –o addcontentdb –url http://url –databasename “databasename” –databaseserver “newserver”

 

Move SSP to the new server

 Take back up of SSP through central admin

  1. Take back up using stsadm  (stsadm -o backup -directory ”\\server\SharedFolderbackup”  -backupmethod full -item “SSPName”)
  2. Take backup of SSP content database from SQL management  Studio
  3. Place SSP backup in the shared folder where both servers has access and SQL service account from new server should also have access to the backup folder
  4. Delete SSP (stsadm -o deletessp -title ”SSPName” -deletedatabases –force)
  5. Detach SSP Content database (stsadm -o -deletecontentdb -url http://url -databasename “databasename”)
  6. Make sure SharePoint Timer Service is running
  7. Make sure Search Services are running on the new server
  8. Restore SSP to new server using central admin
  9. Check User profiles page (you might see an error : An Indexer is not assigned to the SSP, follow steps 11 and 12 else go to 13)
  10. Go to SSP ->Edit properties
  11. Make sure index server is selected
  12. Stop Search Service on the old server
  13. Create Search service from central admin (enter new server details)
  14. Make sure Search Services are running on the new server
  15. If needed run the crawl
  16. Visit the site to make sure everything is normal and running smooth

Move SharePoint Config Database

Make sure you login as Farm Admin and you have access to database as DbCreator on the new sql server.

  1. Take back up of SharePoint Configuration Database
  2. Restore Config DB to the new server
  3. Disconnect Config DB from the old server  (Psconfig.exe –cmd configdb –disconnect)
  4. Connect the Config DB to the new Server (psconfig.exe -cmd configdb -connect -server  ”newsql” –database “SharePoint_Config”  -user  ”domain\user” -password  ”user_password”)

OR

psconfig.exe -cmd configdb -connect -server ”newserver” -database “Sharepoint_Config” -dbuser “domain\user” -dbpassword “password” -user “domain\user” -password  “password”

 Run SharePoint Config Wizard (select do not disconnect). Select the same port as it was earlier for central admin.

-          Re-Start IIS

-          Database should now be linked to the new SQL server.

Check Central Admin -> Operations -> Servers in the Farm

Configuration database server might be pointing to the old server. This is because config db stores information about all servers and re-name server command might not work at this stage

Check my previous blog about fixing this issue

 

In that case please make a change (change the parentID of the new server) in the config database.

 

 

2 comments - What do you think?  Posted by Tosh - October 10, 2011 at 9:45 am

Categories: Administration, MOSS 2007, Search, Sharepoint Installation   Tags: , , , , , , ,

Breadcrumb (PlaceHolderTitleBreadcrumb) problem in OrangeSingleLevel.master Sharepoint 2007

Customizing MOSS 2007 could be difficult sometimes. There are some Out of Box customized Master pages within SharePoint which can be used.

When using OrangeSingleLevel.master, you might encounter some problems

- PlaceHolderTitleBreadcrumb is one of them

Problem:

It only display the breadcrumb if .aspx pages are selected but does not display anything if you select csub sites
Solution:

Use default breadcrumb used by the default.master

 - locate the tag below

 <asp:ContentPlaceHolder id=”PlaceHolderTitleBreadcrumb” runat=”server”>
  <div>
   <asp:SiteMapPath ID=”siteMapPath” Runat=”server” SiteMapProvider=”CurrentNavSiteMapProviderNoEncode” RenderCurrentNodeAsLink=”false” SkipLinkText=”" cssclass=”breadcrumb” CurrentNodeStyle-CssClass=”breadcrumbCurrent” NodeStyle-CssClass=”ms-sitemapdirectional” />
  </div>
 </asp:ContentPlaceHolder>
- Change id=”PlaceHolderTitleBreadcrumb” to id=”xPlaceHolderTitleBreadcrumb” in the above tag

- Paste the tag below to the above tag

<asp:ContentPlaceHolder id=”PlaceHolderTitleBreadcrumb” runat=”server”/>

What we have done above is modified the id=”PlaceHolderTitleBreadcrumb” to id=”xPlaceHolderTitleBreadcrumb” so that OrangeSingleLevel.master does not use
id=”PlaceHolderTitleBreadcrumb” to display breadcrumb and it will display the default breadcrumb what is displayed if using default.master

Now we are using second tag <asp:ContentPlaceHolder id=”PlaceHolderTitleBreadcrumb” runat=”server”/> which displays the breadcrumb defind by id=”PlaceHolderTitleBreadcrumb” in OrangeSingleLevel.master

so at this point we have two breadcrumbs coming up on the page.

Now let’s hide the second one:

Because OrangeSingleLevel.master ContentPlaceHolder id=”PlaceHolderTitleBreadcrumb” contains both breadcrumb and search (which displays on the results pages of the search center), we will hide just the breadcrumb so that it still displays the search box

- Just before </head> tag, insert the text below

<style>
#ctl00_PlaceHolderTitleBreadcrumb_siteMapPath{
display:none
}
</style>

1 comment - What do you think?  Posted by Tosh - September 17, 2010 at 1:40 pm

Categories: Branding, Search, Sharepoint Errors   Tags: , ,

Advanced Search problem using OrangeSingleLevel.master SharePoint 2007

Customizing MOSS 2007 could be difficult sometimes. There are some Out of Box customized Master pages within SharePoint which can be used.

When using OrangeSingleLevel.master, you might encounter some problems

- Search is one of them
Even if you enable Advanced Search, on some pages (specifically pages with .aspx) it comes up with normal search or hides Advanced Search text.

Solution:

- Open OragneSingleLevel.master page in visual studio
- Locate the tag below

<asp:ContentPlaceHolder id=”PlaceHolderSearchArea” runat=”server”>
<SPSWC:SearchBoxEx id=”SearchBox” RegisterStyles=”false” TextBeforeDropDown=”" TextBeforeTextBox=”<%$Resources:cms,masterpages_searchbox_label%>” TextBoxWidth=”100″ UseSiteDefaults=”true” DropDownMode = “HideScopeDD” SuppressWebPartChrome=”true” runat=”server”/>
</asp:ContentPlaceHolder>
<PublishingVariations:VariationsLabelMenu id=”labelmenu1″ runat=”server”/>
<asp:ContentPlaceHolder ID=”PlaceHolderMiniConsole” runat=”server” />
- Replace the above lines with the tag below (this is what is used in default.master)

 <asp:ContentPlaceHolder id=”PlaceHolderSearchArea” runat=”server”>
 <SharePoint:DelegateControl runat=”server” ControlId=”SmallSearchInputBox” />
</asp:ContentPlaceHolder>

- Locate and delete the tag below at the top of the page

<%@ Register Tagprefix=”SPSWC” Namespace=”Microsoft.SharePoint.Portal.WebControls” Assembly=”Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
- Save OrangeSingleLevel.master and upload to master page gallery

Be the first to comment - What do you think?  Posted by Tosh - at 1:20 pm

Categories: Administration, Branding, Search, Sharepoint Errors   Tags: , , ,