InfoPath Dev

 You will need a try/catch around the EnsureUser call.  If the user does not exist in the SharePoint user list for the site, the user is attempted to be added to the site.  This is why it works for administrators but not normal users.  If the user already exists on the site, normal users should not get an exception.  You ...

Authentication will either require your environment be configured using Kerberos, which can be complex to get configured.  The other alternative is to use credentials from the Secure Store Service.  If connecting to the remote service using a single set of credentials is sufficient, that would be the quickest way of getting it ...

  This is a client side error.  In Control Panel you can go through Programs and Features and select change for Microsoft Office.  Then make sure the .NET Programmability Support is installed

A couple of questions:How are individual doctype permissions configured? Are new users just not able to submit to DBXL?Is the user alias is the same across domains?  If you are using the Qdabra Active Directory web service,  you can add a second domain for lookups if you have a later version of DBXL.  I believe v2.8 and later ...

Your InfoPath XSNs likely have hrefs and data connections pointing to http://frednet.   To force these to resolve to the DR environment, you can configure the servers' hosts files to resolve frednet to the frednetdr (you will need to use DisableLoopbackCheck or BackConnectionHostNames when doing this).  Client machines ...

This could also be a matter of having multiple DBXL servers. We had a customer recently updated their Production environment, but the app in error was using the DEV environment url. If you have QA and Production environments, you will need to apply the license to each.

Calling GetUserProfileByName in Office 365 has been a big problem.  Here is a thread on similar issue that has a workaround for getting details in the form via web part connections:  http://www.infopathdev.com/forums/p/22986/79536.aspx Is the GetUserProfileByName being called automatically on load, or are you executing in a rule in ...

 You are running into the throttling limit in SharePoint.  To change the limit, you can go to Central Admin, manage general settings and Resource throttling.  Adjust the List View threshold as needed.  Please be aware that this can affect overall SharePoint performance. Jim Cantwell Qdabra  

Correction: I was mistaken, Microsoft.SharePoint.Administration is available in the sandbox. I will review the logs further to maybe see why it was unable load the assembly.

The DBXL event receiver will submit the document to DBXL whenever the SharePoint Added, Updated or Deleting events are fired. Workflow operations that update the form content should generate these events and the DBXL document updated.