InfoPath Dev

Based on the text of the message, you are installing on the SharePoint 2010 site. You will need to install to a standalone site not used by SharePoint. It can still be on the same server, just not on a SharePoint site.

The normal SharePoint upgrade process will include the InfoPath templates. After the migration, you will need to update any InfoPath browser forms that have code to be InfoPath 2013 browser forms.

You should find the following files in the zip download: 7z.dll 7z.exe FormsViewer On-Premise Installation and ...

Configuring cross-domain web service calls is only required when you need the browser client to connect directly to the endpoint for authentication reasons. If you do not configure for cross-domain, the call will go through the FormsViewer proxy. The proxy can make calls to web services anonymously, or using credentials saved under "Manage ...

Yes, you can use a remote SQL Server instance. The install location can be any server, it is more a server load question. FormsViewer is not very resource intensive, but if you SharePoint WFE is low on resources, you may want to put on a lower utilized server. It is sometimes easier to put on the WFE that already has routing configured where ...

This error will occur if you have the QRules 2010 browser dll injected. Re-inject for SharePoint 2013 browser and it should resolve it.

DBXL v3.2 must be installed on a non-SharePoint site. This error would normally be a result of authentication failing. If installed on SharePoint site, that would definitely be an issue. If installing on a clean server with just IIS, you are possibly missing some feature dependencies. The DBXL installation guide has a list of features to ...

My apologies Catharine, I was having a Friday morning moment. Not sure why I was thinking this was DBXL related. I will check if we've seen this issue with Nintex workflows before.   You might test whether a SharePoint workflow will start properly, and determine if it is Nintex specific, or general SharePoint workflow related.

First thing to check is that  DBXL web.config has the <System.Workflow.ComponentModel.WorkflowCompiler> section copied from the SharePoint web.config.  This is required for workflows to function properly when updated by DBXL (and not using web services option).  If you need to use web services with a ...

Did you receive a Correlation ID that you can find in the logs?  I recommend using Merge-SPLogFile to find the log entries, as it will pull together the logs from all the servers. If the error is caused by exceeding a sandbox limit, it should show in the logs.  You can then adjust the specific setting that is being exceeded.