Have you seen Product Update - What you need to know?
Version 1.3.x was the first version of Nintex Forms 2010 to support the functionality of Nintex Mobile.
To take advantage of the functionality offered by Nintex Mobile, continue below or proceed to the next section, “Regular Upgrade Process”.
If your SharePoint farm is exposed outside of your corporate network via internet, you may want to provision communication for Nintex mobile in-house. This method is more direct and faster than communication via Nintex Live.
If your SharePoint farm is not available outside of your corporate network, the Nintex Live option allows Nintex Mobile to communicate with your environment. Uploads using this channel are restricted to a maximum of 100MB per item.
If you choose the option to use Nintex Mobile via Nintex Live, you must install the .NET 4 Framework on at least one web front end (WFE) server in your SharePoint farm before installing 1.3. This will enable the installation of two NT services (components referred to as “Live Relay” services), one of which requires .NET 4 to communicate with Nintex Live. Both of these NT services must be installed on the same server and that server must be a licensed web front end.
Once you have chosen which server will host the services, install the .NET 4 Framework. The installer is available here:
Please note: When the Nintex Forms installer is run, it will look for any servers running the .NET 4 Framework and deploy the Nintex Live Relay services to them. They are started on selected servers at a later point via SharePoint Central Administration.
Ensure the user account that is performing the Installation/Deployment (Windows user as well as user logged into Central Administration) is the Farm Installation account and that it is a Local Administrator on the Server you are installing on.
Installing Nintex Forms Enterprise Edition (optional)
Updating from previous versions
To update from previous versions of Nintex Forms 2010, download the NintexForms2010.exe file and save it to your server environment. Double-click the file and follow the guides and instructions in the installation script. All updates to the application and database will be applied.
If you have chosen to not use Nintex Live or Nintex Mobile, the upgrade is now complete.
If you have previously installed and configured both Nintex Live and Nintex Mobile, the upgrade is now complete.
*If using Nintex Live and Nintex Mobile for the first time, please read steps below to continue and complete the upgrade:
If Nintex Live has not previously been used:
Establish a Connection to Nintex Live
The Nintex Live Framework requires a connection to the internet to communicate with Nintex Live.
Configure Nintex Live Forms
Note: Allowing anonymous form submissions may require Microsoft server internet licensing.
Nintex Live is already configured but Nintex Mobile is not
Emily Billing Hi Emily, Looking for your assistance. We recently upgraded from 184.108.40.206 to 220.127.116.11. I ran the installer which took very long time to retract the wsp, Hence I retracted the wsp (nintexforms2010.wsp) manually. Then, I ran the installed again, and it completed successfully and I could see the wsps (nintexforms2010.wsp, nintexforms2010core.wsp ) in the Farm Solution in CA. The version in the Licensing page is also updted. The forms are working (New Item, Edit Item), but as I tested to publish an existing form through Form Designer it throw the following error,
"The server encountered an error processing the request. The exception message is 'Could not find stored procedure 'NM_DeleteFormByContentTypeAndList'.'. See server logs for more details."
As I looked at the SQL DB of the Nintex Forms database, the new stored procedures as part of the upgraded cannot be found in the Nintex Forms database. What do you suggest to resolve the problem.
Appreciate your speedy reply on this as this is our Production farm.
Worked with Nintex Support call and got this resolved. Ran this command based on their guidance in Management Shell: upgrade-nfservice and it resolved the problem. I was told that this command should be run only if we have post-upgrade issue.