Migrate browser based InfoPath Forms with code behind from MOSS 2007 to SharePoint 2013

What?

How to successfully migrate browser based InfoPath Forms with code behind from MOSS 2007 to SharePoint 2013?

In this post I will try to explain some of the obstacles that you might be hit with and the ways to get around them.

Please use this is a general guide to understand the overall migration process.

InfoPath assembly Microsoft.Office.InfoPath.Server.dll missing in SharePoint 2013?

What?

I am working on migrating an InfoPath Form Solution with code-behind from MOSS 2007 to SharePoint 2013.

After the old solution was upgraded to Visual Studio 2012 on a SharePoint 2013 server, Visual Studio complained that the assembly Microsoft.Office.InfoPath.Server.dll could not be found.

Where?

Not in GAC
Not in 15\Bin
Not in 15\ISAPI

It is found in C:\Program Files\Microsoft Office Servers\15.0\Bin

Nintex Workflow 2010: Integer vs Number

What?

A workflow that was built using Nintex Workflow 2010 in SharePoint Server 2010 was working fine for a couple of months and it suddenly started to throw workflow errors.

The workflow was erroring because of a "for each" action that iterates through a collection of integers.

SharePoint 2010 - Internal server error exception: System.ServiceModel.FaultException Microsoft.Office.Server.Search.Query.KeywordQueryInternal.Execute()

What?

You might receive an internal server error exception when you use Search Core / Custom Search Results Web Part in SharePoint 2010 with the below exception in ULS log:

Internal server error exception: System.ServiceModel.FaultException Microsoft.Office.Server.Search.Query.KeywordQueryInternal.Execute()

SharePoint Health Analyzer - The following servers have not executed any timer jobs in the last 2 hours

What?

We have setup a new SharePoint 2010 production farm with 2 web servers. (One WFE and one APP). In the new farm, we have started to see a critical issue in the health analyzer that says "The following servers have not executed any timer jobs in the last 2 hours"

SharePoint 2010: Linq Exception - An item with the same key has already been added.

What?

All of a sudden we started to see a weird exception in our intranet "System.ArgumentException: An item with the same key has already been added." being thrown by a custom web part that shows results that are indexed by SharePoint 2010 Search.

Nintex Workflow 2010 - The dreaded "Workflow failed to run" error

What?

Workflows that are built using Nintex Workflow 2010 fail with error: "[Workflow Name] failed to run"
when the following actions are executed:

• Task Reminder Action
• Task Delegation Action
• Pause For

You may also notice that the workflows also don't perform as they should.

Nintex Workflow 2010 crashes IE unexpectedly during events such as when a new string variable is created in a workflow

What?

Nintex Workflow 2010 crashes IE unexpectedly and randomly when certain actions are performed such as when a new string variable is created in a workflow

Why?

Nintex Workflow 2010 at the time of posting this blog is not fully compatible with IE 10. It works perfectly with IE 9 and IE 8.