Qdabra Database Accelerator

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Tue, 15 Jan 2013 20:43:43 GMT

Sorry to waste your time. It seems like it's working now. I can't seem to figure out what could have changed. Thank you for your time.

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

ErnestoM — Tue, 15 Jan 2013 18:02:08 GMT

I have not, sorry if I misunderstood.

I think the culprit is the SQL DB connection, and I believe the issue would arise in form with qRules or forms with custom code.

Since the form is already set up as a doctype in DBXL, and the form submit to DBXL, then the solution is to use the QueryDB/QuerySharePoint methods.

If you would like us to perform a more in depth investigation (i.e. find out why the non-QueryDB data connection fails), please send email to Support (at) qdabra (dot) com and we'll open a support ticket for this. Thanks.

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Tue, 15 Jan 2013 17:03:59 GMT

Have you had a chance to look into this again? Eventually I would like to use the other code functionalities of qRules with DBXL.

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Thu, 10 Jan 2013 22:08:16 GMT

I can look into that. But did you run into the same problems I documented?

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

ErnestoM — Thu, 10 Jan 2013 16:56:38 GMT

My only thought is that, since you're already using DBXL, then the form could make use of the QueryDB web service and/or the QuerySharePoint web service. Have you had a chance to try those out?

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Thu, 10 Jan 2013 16:45:52 GMT

Have you had a chance to take a look?

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Tue, 08 Jan 2013 17:37:10 GMT

I had written a very long post, but it seems that it didn't get recorded. Since I don't feel like repeating myself today, here's a summary:

Something had changed and a SharePoint List Data connection did not cause any problems
Moved forward with adding a SQL Data source --> form on open errors out that it could not query data source
Turned off Automatically query data for SQL data source and then set form to wait till the QdabraRules field Formloadfinish = TRUE to query the SQL Data source --> a cross-domain / UDCX connection file requirement error
With Automatically query data turned off, I removed the previous formloadfinish rule and created a button to query the SQL data. Waited till the browser form load completed, then clicked the button, same cross-domain/UDCX error
So I followed the error's suggestion of creating a UDCX connection file (Relative site). Approved the UDCX conneciton file in the data connections library. Made sure Cross-domain for InfoPath was allowed. Published the form through DAT once more and now kicking off the query with a button does nothing.

<?xml version="1.0" encoding="UTF-8" ?>

<?MicrosoftWindowsSharePointServices ContentTypeID="0x010100B4CBD48E029A4ad8B62CB0E41868F2B0"?>

- <udc:DataSource MajorVersion="2" MinorVersion="0" xmlns:udc="http://schemas.microsoft.com/office/infopath/2006/udc">

<udc:Name>PFSection1aItemBFilersAssetsByFund</udc:Name>

<udc:Description>Format: UDC V2; Connection Type: Database; Purpose: ReadOnly; Generated by Microsoft InfoPath 2010 on 2013-01-07 at 17:04:11 by CORP\lokj.</udc:Description>

- <udc:Type MajorVersion="2" MinorVersion="0" Type="Database">

<udc:SubType MajorVersion="0" MinorVersion="0" Type="" />

</udc:Type>

- <udc:ConnectionInfo Purpose="ReadOnly" AltDataSource="">

<udc:WsdlUrl />

- <udc:SelectCommand>

<udc:ListId />

<udc:WebUrl />

<udc:ConnectionString>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=REGFORMS;Data Source=db-regforms-la01d,5500;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=LAD1013903;Use Encryption for Data=False;Tag with column collation when possible=False</udc:ConnectionString>

<udc:ServiceUrl UseFormsServiceProxy="false" />

<udc:SoapAction />

<udc:Query>select "PFSection1aItemBFilersAssetsByFundId" from "dbo"."PFSection1aItemBFilersAssetsByFund" as "PFSection1aItemBFilersAssetsByFund"</udc:Query>

</udc:SelectCommand>

- <udc:UpdateCommand>

