InfoPath Dev

Hello, Could you do me a favor? I am a PowerApps user, and am not familiar with InfoPath. What I found after I researched was it was hard to find an InfoPath community since it has been replaced by PowerApps. We won't use the infoPath in a few months, but I need to figure out this issue for my job. The issue is that, After I published the InfoPath form in the same location and as a same name, (The compatibility was a web browser form infopath 2010. 2007 didn't work), it kept saying that the form can not be opened in a web browser. Is there anyone who can help me with this issue?

The Correlation ID is Outer Exception: This form cannot be opened in a Web browser. To open this form, use Microsoft InfoPath.. Stack trace: at Microsoft.Office.InfoPath.Server.Util.InfoPathException.LogException(Exception e) at Microsoft.Office.InfoPath.Server.DocumentLifetime.FormInvocation.DetermineErrorInformation(SPSite contextSite, Boolean& isClientOnlyCrossServer, Uri absoluteSolutionUri, FormTemplate formTemplate, Boolean isCrossSiteException, SolutionMetaInformation& solutionMetaInformation, InfoPathException& error) at Microsoft.Office.InfoPath.Server.DocumentLifetime.FormInvocation.TryCreateSolutionMetaInformationByUrl(SPSite contextSite, String xsnLocation, SolutionMetaInformation& solutionMetaInformation, String& absoluteSolutionLocation, InfoPathException& error, Boolean& isClientOnlyCrossServer) at Microsoft.Office.InfoPath.Server.DocumentLifetime.FormInvocation.TryFetchMetaInformation(SPSite contextSite, String xmlLocation, String xsnLocation, String saveLocation, InfoPathXmlDocument document, DocumentMetaInformation& documentMetaInformation, SolutionMetaInformation& solutionMetaInformation, String& absoluteSolutionLocation, InfoPathException& error, Boolean& isClientOnlyCrossServer) at Microsoft.Office.InfoPath.Server.Controls.FormServerPage.NewEditingSession(SPSite contextSite, FormServerPageQueryParameters queryParameters, Boolean isFormServerProperlyConfigured, Boolean& renderSessionsStateError) at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.StartNewEditingSession() at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.EnsureDocument(EventLogStart eventLogStart) at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.<>c__DisplayClassb.b__5() at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) at Microsoft.Office.InfoPath.Server.DocumentLifetime.ErrorPageRenderer.RunAndGetErrorRendererOnException(HttpContext context, EventLogStart eventLogStart, TryBlock tryblock, CatchBlock catchblock) at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.LoadDocumentAndPlayEventLog() at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnDataBindHelper() at Microsoft.Office.InfoPath.Server.Controls.XmlFormView.OnDataBinding(EventArgs e) at System.Web.UI.WebControls.WebParts.Part.DataBind() at Microsoft.Office.InfoPath.Server.Controls.FormServerPage.Initialize() at Microsoft.Office.InfoPath.Server.Controls.FormServerPage.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at Microsoft.Office.InfoPath.Server.Controls.FormServerPage.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) 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) .

Any chance I can see a copy of the form? You can attach it under the Options tab in a reply. You might try using the Design Checker to see if it will tell you what's wrong: https://support.microsoft.com/en-us/office/introduction-to-the-design-checker-task-pane-474a1a54-ae56-42cd-b505-1f8ec20852c4

Hello Hilary, Thank you for your help. Unfortunately I can't share with others since I need permission to copy it to my computer. But I used the designer checker and it said Control sends data to serve when value changes(primary cause) I have attached the error message to this chat.

Here is one more error message

One more

In theory, I'd think since these are all warnings, they should not prevent the form from being opened in the browser. However, you may want to try to change the data connections to not be available offline - just to see if that makes a difference. That would be under Form Options - from the File Menu > Info > Click on the Form Options button and deselect the offline option.

Thank you for your help again! I was not able to enjoy my weekend due to this issue. Alas. Your help means a lot to me. I've just checked the offline. That was already marked. Is there anything I can do? I hope I can create this form using PowerApps but I am allowed it yet.

Try deselecting that option and publishing again.

I deselected and published but it didn't work. I've attached this image.

The message is attached.

Again, I wouldn't expect any of these warnings to prevent the form opening the browser. The compatibility is still set to browser enabled? That's also under form options. You may want to make a copy of the form and publish it to a test library, then you can try removing things from the form to narrow the issue down. You could also try running a tool like Fiddler when publishing to see if you can get any better info back from the publish process around why it is failing to browser enable.

Yes, that is what I first checked when it happened. The compatibility was the web browser form (infopath 2010), I tried the 2007, but it didn't work. I've attached images. I will look up on the internet to findthe Fiddler.

Hello Hilary, I am sorry to bother you. I got an error message, "Error loading form code assembly: Could not load file or assembly 'Microsoft.Office.InfoPath, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.." This is InfoPath 2010, and SharePoint 2013. Is there anything I can do for it? I found this question and replies,(https://social.technet.microsoft.com/Forums/en-US/0f4855f7-aa03-4580-85f0-e8672ad0f86d/infopath-forms-arent-uploading-in-central-admin?forum=SP2016) but I don't know which action I should take. Thank you for your help.

Does your form have code in it? Or did you maybe add code accidentally?