Re: Error publishing an InfoPath Browser Form on SharePoint 2013

ErnestoM — Wed, 18 Jun 2014 13:21:43 GMT

Thanks for checking.

When thinking about the site, those are the two things we typically look for: the user being a Site Collection Admin and the Sandbox service enabled.

As far as the form itself, please check that the form template is an InfoPath 2013 browser form, and that it is injected with the 2013 Browser option in the qRules injector.

Feel free to attach the form and we can take a look at it. Thanks.

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

Björn Brand — Wed, 18 Jun 2014 07:39:55 GMT

Yes, my User is Site Collection Administrator.

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

ErnestoM — Tue, 17 Jun 2014 20:50:28 GMT

Could you check to see if you are a site collection admin?

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

Björn Brand — Tue, 17 Jun 2014 14:32:03 GMT

By the way: The Sandbox service is started. I have tested the service with another sandbox solution. In Office 365 I can publish the form easily.

Error publishing an qRules Injected InfoPath Browser Form on SharePoint 2013

Björn Brand — Tue, 17 Jun 2014 14:23:01 GMT

When I try to publish to SharePoint 2013 browser form I get the message:

"The form template has been published to the server but it can only be opened in the InfoPath Filler Because it contains features that are not compatible with Web browser"

The form can also only open in the InfoPath Filler.

During the upload process, the sandbox solution is displayed in the Solution Library. After the error, the file will be deleted automaticly.

I have been used a simple form to test without data connections or qRules functions. The form may be published through the Central Administration, however this is nor solution for the customer project.

The following errors are displayed to ULS Log:

- - Error activating type from sandboxed code assembly. The cached sandboxed assembly could not be found. - this.UserCodeAssemblyGroupId = ", GroupId = "EAD5EDCDCCDC40648D920DDCD21CF9EB-jbTPYgfZKEPQ4fWgtzI6bBnhHVI9k0+SfzOVA0uRmSc="", assemblyName = "System.AddIn, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

- - Timeout while waiting for request to complete within the sandboxed appdomain. - userCodeWrapperType.FullName = "Microsoft.Office.InfoPath.Server.Host.FormServerUserCodeWrapper", userAssemblyGroup = ".UserCodeAssemblyGroupId = ", GroupId = "EAD5EDCDCCDC40648D920DDCD21CF9EB-jbTPYgfZKEPQ4fWgtzI6bBnhHVI9k0+SfzOVA0uRmSc="", .RootDirectoryPath = "C:\ProgramData\Microsoft\SharePoint\UCCache\8D157870ED982FD\EAD5EDCDCCDC40648D920DDCD21CF9EB%2DjbTPYgfZKEPQ4fWgtzI6bBnhHVI9k0%2BSfzOVA0uRmSc%3D-C"", siteCollectionId = 8d7d6f59-acd5-44a3-815d-9806ab89a782, executionContext = "Microsoft.Office.InfoPath.Server.DocumentLifetime.RemoteConversionContext

- - 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 = "EAD5EDCDCCDC40648D920DDCD21CF9EB-jbTPYgfZKEPQ4fWgtzI6bBnhHVI9k0+SfzOVA0uRmSc=", siteCollectionId = "8d7d6f59-acd5-44a3-815d-9806ab89a782" - Inner Exception: Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Timeout while waiting for request to complete within the sandboxed appdomain

- - Timeout while waiting for request to complete within the sandboxed appdomain. - Request executing userSolution Id "ead5edcd-ccdc-4064-8d92-0ddcd21cf9eb" for site collection id " 8d7d6f59-acd5-44a3-815d-9806ab89a782" has encountered an unhandled exception while executing user code

- 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: Timeout while waiting for request to complete within the sandboxed appdomain.       -
-- 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, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)    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.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, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)    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)

FormServer Partial Trust - remote conversion for solution IW:/apps/000100/scheduling form/Forms/template.xsn, tag:tPK1y4oxvlGjEsE6edILBpiYu4HwnlZJcLLhGAYJw(InfoPath Form_scheduling form_E1rZ1CKP_1.0.0.283.wsp) from site 8d7d6f59-acd5-44a3-815d-9806ab89a782 failed with exception Unhandled exception was thrown by the sandboxed code wrapper's Execute method in the partial trust app domain: An unexpected error has occurred.

Deployment failed conversion, or design checker found fatal errors: The sandboxed solution could not be activated. 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.

Qdabra qRules

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

Re: Error publishing an InfoPath Browser Form on SharePoint 2013

Error publishing an qRules Injected InfoPath Browser Form on SharePoint 2013