<udc:ServiceUrl UseFormsServiceProxy="false" />

<udc:SoapAction />

<udc:Submit />

<udc:FileName>Specify a filename or formula</udc:FileName>

<udc:FolderName AllowOverwrite="" />

</udc:UpdateCommand>

- <!--

udc:Authentication><udc:SSO AppId='' CredentialType='' /></udc:Authentication

-->

</udc:ConnectionInfo>

</udc:DataSource>

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

ErnestoM — Tue, 08 Jan 2013 13:48:15 GMT

Hi-

Is there an update? I thought I had seen some info but now I see <deleted>?

Let us know. Thanks.

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Mon, 07 Jan 2013 19:16:13 GMT

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

ErnestoM — Sat, 05 Jan 2013 18:57:17 GMT

Could I take a look at the form?

I'd like to create a version that does not have the "Automatically retrieve data" checkbox checked in the Data Connetion Wizard, but instead queries the data connection when finishedLoading = TRUE.

I can make this change and send you the form back, so you can test. Thank you.

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Fri, 04 Jan 2013 22:01:58 GMT

These are the steps I tried

FIRST TEST --> SUCCESS

Took your form and published it to SharePoint
Form opens and saves fine in web browser

SECOND TEST --> SUCCESS

Took your form and attached it to DBXL
Created SharePoint mapping with "Publish LIbrary and XSN" and "Use Forms Services" checked
Clicked Save in DBXL
Form opens and saves fine in web browser

THIRD TEST --> SUCCESS

Took your form and removed the code
Injected form with qRules
Attached form to DBXL
Clicked Save in DBXL
Form opens and saves fine in web browser

FOURTH TEST --> FAILED

