Share via

The publish operation could not be completed. It cannot be determined if the form template was successfully published... while publishing InfoPath form to Sharepoint

  • Article

When you are trying to publish Infopath form to Sharepoint forms library, you might get the below error messages.

"The publish operation could not be completed. It cannot be determined if the form template was successfully published. Try publishing the template again, or change the list settings to use the default SharePoint form."

"InfoPath cannot connect to the server. The server may be offline, your computer might not be connected to the network, or InfoPath Forms Services 2010 might not be enabled on the server. To fix this problem, start by checking your network connection, and then try again."

The above error message is a very generic error message. It might also occur due to execution time out and other reasons.To understand the issue better we captured the ULS logs and found the below error messages.

06/12/2015 09:40:07.50 w3wp.exe (0x3528) 0x2D4C SharePoint Foundation General ai1wu Medium System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002), StackTrace: at Microsoft.SharePoint.SPWeb.GetList(String strUrl) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.VerifyListPresence(SPSite site, Boolean& foundFormTemplateLibrary, Boolean& foundConvertedLibrary) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<IsSupportFeaturePresent>b__15(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass13.<IsSupportFeatureActiveNoCache>b__12(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.AccessSiteUnderSystemAccount(SPSite site, VisitSite siteHandler) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeatureActiveNoCache(SPSite site, Guid featureId, Action`1 actionIfFound) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeaturePresent(SPSite site, Guid featureId) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DesignCheckerVerificationContext.OnAfterSolutionInformationParse(SolutionInformation information) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.TryRunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId, Byte[] solutionData, WspSolutionInfo wspSolution) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.RunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass7.<VerifyUnpackedSolution>b__6() at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.VerifyUnpackedSolution(SolutionCabinet solutionCabinet, String originalFileName, ConversionContext context, ConverterLog& outputConverterLog, Byte[]& outputConvertedData) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.VerifySolution(String absoluteLocalPath, ConversionContext context, ConverterLog& converterLog, Byte[]& convertedData) at Microsoft.Office.InfoPath.Server.FormsServicesWebService.DesignCheckFormTemplate(Int32 lcid, String base64FormTemplate, String applicationId) 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) 16ad0f9d-0e35-d08a-3e99-936b9eee525f

06/12/2015 09:40:07.62 w3wp.exe (0x3528) 0x2D4C InfoPath Forms Services Runtime m1y5 Exception LoadDocumentAndPlayEventLog failed with unhandled exception Microsoft.Office.InfoPath.Server.Util.InfoPathLocalizedException: Activation could not be completed because the InfoPath Forms Services support feature is not present. at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<IsSupportFeaturePresent>b__15(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass13.<IsSupportFeatureActiveNoCache>b__12(SPSite revertedSite) at Microsoft.Office.InfoPath.Server.Administration.NonAdminSolution.AccessSiteUnderSystemAccount(SPSite site, VisitSite siteHandler) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeatureActiveNoCache(SPSite site, Guid featureId, Action`1 actionIfFound) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.IsSupportFeaturePresent(SPSite site, Guid featureId) at Microsoft.Office.InfoPath.Server.SolutionLifetime.DesignCheckerVerificationContext.OnAfterSolutionInformationParse(SolutionInformation information) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.TryRunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId, Byte[] solutionData, WspSolutionInfo wspSolution) at Microsoft.Office.InfoPath.Server.Converter.ConversionAppDomain.RunConversion(ConversionContext context, SolutionCabinet solutionCabinet, SolutionIdentity solutionId) at Microsoft.Office.InfoPath.Server.Util.InstalledSolutions.<>c__DisplayClass7.<VerifyUnpackedSolution>b__6() at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) StackTrace: at Microsoft.Office.Server.Native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21BE5) 16ad0f9d-0e35-d08a-3e99-936b9eee525f

  • From the above stack trace, we see that the feature is not activated.
  • We ran the below commands to get the status and the scope of the IPFSSiteFeatures. (Infopath Form Services Feature).

$a = get-spfeature "IPFSSiteFeatures"

$a.status

online

$a.scope

site

  • The IPFSSiteFeatures is activated already. When we ran the below command, we got the error messsage "Feature 'a0e5a010-1329-49d4-9e09-f280cdbed37d' is not activated at this scope"

Stsadm.exe -o deactivefeature -filename IPFSWebFeatures\feature.xml -url ""

  • We activated the IPFSWebFeatures using the below command and we are able to publish the InfoPath form successfully.

Stsadm.exe -o activatefeature -filename IPFSWebFeatures\feature.xml -url ""