none
Infopath sandboxed publishing error in SP 2013

    Question

  • Hi,

    I am trying to publish sandboxed infopath form that has been migrated from SharePoint 2010 to 2013 ? But while same form works in 2010 it doesn't work in 2013. I stripped down a lot of views and finally published it but i get same error in uls log view.

    UserAgent not available, file operations may not be optimized.  

     at Microsoft.SharePoint.SPFileStreamManager.get_UserAgent()   

     at Microsoft.SharePoint.SPFileStreamManager.SetOutputLockBytes(ILockBytes ilbIn)   

     at Microsoft.SharePoint.Library.SPRequestInternalClass.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int64 cbFile, Object punkSPFileMgr, Object punkFFM, Int64 PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, SPFileSaveParams sfsp, SPFileInfo& pFileProps, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)   

     at Microsoft.SharePoint.Library.SPRequestInternalClass.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int64 cbFile, Object punkSPFileMgr, Object punkFFM, Int64 PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, SPFileSaveParams sfsp, SPFileInfo& pFileProps, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)   

     at Microsoft.SharePoint.Library.SPRequest.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int64 cbFile, Object punkSPFileMgr, Object punkFFM, Int64 PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, SPFileSaveParams sfsp, SPFileInfo& pFileProps, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)   

     at Microsoft.SharePoint.SPFileCollection.AddStreamOrBytesInternal(String urlOfFile, Stream file, Int64 fileSizeToSave, SPFileStreamManager spmgr, PutFileOpt fileOpt, String createdBy, String modifiedBy, Int32 createdByID, Int32 modifiedByID, DateTime timeCreated, DateTime timeLastModified, Object varProperties, String checkInComment, Stream formatMetadata, String lockIdMatch, String etagToMatch, SPLockType lockType, String lockId, TimeSpan lockTimeout, Boolean validateRequiredFields, SPVirusCheckStatus& virusCheckStatus, String& virusCheckMessage, String& etagNew, Boolean& ignoredRequiredProps)   

     at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Stream file, Boolean overwrite, String checkInComment, Boolean checkRequiredFields)   

     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.UploadWspSolution(FileStream wspFileStream, String wspSolutionName, SPSite site, SPFile originalFile)   

     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.CreateAndActivateWspSolution(SPSite site, SPFile originalFile, SolutionInformation information, String& wspSolutionName, String& wspSolutionHash)   

     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.<>c__DisplayClass3.<Activate>b__0()   

     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)   

     at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.Activate(ConversionContext context, FormsService formsService, SPSite site, SPFile originalFile, ActivationFlags activationFlags, ConverterLog& conversionLog)   

     at Microsoft.Office.InfoPath.Server.Administration.FormsService.BrowserEnableUserFormTemplate(SPFile solutionFile)   

     at Microsoft.Office.InfoPath.Server.FormsServicesWebService.BrowserEnableUserFormTemplate(String formTemplateLocation)   

     at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)   

     at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)   

     at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)   

     at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)   

     at System.Web.Services.Protocols.WebServiceHandler.Invoke()   

     at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()   

     at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)   

     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()   

     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)   

     at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)   

     at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)   

     at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)   

     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)   

     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)   

     at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)   

     at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)   

     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)   

     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

    Solution Deployment : Looking for 'ReceiverAssembly' attribute in manifest root node for solution 'InfoPath Form_xsn_AnZw6uZd_1.0.0.2464.wsp'.

    Solution Deployment : Looking for 'ReceiverClass' attribute in manifest root node for solution 'InfoPath Form_.xsn_AnZw6uZd_1.0.0.2464.wsp'.

    Solution Deployment : Missing one or more of the following attributes from the root node in solution InfoPath Form_.xsn_AnZw6uZd_1.0.0.2464.wsp: assembly '', type ''.

    Timeout while waiting for request to complete within the sandboxed appdomain

    -  - 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 = "DC867F1D3BBE4C8B9A536CDBB54B412C-UIrNMR4rChl5FDCoT5qyJLVb03x1GibWZ4TuPywJnNI=", siteCollectionId = "66c215c2-7207-4c6b-b73d-50497b5b1ca8" - Inner Exception: Microsoft.SharePoint.UserCode.SPUserCodeSolutionProxiedException: Timeout while waiting for request to complete within the sandboxed appdomain


    sachin

    Monday, August 26, 2013 7:45 PM

All replies

  • Interesting enough I have the same problem for forms with sandbox code.  We increased the timeout from 30 seconds to over 60 seconds and got it to publish with out stripping out views for some smaller forms (4-6 small views).  Bigger forms (6-8 larger views) still time out. (In 2010 they would publish in 20 seconds or less) Tried troubleshooting the process by selectively removing different items.   Nothing except the total number of views made any difference.   We ran fiddler on the client and compared it to the publish process on 2010 and everything is the same except the web post to the formservices.asmx when the InfoPath client is actually doing the form publish to the forms server.   This is the post after the form is pushed to the server and  after creation of the content type.  The response message comes back correctly but just says the form must be filled out using filler and not the browser.  No other network communication issues or windows events were observed except for similar uls postings as noted above.

    I have tried posting the form with Infopath 2010 (vs2005) and Infopath 2013 (vs2012).

    Tuesday, August 27, 2013 5:33 AM
  • Yes i have made form services time out 60 seconds and after stripping the views it got published but still these errors showed up in the logs. I do not have any idea where else to fix this since all these get configured by SharePoint on its own. If you get anything please post here. We also ran fiddler and same web service would either fail or pass for the infopath form.

    sachin

    Tuesday, August 27, 2013 2:14 PM
  • Hi sachin,

    thank you for your post,

    perhaps regarding this issue you may try to check:

    1. make sure the 2 sandbox feature at service in central admin are restarted

    2. try to add the time out to 2 minutes as default,

    3. please have a check on your web.config,  <httpRuntime requestLengthDiskThreshold = “4096″ />

    if the issue still persist, then perhaps this issue is a starvation issue, that we need to capture more logs, such as ULS-verbose logs, and WCF logs, then if its true, you may need to double check your infopath form design.

    http://blogs.msdn.com/b/cliffgreen/archive/2013/02/19/sharepoint-2013-the-directory-is-not-a-subdirectory-of-the-root-directory.aspx


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, August 28, 2013 8:32 AM
  • Where should i add this httpRuntime requestLengthDiskThreshold = “4096″ /> in web.config file?

    sachin

    Wednesday, August 28, 2013 8:09 PM
  • Hi sachin,

    please check this article:

    http://msdn.microsoft.com/en-us/library/e1f13641(v=vs.85).aspx

    http://msdn.microsoft.com/en-us/library/vstudio/e1f13641(v=vs.100).aspx

    example:

    <configuration>
       
    <system.web>
           
    <httpRuntime requestLengthDiskThreshold = “4096″ />
       
    </system.web>
    </configuration>


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, August 29, 2013 2:45 AM