Took the form and added a data connection to a SharePoint list as Receive data
Attached form to DBXL
Clicked Save in DBXL
Form does not open, errors out
Browser error displayed: The custom code in the form cannot be run. This functionality may be deactivated on the server. For more information, contact the server farm administrator.
First SharePoint error log: "Sandboxed Code Service 0000 High - UserCodeExecutionProxy call failed. Microsoft.SharePoint.UserCode.SPUserCodeSolutionExecutionFailedException: Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust app domain: An unexpected error has occurred. ---> Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Object reference not set to an instance of an object. Server stack trace: at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.UrlIsSameFileOrSamePath(String absoluteFileUrl, String baseFileOrFolderUrl) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.IsSolutionMoved(Document document) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.GetList(WebHolder webHolder, Boolean impersonatedIdentity, Document document, String siteUrl, Boolean isUrlSetThroughOM, Guid listId) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.<>c__DisplayClasse.<Execute>b__3(Boolean impersonatedIdentity) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String userDomain, String password, CodeToRunUnderImpersonation codeToRun) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String password, CodeToRunUnderImpersonation codeToRun) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.Execute(String siteUrl, Guid listId, SPContentTypeIdcontentTypeId, Document document, DataAdapterListDataProvider documentAdapter, Boolean useDcl, XPathNavigator queryFields, XPathNavigator resultFields, Boolean isListItemEditing, Boolean discoveryOnly, Int64& auxDomSize) at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataAdapterListDataProvider.ExecuteInternal(XPathNavigator queryFields, XPathNavigator resultFields, Boolean useListItemMode) at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.QueryDataOnLoad(DataAdapter documentDataAdapter, DataObject documentDataObject) at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.ExecuteInitOnLoadForDataObjects() at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.LoadFromRemoteContext(Boolean firstOpened, String editingSessionId, Solution solution, Byte[] serializedState, Byte[] serializedVersionState, Dictionary`2 inputParams, OpenParameters openParameters) at Microsoft.Office.InfoPath.Server.Controls.XmlFormView..ctor(Solution solution, RemoteExecutionContext remoteExecutionContext) at Microsoft.Office.InfoPath.Server.Host.FormServerUserCodeWrapper.Execute(SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.ExecuteWrapper(SPUserCodeWrapper wrapper, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.CodeToExecuteWrapper.EndInvoke(IAsyncResult result) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) --- End of inner exception stack trace --- Server stack trace: atMicrosoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) at Microsoft.SharePoint.UserCode.SPUserCodeAppDomain.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxyForShim.ExecuteInternal(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxy.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.ExecuteDelegate.EndInvoke(IAsyncResult result) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String currentAffinity, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodePoolableProcessConnection.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String affinity, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeExecutionHost.Execute(Type userCodeWrapperType, Guid siteCollectionId, SPUserToken userToken, String affinity, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [1]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.Administration.ISPUserCodeExecutionHostProxy.Execute(Type userCodeWrapperType, Guid siteCollectionId, SPUserToken userToken, String affinityBucketName, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeExecutionManager.Execute(Type userCodeWrapperType, SPSite site, SPUserCodeExecutionContext executionContext)
Second SharePoint Log error: "FormServer Partial Trust - remote execution for solution b5e5e3f8-9d10-4a38-a2bf-cf8e20ea2700 from site 8caa4f82-b2f7-42f0-a3d4-ac8d0f34d4c0 failed with exception Microsoft.SharePoint.UserCode.SPUserCodeSolutionExecutionFailedException: Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust app domain: An unexpected error has occurred. ---> Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Object reference not set to an instance of an object. Server stack trace: at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.UrlIsSameFileOrSamePath(String absoluteFileUrl, String baseFileOrFolderUrl) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.IsSolutionMoved(Document document) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.GetList(WebHolder webHolder, Boolean impersonatedIdentity, Document document, String siteUrl, Boolean isUrlSetThroughOM, Guid listId) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.<>c__DisplayClasse.<Execute>b__3(Boolean impersonatedIdentity) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String userDomain, String password, CodeToRunUnderImpersonation codeToRun) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String password, CodeToRunUnderImpersonation codeToRun) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.Execute(String siteUrl, Guid listId, SPContentTypeId contentTypeId, Document document, DataAdapterListDataProvider documentAdapter, Boolean useDcl, XPathNavigator queryFields, XPathNavigator resultFields, Boolean isListItemEditing, Boolean discoveryOnly, Int64& auxDomSize) at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataAdapterListDataProvider.ExecuteInternal(XPathNavigator queryFields, XPathNavigator resultFields, Boolean useListItemMode) at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.QueryDataOnLoad(DataAdapter documentDataAdapter, DataObject documentDataObject) at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.ExecuteInitOnLoadForDataObjects() at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.LoadFromRemoteContext(Boolean firstOpened, String editingSessionId, Solution solution, Byte[] serializedState, Byte[] serializedVersionState, Dictionary`2 inputParams, OpenParameters openParameters) at Microsoft.Office.InfoPath.Server.Controls.XmlFormView..ctor(Solution solution, RemoteExecutionContext remoteExecutionContext) at Microsoft.Office.InfoPath.Server.Host.FormServerUserCodeWrapper.Execute(SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.ExecuteWrapper(SPUserCodeWrapper wrapper, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.CodeToExecuteWrapper.EndInvoke(IAsyncResult result) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) --- End of inner exception stack trace --- Server stack trace: at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) at Microsoft.SharePoint.UserCode.SPUserCodeAppDomain.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxyForShim.ExecuteInternal(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxy.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.ExecuteDelegate.EndInvoke(IAsyncResult result) at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String currentAffinity, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodePoolableProcessConnection.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String affinity, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeExecutionHost.Execute(Type userCodeWrapperType, Guid siteCollectionId, SPUserToken userToken, String affinity, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [1]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.Administration.ISPUserCodeExecutionHostProxy.Execute(Type userCodeWrapperType, Guid siteCollectionId, SPUserToken userToken, String affinityBucketName, SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeExecutionManager.Execute(Type userCodeWrapperType, SPSite site, SPUserCodeExecutionContext executionContext) at Microsoft.Office.InfoPathServer.DocumentLifetime.PartialTrustExecutorHelper.<>c__DisplayClass1.<PlayEventLogInRemote>b__0(), inner exception Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Object reference not set to an instance of an object. Server stack trace: at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.UrlIsSameFileOrSamePath(String absoluteFileUrl, String baseFileOrFolderUrl) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.IsSolutionMoved(Document document) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.GetList(WebHolder webHolder, Boolean impersonatedIdentity, Document document, String siteUrl, Boolean isUrlSetThroughOM, Guid listId) at Microsoft.Office.InfoPath.ServerSolutionLifetime.DataAdapterListDataProvider.<>c__DisplayClasse.<Execute>b__3(Boolean impersonatedIdentity) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String userDomain, String password, CodeToRunUnderImpersonation codeToRun) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String password, CodeToRunUnderImpersonation codeToRun) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterListDataProvider.Execute(String siteUrl, Guid listId, SPContentTypeId contentTypeId, Document document, DataAdapterListDataProvider documentAdapter, Boolean useDcl, XPathNavigator queryFields, XPathNavigator resultFields, Boolean isListItemEditing, Boolean discoveryOnly, Int64& auxDomSize) at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataAdapterListDataProvider.ExecuteInternal(XPathNavigator queryFields, XPathNavigator resultFields, Boolean useListItemMode) at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.QueryDataOnLoad(DataAdapter documentDataAdapter, DataObject documentDataObject) at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.ExecuteInitOnLoadForDataObjects() at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.LoadFromRemoteContext(Boolean firstOpened, String editingSessionId, Solution solution, Byte[] serializedState, Byte[] serializedVersionState, Dictionary`2 inputParams, OpenParameters openParameters) at Microsoft.Office.InfoPathServer.Controls.XmlFormView..ctor(Solution solution, RemoteExecutionContext remoteExecutionContext) at Microsoft.Office.InfoPath.Server.Host.FormServerUserCodeWrapper.Execute(SPUserCodeExecutionContext executionContext) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.ExecuteWrapper(SPUserCodeWrapper wrapper, SPUserCodeExecutionContext executionContext) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg,Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.CodeToExecuteWrapper.EndInvoke(IAsyncResult result) at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId).

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Fri, 04 Jan 2013 21:50:19 GMT

