Unable to save forms with from client

Discussions about Forms Designer for SharePoint 2013 / 2016 and Office 365.
Locked
Alex
Posts: 32
Joined: Fri Jun 30, 2017

07 Nov 2017

I'm only able to save forms once after opening. The very first save process succeeds, all following not.
The error message I get is:

Code: Select all

System.ServiceModel.CommunicationException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---

Server stack trace: 
   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

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 FormsDesigner.SharePoint.WebServices.IFDService.PublishForms(Guid listId, String contentTypeId, Guid groupId, Forms forms, String layout)
   at FormsDesigner.SharePoint.WebServices.FDServiceClient.PublishForms(Guid listId, String contentTypeId, Guid groupId, Forms forms, String layout)
   at VHNPDwFIlS6CoJyaAR.EU3D29l7DnwwFH4tbM.<>c__DisplayClass27_0.<SetLayoutAsync>b__0()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at VHNPDwFIlS6CoJyaAR.EU3D29l7DnwwFH4tbM.<SetLayoutAsync>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at FormsDesigner.ViewModels.DesignerViewModel.<SaveAsync>d__194.MoveNext()
I have always to export the form, then reconnect with the Form Designer to save it. It's really annoying...

I'm using Forms Designer 3.1.4 with on prem SharePoint 2016
What could be the problem here?

User avatar
Nikita Kurguzov
Posts: 889
Joined: Mon Jul 03, 2017

07 Nov 2017

Hello, Alex!
Hmm, it's possible that you just do not have enough memory on the WFE-server and this causes errors when saving forms. Make sure that all the WFEs have enough free memory, at least more than 5%.
Cheers

Alex
Posts: 32
Joined: Fri Jun 30, 2017

07 Nov 2017

Hi Nikita,
checked that, frontends have about 40% free memory.

Alex
Posts: 32
Joined: Fri Jun 30, 2017

07 Nov 2017

You've brought me to the idea with the frontends, it seems to a issue due to our load balancing. With modified host-file there is no issue.
The active session is probably being switched sometimes to the next frontend after the first save action...

Maybe this could be the problem?

User avatar
Nikita Kurguzov
Posts: 889
Joined: Mon Jul 03, 2017

07 Nov 2017

Yes, that's likely the reason that causes the issue with saving.
Cheers

Locked
  • Information
  • Who is online

    Users browsing this forum: No registered users and 10 guests