ANDREW OLSENJune 3, 2022 at 6:48 amPost count: 10
Any ideas on why I might receive this message? Our PROD environment is behaving as expected, but our TEST environment returns this message when attempting to visit the Shop Floor Insight URL.
<div class=”value”>Failed to communicate with NAV to retrieve employee count licensing info – The HTTP request is unauthorized with client authentication scheme ‘Negotiate’. The authentication header received from the server was ‘NTLM’. – The remote server returned an error: (401) Unauthorized. – (IW.TimeCollectionModule.Common.LicenseException)</div>
</div>Matt BenderJune 3, 2022 at 11:24 amPost count: 1
Having a very similar issue. Working with support to resolve. We are trying to enable SSL Web Services in NAV and are unsure what changes are needed on the SFI Service Authentication settings. If you find a resolution on your own please share – I will do the same.ANDREW OLSENJune 3, 2022 at 11:51 amPost count: 10
Will do Matt. At first glance the broken part of this seems to be on Insight Works side, but unfortunately we’ll be the ones paying for the resolution when they send out the bill. Our sandbox had been up and running for months and unless we had unexpected visitors, we made no configuration changes within NAV to my knowledge. Odd that our TEST environment is hit by this but not PROD. But, that’s better than vice versa! Good luck Matt.Terri VaiveJune 6, 2022 at 8:53 amPost count: 14
The NAV service that is used by the SF service was configured with NTLM on, but the SF service wasn’t configured accordingly. This was correctly set on his PROD instance, but not so for the TEST instance.
The error message mentions that “the authentication header received from the server was ‘NTLM’…“. This tells us the NAV service is configured with NTLM ON but the SF service had issues with that.
If the NAV service is configured like this: (with NTLM on)
Then the Shop Floor Insight service configuration file needs to have the following:
After restarting the Shop Floor Insight service, the SF web client is now functional again.
ANDREW OLSENJune 6, 2022 at 9:21 amPost count: 10
- This reply was modified 5 months, 3 weeks ago by Terri Vaive.
Thank you for the resolution and explanation Terri!
- You must be logged in to reply to this topic.