Re: DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

ErnestoM — Fri, 04 Jan 2013 13:22:36 GMT

Hi,

I'm sorry you've run into issues.

I would suggest trying a couple of troubleshooting steps to see if the issue can be narrowed down, since the form has a lot of moving parts (qRules, DBXL, data connections).

1. I'm attaching a very simple form with code. With it, I would suggest:

(a) Creating a DBXL document type with a SharePoint mapping

(b) Publishing the form directly to the server (to a new form library)

2. Create a new, blank form, inject it with qRules, and perform steps a and b above.

Let us know what you find. If you want to attach screenshots or an XSN, you can do so via the Options tab. Thank you.

DBXL 2.6, qRules 4.2, SharePoint 2010, InfoPath browser-based Data connections issue

tenbao — Fri, 04 Jan 2013 01:12:04 GMT

I seem to be having problems being able to run a combination of DBXL 2.6, qRules 4.2 and InfoPath browser-based forms with data connections. Currently I have a form that has qRules 4.2 injected. When following instructions on publishing the InfoPath form to a sandbox through the DBXL DAT, I receive no errors. But when I open the browser-based form, I receive the below error.

"The custom code in the form cannot be run. This functionality may be deactivated on teh server. For more information, contact the server farm administrator."

The error only occurs if I have the combination of qRules injected with data connections to a BCS list or SQL data source. SharePoint and Event logs don't indicate any clear errors. I have made sure to turn on the Sandbox service and verified that the form solution is activated on the site collection. This error occurs even though no qRules are being called.

My ultimate goal is to have a browser-based form that submits to DBXL, which can also query SQL to update repeating fields in the form.

I would appreciate any help.