SharePoint Integration

Re: InfoPath Web Part error with q-rules browser form.

Catharine — Thu, 15 May 2014 09:19:23 GMT

Hi Hilary,

Thank you for your reply.

I am Site Collection Admin for the site I am trying to run this on.

I have re-injected q-rules to ensure I have Sandboxed and Browser checked.

I have run the Design Checker with verify on server checked. I now have 1warnings Data connections contain parameterized queries, and numerous browser Optimizations.

I have re-published the form to the library, no errors in the publish. When I click on the open I still get the error.

In the logs I get....

- - Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust app domain: An unexpected error has occurred. - userCodeWrapperType = "Microsoft.Office.InfoPath.Server.Host.FormServerUserCodeWrapper", userAssemblyGroupId = "82AC8447486045A3A46C91B487B5666D-oHWTM3HxAhXW+WV06DPsSI01qbY+o3TteT0141meqxw=", siteCollectionId = "c02e2c04-12b1-4d9b-aec3-1f61ec8a6f95" - Inner Exception: Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Could not load type 'Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager' from assembly 'Microsoft.SharePoint, Version=14.900.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. Server stack trace: at Microsoft.Office.InfoPath.Server.SolutionLifetime.UserHost.GetCurrentUserAccountName() at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.CreateDocument(HttpContext context, SPSite contextSite, String editingSessionId, Solution solution, String webUrl) 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.SPUserCodeApplicationHostAppDomainRefExecute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)

followed by

- - Could not load type 'Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager' from assembly 'Microsoft.SharePoint, Version=14.900.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. - Request executing userSolution Id "82ac8447-4860-45a3-a46c-91b487b5666d" for site collection id " c02e2c04-12b1-4d9b-aec3-1f61ec8a6f95" has encountered an unhandled exception while executing user code.

Does that help ?

Re: InfoPath Web Part error with q-rules browser form.

Hilary Stoupa — Wed, 14 May 2014 23:18:50 GMT

Hi - so if you are getting the same error when you open the browser, I'm surprised you didn't get a warning when you published it that it wouldn't open in the browser. Are you publishing directly to a library to sandbox the form?

Usually what I do in these cases is try to publish the form directly to the library, then review the SharePoint log files for the time of publish to see if there is any info there. Then, I try opening the form in the browser and again review the logs.

If the form has not been injected with the Admin Approve option selected, it should be able to be published directly to a library instead of admin approved, as long as you are a site collection admin. This will sound ridiculous, but I have found I cannot sandbox a form as a farm admin - I have to be an actual site collection admin....

Your form should not have to be full trust. Domain trust, injected w/ qRules Browser option selected for the correct version of InfoPath, and then, after ensuring you are a site collection admin, try publishing to a library again.

InfoPath Web Part error with q-rules browser form.

Catharine — Wed, 14 May 2014 15:40:40 GMT

Hi All,

Wasn't sure what Forum to put this on....SharePoint or Q-rules.

I have an InfoPath Form and SharePoint 2010. I have injected Q-rules 5.1 for browser based forms.

The InfoPath Form services are activated in the site collection.

When I try and open the form in an InfoPath form web part I get an error message. 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.

I am one of the farm administrators and don't really know where to go now.

Does a q rules form have to be an administrator form ?

When the form opens from SharePoint in the client it works fine, but when it opens in the browser it produces the same error. .

The form is currently Domain Security level (Should it need to be full trust?) Checking the form for browser compatibility I get one warning about data connections having parameterized queries.

Once the form is opened it works until I access a field with rules which interacts with the command line in q-rules, at which point I get the same error.

Thank you for your advice.

Catharine