Share
Report
25Dynamics NAV 2016 - Credential Type UserName - user login crashing NAV Service
We have many NAV 2016 Servers working perfectly with Credential Type Windows – all OK...
We then configured a further NAV service for a client for alternative Credential Type UserName (which prompts user for their windows login) the NAV Service crashes every time an attempted client login is made – we have the same problem with Credential Type NavUserPassword even after many attempts!
I have read available info, and help without success, and have tried alternative settings and machines without success. Has anyone else seen this? Any help welcome. Are we missing something obvious?
The service starts fine with healthy logs…
Server instance: NAV2016
'Microsoft Dynamics NAV Service' is listening to requests at net.tcp://navdemo.cbsnav.co.uk:6046/NAV2016/
Server instance: NAV2016
The service has registered service principal names in Active Directory.
Account: CBSNAV\NAVService
Service principal names:
DynamicsNAV/NAVDEMO:6045
DynamicsNAV/NAVDEMO.cbsnav.co.uk:6045
But when we attempt to connect - The service log gets this error… (All logins used have permissions assigned on SQL Server database - just for good measure – although the service is expected to use the service account connection to database – which is separate from the users connection…) (Same user works via Windows client connection)
Server instance: NAV2016
Tenant ID:
User:
Type: System.Data.SqlClient.SqlException
ClientConnectionId: 00000000-0000-0000-0000-000000000000
Class: 20
LineNumber: 0
Number: -1
State: 0
Source: .Net SqlClient Data Provider
ErrorCode: -2146232060
Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
A further error Event Log mentions tenants but these are not in use...
Server instance: NAV2016
Tenant ID: nav-systemapplication
The connection to SQL server could not be established
Database server: NAVDEMO\NAVDEMO
Database name: DemoNAV2016.
Bit more information to confirm...
To test the UserName client login (which prompts user for a windows login) we were careful to update the client config file settings, and the user name used works fine for windows authentication (i.e. is SUPER)….
Each time we changed Credential Type we restarted the service and deleted the client settings here…
-
%APPDATA%\Microsoft\Microsoft Dynamics NAV\90\ClientUserSettings.config
and updated the client settings accordingly here…
-
%PROGRAMDATA%\Microsoft\Microsoft Dynamics NAV\90\ClientUserSettings.config
When attempting to connect we set this key value...
-
key="ClientServicesCredentialType" value="UserName"
And have tried alternative values for these settings to no avail…
-
key="ClientServicesProtectionLevel" value="EncryptAndSign"
-
key="ServicesCertificateValidationEnabled" value="false"
-
key="DnsIdentity" value="NAVDEMO.cbsnav.co.uk"
The NAV Service crashes every time!
Same results on different servers.
It looks like an issue in NAV2016 CU3.
Am I missing something? Has anyone had this working. Any help welcome.
*This post is locked for comments
All responses (
Answers (
