Can't publish to a Form Library for some strange reason. Please help me solve this mystery - InfoPath Dev
in

InfoPath Dev

Can't publish to a Form Library for some strange reason. Please help me solve this mystery

Last post 07-24-2019 08:18 AM by Hilary Stoupa. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 07-22-2019 06:26 AM

    Can't publish to a Form Library for some strange reason. Please help me solve this mystery

    I'm trying to publish to a Form library, but I keep getting this error message... "InfoPath cannot save the following form: https://testNet/teams/ms/MyNewFormLibrary This document library was either renamed for deleted, or network problems are preventing the file from being saved.  If this problem persists, contact your network administrator". I'm not publishing from the same server as SharePoint is located because I've read a few fixes for that scenario.  I'm using InfoPath 2013 and SharePoint 2016.

    Please note that I'm able to publish to a List, without any issues.

    I've been working with InfoPath for quite a few years, so this is really stumping me.  I've tried creating the Form Library, then publishing the form to it.  I've tried creating the Form library at the time when publishing, but receive the same error message for both attempts. I've selected "run as Administrator" when opening InfoPath Designer.   I'm the Admin, so I can remote into the server where Central Admin is located.  I tried to make it an admin approved form, but when I try to active the Form Template it says "This form template cannot be activated because it is still being uploaded to the farm. Wait until the form template's status is Ready and try again." This is a test form, so it only has a couple fields. tried to active it a few days later, but received the same message.

    I highly appreciate any help in solving this mystery!  

    Filed under:
  • 07-23-2019 11:44 AM In reply to

    Re: Can't publish to a Form Library for some strange reason. Please help me solve this mystery

    I would try running Fiddler while publishing, finding the publish request / response & see if there is any better info there. Another place to look is your SharePoint ULS logs. Is your SharePoint server up-to-date on patches?
    Hilary Stoupa

  • 07-24-2019 06:30 AM In reply to

    Re: Can't publish to a Form Library for some strange reason. Please help me solve this mystery

    Hi Hilary,

    Thank you so much for taking a peek at this!  All of our server patches are up-to-date. 

    So after some digging I was able to narrow down info from the logs.  The log is very long, but I thought these first 4 lines might provide a clue. On a side note, all of these lines started with "SharePoint Server Distributed Cache Unexpected".  The first line says "Ensure that security permission has been granted for this client account" which might be my best clue.  Does this ring a bell?  I thought I had Full Control everywhere, but could there be somewhere that you could think of that I am missing permissions?  ....or could it be something else?

     

     LINE 1:
    Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedActivityFeedLMTCache' - Exception 'Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.) ---> System.ServiceModel.EndpointNotFoundExcepti...  

     LINE2:
     ...on: Could not connect to net.tcp://xxxsps2:2xxxx/. The connection attempt lasted for a time span of 00:00:00. TCP error code 10061: No connection could be made because the target machine actively refused it 10.1.xx.46:2xxx3.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.1.xx.46:2xxx3     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)     at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)     at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     --- End of inner exception stack trace ---    Server stack trace:      at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     at System.Ser... 

     LINE 3:
    ...viceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)     at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)     at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)     at Microsoft.ApplicationServer.Caching.CacheResolverChannel.Open(TimeSpan timeout)     at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)     at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Exception rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message r... 

     LINE 4:
     ...eqMsg, Boolean bProxyCase)     at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)     at Microsoft.ApplicationServer.Caching.CacheResolverChannel.OpenDelegate.EndInvoke(IAsyncResult result)     at Microsoft.ApplicationServer.Caching.ChannelContainer.Opened(IAsyncResult ar)     --- End of inner exception stack trace ---     at Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ResponseBody respBody, RequestBody reqBody)     at Microsoft.ApplicationServer.Caching.DataCacheFactory.GetCacheProperties(RequestBody request, IClientChannel channel)     at Microsoft.ApplicationServer.Caching.DataCacheFactory.GetCache(String cacheName)     at Microsoft.Office.Server.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'.  

      

     

    Thank you! 

     

  • 07-24-2019 08:18 AM In reply to

    Re: Can't publish to a Form Library for some strange reason. Please help me solve this mystery

    It doesn't - let's try the Fiddler trace approach. You would need to have Fiddler installed on your machine & open while you publish - once publish fails, you can look at the list of the URLs in the left pane of Fiddler for the publish URL - it will likely be red, since publishing failed. Then you could look at the request & response (I can help you with that). Here is a link to info that looks to be the same as the error in your first line: https://blogs.msdn.microsoft.com/brian_farnhill/2014/06/24/exception-microsoft-applicationserver-caching-datacacheexception-errorcodeerrca0017substatuses0006/
    Hilary Stoupa

Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.