Failure on Windows Application Forms Designer 3.1.4

Discussions about Forms Designer for SharePoint 2013 / 2016 and Office 365.
Locked
grindgod
Posts: 4
Joined: Tue May 29, 2018

29 May 2018

I have the Problem, when I try to design a form via the Windows application I get an error like:

"Unable to retrieve the supported Version number....
The HTTP request is unauthorised with client authentication scheme 'ntlm'."

We use latest Version of server-side-components and the latest version of Forms Designer 3.1.4. The Silverlight Plugin let me use it without this problem. We already did an IIS-Reset and we already had a weekend :D .

Is there any idea about that problem?

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

29 May 2018

Dear grindgod,
The issue is connected to authentication, what are your settings in the desktop version?
LoginDifferentAuth.png
LoginDifferentAuth.png (16.29 KiB) Viewed 2018 times
Please, try to use different authentication methods and do not select Login as the current Windows user. Finally, if this doesn't work for your account, try a different login, preferably one with domain name.
Cheers

grindgod
Posts: 4
Joined: Tue May 29, 2018

29 May 2018

Hello Mr. Kurguzov,

thanks for your reply.
I've tried different users, different authentication methods, with and without domain name, different machines. Nothing was successful. Any other ideas?

cheerz

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

29 May 2018

Dear grindgod,
Can you tell us about the authentication settings for your SharePoint? Is it Forms authentication, Kerberos, something else?
Cheers

grindgod
Posts: 4
Joined: Tue May 29, 2018

29 May 2018

We use Kerberos for authentication. Before we bought the product, we tested the functionalities in our integration environment and of course we used the Forms Designer 3.1.4. There was no problem. After installing the license and so on in our productive SharePoint we got this problem. Both environments are configured the same.

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

29 May 2018

Dear grindgod,
The license installation definitely is not connected to it. Please, double check the configuration to make sure that it's absolutely the same, there is likely to be at least some difference causing it. If possible, try to disable NTLM, only as a test.
Cheers

grindgod
Posts: 4
Joined: Tue May 29, 2018

04 Jun 2018

Hey Mr. Kurguzov,

I'm sorry but we don't have the possibility to disable NTLM. What can we do to reconnect the license, or just connect it correctly?!

kind regards

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

04 Jun 2018

Dear grindgod,
No, what I mean by not connected to license - it's not related to it, it's only a problem of user authentication, not connected (related) to a license at all. I would recommend searching for the potential answers Online, there must be something with configuration that causes the error - we just can't be sure what exactly as we don't know all the details.

Here are some of the potential answers:
https://stackoverflow.com/questions/127 ... cheme-ntlm
https://stackoverflow.com/questions/137 ... ntlm-the-a
Cheers

ragesoft
Posts: 50
Joined: Fri Feb 23, 2018

15 Jun 2018

Hi there!

In the formdesinger config file, there is a entry for the endpoint connection:
<transport clientCredentialType="Ntlm" />

Changing this to (3 times):
<transport clientCredentialType="Windows" />

solved the problem!

Locked
  • Information
  • Who is online

    Users browsing this forum: No registered users and 23 guests