Turning on ServicesUseNTLMAuthentication on BC23, brakes running NavAdminTool scripts.

microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.

MIT License

733 stars 243 forks source link

Turning on ServicesUseNTLMAuthentication on BC23, brakes running NavAdminTool scripts. #7541

Closed HegedusZsolt closed 5 months ago

HegedusZsolt commented 11 months ago

Enabling ServicesUseNTLMAuthentication property on a newly installed, CRONUS based BC23 instance, makes NavAdminTool based scripts, like Export-NAVServerLicenseInformation, unusable.

The following message comes: Export-NAVServerLicenseInformation : There was no endpoint listening at http://localhost:7086/BC230/ManagementServicePs/Service.svc that could accept the message. This is often c aused by an incorrect address or SOAP action. See InnerException, if present, for more details.

It is working with disabled ServicesUseNTLMAuthentication property and also working in all previous versions (including BC22) with enabled property.

Is it a bug or is it a limitation in BC23?

MarvinWagner-BSS commented 9 months ago

I can confirm the issue in BC23.

Simplest way to reproduce: Set-NavServerConfiguration -ServerInstance BC230 -KeyName "ServicesUseNTLMAuthentication" -KeyValue true Restart-NAVServerInstance -ServerInstance BC230 Set-NavServerConfiguration -ServerInstance BC230 -KeyName "ServicesUseNTLMAuthentication" -KeyValue false

The admin shell's connection to the service stops working after the service restart and you have to disable NTLM manually in the service config file to make it work again. Its a platform issue and not AL I guess.. Anyway I'm hoping for a fix too.

ralf-escher commented 6 months ago

I have the same issue. Upgrade from BC23, RTM to BC23, CU5 solved the problem for our database.

thloke commented 5 months ago

Hi, this issue is out of scope of for this repository. You should do one of the following:

Open a support request to CSS through the PartnerSource portal
Open a bug in Collaborate
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

As a reminder, this repository only handles issues to do with the compiler or VSCode development experience for AL.