Sharepoint 2010 Backup Folder Configuration

If you are getting an error when backup operation  like  :

Cannot open backup device ‘E:\yedekk\spbr000000000BE.bak’. Operating system error 3(The system cannot find the path specified.).
BACKUP DATABASE is terminating abnormally.

Ensure that the following are given the Full Control file share and NTFS permissions for the backup shared folder:

  • The account used by the SQL Server service account.
  • The Windows SharePoint Services Timer V4 (SPTimerV4) account.
  • The logged on account, if you are using Windows PowerShell to perform the backup or restore.
  • If the backup folder is a network share, ensure that all accounts that are listed above have access to both the share and the folder itself.
  • If you are performing a backup or restore operation between two SharePoint farms, services on both farms must have the permissions described above.

Step by Step Configuration

1) Creating a backup folder where we want to store sharepoint backup files on specified computer in your domain. After that you have to share this path and create a network path .

2) If you create the shared folder on a computer other than the one running SQL Server, ensure that the service account for SQL Server (MSSQLSERVER) is using a domain user account and that it has Full Control permissions on the shared folder.Give Full Control for  SQL Server Service Account .You can find SQL Server Service Account that first connect your SQL Server -> Start -> All Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL server configuration Manager.

3)  Give Full Control to Sharepoint Timer Service Account. for do that connect your Microsoft Sharepoint Server 2010 installed machine and run-> services.msc

4) Give Full Control to The SharePoint Central Administration application pool identity account

5) Lets configure our sharepoint from Central Administration. Connect your CA and -> Backup and Restore ->
Configure Backup Settings and type your network path to “Backup File Location” section .

6) Click Ok than perform a backup .

Some Resources:
Prepare to back up and recover
http://technet.microsoft.com/en-us/library/ff806332.aspx

Advertisements

Sharepoint Calculated Column’s Formula Syntax changes by specific culture.

Symptom :

One of our customer complain that after migrate Sharepoint 2007 farm to Sharepoint 2010 farm and implement turkish language pack , calculated column of formula is not working.And Getting error The Formula contains a syntax error is not supported.

Solution:

Change the culture settings to previous language than see it will work. If you load Turkish Language Pack and define Religional Settings -> Culture as Turkish , Calculated Column Formula syntax has changed to use “;” semi colon instead of “,” colon. Because Decimal seperator is “,” colon  in some cultures like Turkish and this cause a conflict between Calculated Column Formule Syntax  Parameter seperator and Decimal Seperator.

For Example:

SUM(10.10 , 10.20 , 10.30)  it s working en-US as total of 30.60

SUM(10,10 , 10,20 , 10,30)  its working wrong  tr-TR as total of 120.

Here is the right usage:

SUM(10,10 ; 10,20 ; 10,30)

In Migration senarios you have to careful for culture differences between two product.

Happy Migrations..

Unexpected error in “content sources” when try to crawl in SSP

Errors:

Exception Details: System.IndexOutOfRangeException: DisplayInAdminUI

detailed:

Could not find stored procedure ‘dbo.proc_MSS_GetCrawlHistory’.   at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchSSPAdminPageBase.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP._layouts_listcontentsources_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Caused:

SharePoint database is not on the same version as the farm’s configuration database. If you open up SQL Server and looked at the rows on the dbo.Version tables in both the configuration database and the database associated with the failed SSP, and check that they are not in sync; the updates for the farm had been applied to the configuration database but not the SSP databases.

Solution:

  1. On a SharePoint server in your farm (I’d suggest the one hosting the Central Admin site), open a command prompt and navigate to the directory containing the SharePoint Products and Technologies Configuration Wizard (psconfig.exe)
  2. Execute the following command:
    psconfig -cmd upgrade -inplace b2b -wait -force
  3. Review the PSconfig and Update logs to see if any errors were reported.
  4. Check the versioning data in the dbo.Version table in both of the SSP’s databases to confirm that they now matched the config database’s version.
  5. Open the SSP Admin site and tried to administer the farm’s Search configuration

Resources:

http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/69e664d9-c841-4c9e-8468-2e8b605d781a?prof=required

Error occurred in deployment step ‘Activate Features’ Sharepoint 2010

This error cause by Visual Studio’s default deployment step configuration because it use the -local option when deploying…. thats why it dont create timer job to deploy on other server…

You can fix it by creating your own deployment step or use stsadm command and creating a batch file like me.

For more info for creating your own deployment steps:
http://msdn.microsoft.com/en-us/library/ee256698.aspx

You should consider fallowing advices:

1) As farm deployment to multiple servers requires a timer job you will need to pause the deployment steps and wait for the timer job to complete (which will no doubt require a constant poll of the timer job status to check whether it has completed or not)

2) Make sure you account for the timer job completing but the solution failing it’s deployment – replying solely on the timer job status will not be a sure fire way of determining whether the solution has actually deployed succesfully

3) Ensure that the account performing the VS Deloyment has enough rights to create the timer job and deploy cross farm
Resources:
http://www.go4answers.com/Example/error-occurred-deployment-step-32423.aspx

Here is an example deployment cmd

@echo Deploying NSF2010 solution
 
@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN;%PATH%
 
@if "%1"=="" (goto invalidParameters) 
 
stsadm -o deactivatefeature -name NSFBase_NSFBase -url %1 -force
stsadm -o deactivatefeature -name NSFBase_NSFErrorModuleFeature -url %1 -force
 
stsadm -o uninstallfeature -name NSFBase_NSFBase -force
stsadm -o uninstallfeature -name NSFBase_NSFErrorModuleFeature -force
 
stsadm -o retractsolution -name NSFBase.wsp -immediate -url %1
stsadm -o execadmsvcjobs
stsadm -o deletesolution -name NSFBase.wsp -override
 
stsadm -o addsolution -filename NSFBase.wsp
stsadm -o deploysolution -name NSFBase.wsp -immediate -allowgacdeployment -force -url %1
stsadm -o execadmsvcjobs
 
stsadm -o installfeature -name NSFBase_NSFBase -force
stsadm -o installfeature -name NSFBase_NSFErrorModuleFeature -force
 
stsadm -o activatefeature -name NSFBase_NSFBase -url %1
stsadm -o activatefeature -name NSFBase_NSFErrorModuleFeature -url %1
 
@goto endOfBatch
 
:invalidParameters
	@echo Please call with the correct parameters.
	@echo The correct syntax of this command is:
	@echo Deploy [siteurl]	
 
:endOfBatch

Usage:

run cmd  with administrative rights then type

deploy [http://your site url:port]

 

Happy Codding.

HTTP 500 – Internal server error page Sharepoint 2007

You can get more detailed error open debug functionality in web config

  • In the <system.web> tag, locate the <customErrors mode=”On”> tag and change it to <customErrors mode=”Off”> to see the ASP.NET exception when an error occurs instead of being redirected to the error page.
  • In the <SharePoint> tag, locate the <SafeMode MaxControls=”50″ CallStack=”false”/> tag and change it to <SafeMode MaxControls=”50″ CallStack=”true”/>. This causes the ASP.NET error message to display with stack trace information
  • In my case error caused by Language pack . You should check your server version and service packs also .

    See :

    http://blog.bugrapostaci.com/2010/10/21/sharepoint-2007-language-pack-service-pack-order/

    See you now.

    The page took too long to save…

    See my post about:

    Saving Page Content Sharepoint with IE8 cause annoying delay:

    http://blog.bugrapostaci.com/2010/03/03/saving-page-content-sharepoint-with-ie8-cause-annoying-delay/

    See you next article…