Unable to retrieve the supported version number

[karl.lehnert]

I am having 2 issues with our new installation of Forms Designer on SharePoint 2016 on premises.

Firstly, I can only edit forms with Silverlight, the app returns the error.
Unable to retrieve the supported version number
The HTTP request is unauthorised with client authentication scheme 'ntlm'.
FYI our site is configured for Kerberos and SAML.

Also, we have 8 Forms designer icons in the SharePoint ribbon.

Thanks

[Dmitry Kozlov]

Hi Karl,
You should upgrade the server-side component. Download the solution from our website:
http://spform.com/download

After finishing the wizard steps, reactivate Forms Designer feature at the site collection level (de-activate and activate it again). Please, note that after upgrading between major versions (from 2.x to 3.x), you will also have to re-save each custom form in the new designer.

Also, if you purchased a license more than a year ago, you should also purchase a yearly maintainance:
https://spform.com/buy/support-maintenance

[karl.lehnert]

I am already running 3.1.3 and we only purchased the product less than 1 month ago.

I tried downloading as per your recommendation, then doing a repair, I still have 8 x forms designer icons on my SP2013 ribbon (not the new 2016 ribbon) and I get the same error when using the app... ?

[Dmitry Kozlov]

Have you ever installed Forms Designer before? Did you get 8 buttons right after installing? Please, try to de-activate Forms Designer feature - do the buttons disappear?

If the SAML authentication is configured correctly, Windows authentication option in Forms Designer should work fine. If you cannot manage the authentication issue, try to enable basic authentication in addition to Kerberos and use it for designing forms. Then when all forms are ready, de-activate the basic authentication.

[karl.lehnert]

Hi Dmitry,
Firstly, no this is our first on-prem forms designer installation. We have migrated the site from Office365 and this is still in process. The installation of forms designer was pretty straight forward and I don't remember seeing 8 forms designer buttons when it was first migrated but SharePoint was upgraded to that latest patch level this week and the site migrated again.

As for the authentication, it is working as expected both through the browser and also with other applications like SharePoint Designer, ShareGate and file explorer. Authentication is also working with all the browsers we have tried IE, Chrome, and Firefox. Both claims and SAML authentication has been tested and working, I have tried both basic and windows authentication with forms designer. It appears to read the list of libraries and the error is presented upon attempting to open the form. "Unable to retrieve the supported version number".

To answer your question, I deactivated the feature in Site Collection Features and the 8 fd icons disappeared ie no fd icons at all.

UPDATE: I was able to authenticate using DOMAIN\USER instead of user@domain.com.

[Dmitry Kozlov]

What about other lists, sites, site collections - do you see 8 buttons there too?

After enabling basic authentication, pick the corresponding option in Forms Designer's Login dialog:

BasicAuth.png (2.34 KiB) Viewed 2606 times

[karl.lehnert]

I have created another site collection from a SharePoint template and the problem is not apparent there. The site collection with the issue has been migrated from SharePoint online with office 365 version of fd. Is it possible some of the items which were copied could have caused this, are there any files I should clear out of the newly migrated site or investigate?

[karl.lehnert]

Strangely its fixed itself, sorry to waste your time.

[GregReno]

I just started getting the error this morning.

Error: Unable to retrieve the supported version number

As far as I know everything is ok. Yesterday it was working great. Today not so great. Completed 2 forms yesterday.
Using version 3.1.3
It does not work on any form even the forms I created yesterday. Nor does it work on the server or 2 other test machines.

I hope mine resolves it self soon. I have a lot of forms to maintain. All on premise and never 365.


It can not activate "FDService.svc"


Any thoughts.


System.ServiceModel.ServiceActivationException: The requested service, 'https://site/sites/hopestudies/crfs/_vt ... ervice.svc' could not be activated. See the server's diagnostic trace logs for more information.

Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
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.GetSupportedClientVersion()
at FormsDesigner.SharePoint.WebServices.FDServiceClient.GetSupportedClientVersion()
at KIoLRktD2MkBKHBAQc.UxfS1SvN7OTRAtkhlO.<>c__DisplayClass36_0.<GetSupportedClientVersionAsync>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 KIoLRktD2MkBKHBAQc.UxfS1SvN7OTRAtkhlO.<GetSupportedClientVersionAsync>d__36.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.<CheckVersionAsync>d__176.MoveNext()

[Dmitry Kozlov]

Most likely, you just do not have enough memory on the WFE-server, so that all SharePoint services have stopped working. Please, try to run IISRESET and try again. Check the memory.