Thursday, December 18, 2014

SharePoint courses available at Microsoft Virtual Academy

Microsoft Virtual Academy (MVA) is serving in a wonderful way and became an excellent resource for developers, IT Pros and end users.

What is MVA?

“Successful technologists never stop learning and great technology never stops evolving. Microsoft Virtual Academy (MVA) offers online Microsoft training delivered by experts to help technologists continually learn, with hundreds of courses, in 11 different languages. Our mission is to help developers, knowledgeable IT professionals and advanced students learn the latest technology, build their skills, and advance their careers. MVA is free of charge, and the entire service is hosted on Windows Azure.”

MVA is also providing courses on SharePoint which are quite useful for SharePoint professionals.

Course Name URL Published On
Office Guides: Apps for Office and SharePoint  http://www.microsoftvirtualacademy.com/training-courses/office-guides-apps-for-office-and-sharepoint 11/15/2013
Office Guides: SharePoint Online Overview for IT Pros  http://www.microsoftvirtualacademy.com/training-courses/office-guides-sharepoint-online-overview-for-it-pros 11/15/2013
Support Corner: Configure SharePoint Outbound Hybrid Search  http://www.microsoftvirtualacademy.com/training-courses/support-corner-configure-sharepoint-outbound-hybrid-search 9/29/2014
Tuning SQL Server 2012 for SharePoint 2013 Jump Start  http://www.microsoftvirtualacademy.com/training-courses/tuning-sql-server-2012-for-sharepoint-2013-jump-start

3/22/2013

Wednesday, November 26, 2014

“Could not find Stored Procedure Search_GetRepositoryTimePerCrawl” error in SharePoint 2013

In Crawl Log page of Search Service Application, when I clicked on Content Source “Local SharePoint Sites”, I got an error which said “"Could not find Stored Procedure Search_GetRepositoryTimePerCrawl”.

Search Servie Log

This was how Something went wrong screen look like.

SearchError

After searching on different sites, I found a solutions which suggests to check “Search Health Monitoring - Trace Events” Timer Job. When I checked it in Jobs Definitions page, I found it was disabled.

SearchTimerJobDisabled

After enabling and running the timer job, issue was resolved.

TimerJob

This is how Search Crawl Log page looks like

SearchLogs

Reference : http://www.wictorwilen.se/sharepoint-2013-fix-to-the-could-not-find-stored-procedure-search_getrepositorytimepercrawl-error

Stop forcefully SharePoint Search Crawl through PowerShell

Sometime, it happens that we want to stop search crawl but from Central Administration Site, Stop Crawl link doesn’t work. To stop Search Crawl forcefully in SharePoint, we can use this script.

Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "Search Service Application" | ForEach-Object {
    if ($_.CrawlStatus -ne "Idle")
    {
        Write-Host "Stopping : Crawl is currently running for content source $($_.Name)..."
        $_.StopCrawl()
    }
}

Wednesday, November 19, 2014

DateTime picker issue in Nintex Forms

While customizing SharePoint Forms using Nintex Forms, we found that DateTime control in not displaying date in correct manner and form cannot be submitted if DateTime column is a mandatory field. Digits for month were being displayed twice.

1

After doing some search and a after a discussion with my good friend Vahid Taslimi who is Product Manager at Nintex, we started looking into locale and regional settings of SharePoint as it could be potential cause of this issue. We found that their is a conflict between locale settings of OS and locale settings of SharePoint site. When we opened regional settings of the site, we found that locale for the site is English (United States).

2

When we changed Locale from English (United States) to Arabic (U.A.E), issues with DateTime control was not there.

3

Here is the form after this change.

4

Sunday, November 16, 2014

Contents of emails disappeared in Nintex Workflows after SharePoint 2013 SP1 installation

After installing Service Pack 1 for SharePoint 2013, I found an issue with all workflows developed using Nintex Workflows 2013. For some reason, body of email notifications was not visible and it seems contents have been deleted.

image

Nintex Workflows 2013 was installed in June 2014 and that build is not compatible with SP1 for SharePoint 2013. After installing the latest build, issue got resolved and all text for emails are visible as earlier.

image

Monday, May 26, 2014

TF250001: The validation check failed for the following account: NT AUTHORITY\NETWORK SERVICE


While creating new Team Project Collection in Team Foundation Server, if you receive error for SharePoint, make sure that you have added NT AUTHORITY\NETWORK SERVICE as farm administrator in your SharePoint central administration site for Team Foundation Server.

I got this error.

"[Error] TF252031: A SharePoint site could not be created for the team project collection. The following error occurred: TF250001: The validation check failed for the following account: NT AUTHORITY\NETWORK SERVICE. The account must be a member of the Farm Administrators group for the following SharePoint Web application: http://test-tfs-srv01:9000/. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=161206)."







After adding "NT AUTHORITY\NETWORK SERVICE" as farm administrator, team project collection got created successfully.


Wednesday, April 30, 2014

SQL remote blob storage must be installed on each web front end server and on the content database before it may be used.


While enabling Remote Blob Storage on SharePoint servers, we need to run these PowerShell commands to enable RBS.

$cdb = Get-SPContentDatabase WSS_Content_5000  #Set you database name
$rbss = $cdb.RemoteBlobStorageSettings
$rbss.Installed()
$rbss.Enable()
$rbss.SetActiveProviderName($rbss.GetProviderNames()[0])


When you run this line $rbss.Enable(), sometimes we get error and it says, “SQL remote blob storage must be installed on each web front end server and on the content database before it may be used.


To resolve this problem, we need to restart all servers in the Farm. After restarting, it will work like a charm.