SharePoint 2010 to SharePoint 2016, via SharePoint 2013-Workflow Crash

August 27, 2017

Problem:
Migration from SharePoint 2010 to SharePoint 2016, via SharePoint 2013 – Based on Native Approach.
(Assuming same for Migration from SharePoint 2013 to SharePoint 2016)
When workflow is opened in SharePoint Designer, it goes for crash screen as below.

Solution:
Open SP Designer, such that go to: All Files >> Workflows >> target workflow.


You will see following files related to Workflow, Open file with .oxml such that use : Open with: SharePoint Designer (as Text).
Checkout file.

Change assembly version from 14.0.0 to 16.0.0
Or for Migration from SharePoint 2013 to SharePoint 2016, change from 15.0.0 to 16.0.0
Save file, Check-in.
Now open workflow again. the crash screen, will not appear.

Also delete SharePoint Designer cache at following location.

C:\Users\UserName\AppData\Roaming\Microsoft\Web Server Extensions\Cache
C:\Users\your user name\AppData\Local\Microsoft\WebsiteCache

Advertisements

After migration from SharePoint 2010 to SharePoint 2013 , to SharePoint 2016, search does not work.

May 14, 2017

Case:
Windows Server 2016 + SharePoint 2016 +SQL Server 2016
1 App Server + 1 Web front end
Issue:
After migration from SharePoint 2010 to SharePoint 2013 , to SharePoint 2016, search does not work.
Search throws exception as:
System.ServiceModel.FaultException: An error occurred when verifying security for the message. --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request

Advance search throws object null exception as :
AdvancedSearchBox class encountered unexpected error: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Server.Search.Query.ConsumerScopeCache.GetScopes() at Microsoft.Office.Server.Search.Query.ScopeCache.GetSharedScopes() at Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox.GetScopeEnumerator(ScopeInformation& defaultScope) at Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox.CreateScopeRows(Table parentTable) at Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox.CreateScopingSectionChildControls(Table parentTable) at Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox.CreateChildControls().

Solution:
Tried following checklist as:

    verified that the SharePoint Web Services site existed in IIS, and that SecurityTokenServiceApplication existed as a virtual directory.
    Related application pool that are working
    Created new Search Service application and changed the association.
    Done a full crawl
    Did index reset

Run SharePoint configuration wizard again.
Finally, issue was related to time difference b/w application server and Web front end.
They were in different time zone. Fixed time zones, all above exceptions solved.


SharePoint 2010 to SharePoint 2013 Migration – Strange issue – Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetWebPartPageData(

March 26, 2017

Problem Case
SharePoint web application migrated 2010 to 2013, master page was mis-aligned css wise and web parts were not editable. So Microsoft recommends to create a new master page for SharePoint 2013. So created a new master page and pageLayout. While new master page was under revsions based on old master page html content, whole site start giving crash on following pages:
• Site collection site features
• Site features
• Web parts (Web Designer Galleries)
• List templates (Web Designer Galleries)
• Master pages and page layouts (Web Designer Galleries)
• Themes (Web Designer Galleries)
• Solutions (Web Designer Galleries)
Different error stacks in above pages:
Stack Trace:: 1

The file / does not exist.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: The file / does not exist.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
[FileNotFoundException: The file / does not exist.]
Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetWebPartPageData(HttpContext context, String path, Boolean throwIfFileNotFound) +1653
Microsoft.SharePoint.ApplicationRuntime.SPVirtualPathProvider.GetCacheKey(String virtualPath) +112
System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath, Boolean ensureIsUpToDate) +47
System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +91
System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +192
System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) +71
System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) +223
System.Web.UI.Page.ApplyMasterPage() +74
System.Web.UI.Page.PerformPreInit() +208
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1571

Stack Trace:: 2
[FileNotFoundException]: The file / does not exist.
at Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetWebPartPageData(HttpContext context, String path, Boolean throwIfFileNotFound)
at Microsoft.SharePoint.ApplicationRuntime.SPVirtualFile.CalculateFileDependencies(HttpContext context, SPRequestModuleData basicRequestData, ICollection& directDependencies, ICollection& childDependencies)
at Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.EnsureDependencies(HttpContext context, SPRequestModuleData requestData)
at Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.EnsureCacheKeyAndViewStateHash(HttpContext context, SPRequestModuleData requestData)
at Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.GetVirtualPathProviderCacheKey(HttpContext context, SPRequestModuleData requestData)
at Microsoft.SharePoint.ApplicationRuntime.SPVirtualPathProvider.GetCacheKey(String virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
[HttpException]: Exception of type 'System.Web.HttpException' was thrown.
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Server Error in '/' Application.
--------------------------------------------------------------------------------

The file / does not exist.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: The file / does not exist.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:: 3

[FileNotFoundException: The file / does not exist.]
Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetWebPartPageData(HttpContext context, String path, Boolean throwIfFileNotFound) +1653
Microsoft.SharePoint.ApplicationRuntime.SPVirtualPathProvider.GetCacheKey(String virtualPath) +112
System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath, Boolean ensureIsUpToDate) +47
System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +91
System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +192
System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) +71
System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) +223
System.Web.UI.Page.ApplyMasterPage() +74
System.Web.UI.Page.PerformPreInit() +208
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1571

Solution:
Different solutions , that I tried as:
1. De-activate, active publishing features.
2. Run SharePoint Configuration wizard
3. Re-deployed custom features
Solution that clicked as:
Go back to old version of master page (2010 migrated one), everything start working.
So reason is method, Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData.GetWebPartPageData(
When a master file is changed, it is saved in content database internal tables with all elements like web parts. Slowly check which tag of master file in newly created master file is crashing, remove that element of master file…..so problem is master page content, un-expectedly, a lot of site settings stop working.


SharePoint Branding Strategy

January 27, 2017

Topic: SharePoint Branding Strategy
Audience: SharePoint Consultant
SCOPE: Cross Referenced

Click here to download presentation


SharePoint Migrations-SharePoint 2010/13 to 2016

January 12, 2017

SharePoint Migrations-SharePoint 2010/13 to 2016

Cases:

1. SP 2013 to SP 2016

2. SP 2010 to SP 2013 to SP 2016

3. SP 2010/2013/2016 to SP Online

 

Audience : Developer/Architect

Date: 1/11/2017
Click here for presentation download.