Small and medium business | Business Central, N...

Business Central 24.2 on-premise protocol mismatch between the client and the server.

(1) Share

Report

Posted on by KL-13060704-0

Hi Everyone,
I meet the below error message when Business Central 24.2 on premise manual create a new instance and try to access.
I had check all the port and credential are correct.
Is it a bug on the Business Central 24 version?
When use the below script at Business Central 23 version didn't have any issue.

Categories:

Dynamics 365 Business Central

All responses (10)

Answers (0)

F.Steiner 2 on at

Like (0)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hello guys

Run your ps-command with parameter -PublishFolder

New-NAVWebServerInstance -WebServerInstance $ServerInstance -Server Localhost -ServerInstance $ServerInstance -ClientServicesPort $CPort -ManagementServicesPort $MPort -ClientServicesCredentialType NavUserPassword -PublishFolder "C:\Program Files\Microsoft Dynamics 365 Business Central\$($Version)\Web Client\WebPublish"

PublishFolder

Specifies the location of the WebPublish folder that contains the content file that is required for Dynamics NAV Web client.

Default path '%systemroot%\Program Files\Microsoft Dynamics NAV[version number]\Web Client\WebPublish' is not working from version 24, 25, . if you have multiple versions installed on your server
Flanza 16 on at

Like (1)

Report
Business Central 24.2 on-premise protocol mismatch between the client and the server.

Guys, I know that usually the "protocol mismatch" error is due to the difference in ClientServicesCredentialType between the service instance and the webservice instance, but this case is different and I will show you something more.

First of all, to replicate this problem you must have a PC or a server with multiple versions of BC installed. It's not important how many versions.

I have tried with 23 + 24 and all the combinations from 14 to 23 + 24.

I show you all the process, so all of you interested in this topic can - I hope - dig a little more, and maybe we find a solution to that.

Try this.

BC240 is correctly installed and the default instance is running and working

The BC240 service ClientServiceCredentialType is “Windows”

I want to create a new WebServerInstance called “CUSTOM24”, linked to the BC240 Service

I Open the Administration shell version 24

Creation of a new WebServerInstance

New-NAVWebServerInstance -Server localhost -ServerInstance BC240 -WebServerInstance CUSTOM24 -ClientServicesCredentialType Windows -ClientServicesPort 7085 -ManagementServicesPort 7045

(Notice that the Administration Shell is correctly the 24 version and the Windows protocol is the same of the BC240 service)

OK, the Web Server Instance is created by the book, you can think.

The cmdlet command is correct and the administration shell is the right one.

Let’s open http://localhost:8080/CUSTOM24

The error is in Italian, but is “Protocol mismatch between the client and the server”

I did dig it a little more and I noticed this difference:
Let’s go to the BC240 standard Web Server Instance created by the installation process of BC 24

And let’s check the Properties of the file “Microsoft.Dynamics.Framework.UI.dll”:

You can see the Product Version is right.
Not let’s check the same but in the CUSTOM24 Web server instance we just created above:

The Product Version of this DLL is wrong. And it says “14.0.xxxxx” because the lowest version of Business Central in this particular server is 14.
If you have other versione of BC in a server, and you create a Webserver Instance with the 24 Administration Shell, a lot of the files created will always be of the lowest version you have in that server.

This problem exists from version 24.0 and it's still there.

I tried the suggested answer from CU26060549-0 with my heart full of hope, but nothing. It's not working.
Suggested answer

SJ-21081601-0 4 on at

Like (1)

Report
Business Central 24.2 on-premise protocol mismatch between the client and the server.

Run this before New-NAVWebServerInstance and your problems be gone.

Import-Module 'C:\Program Files\Microsoft Dynamics 365 Business Central\240\Web Client\Modules\NAVWebClientManagement\NAVWebClientManagement.psm1'
CU-20080832-10 6 on at

Like (2)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hi there,

if anyone still has this problem. I´ve got the solution.

The hint was to use Get-NavWebServerInstance BC240_Test

This showed 16 instead of 24. So i removed all former BC versions (you can also temporarily remove them), restarted ISE and ran the scripts again. Now it works properly :).

bye

Karsten
Suggested answer

CU26060549-0 on at

Like (2)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hi, You need to chnage the PS file for it to work.
If you navigate to installation media of BC240 that is C:\Program Files\Microsoft Dynamics 365 Business Central\240\Service and search for NAVWeb you encounter two files one that is located in \Service other that is located in \Service\admin.
What you need to do is open the one that is in Service and modify from this

to this:

Then Try again creating the WebServerInstance.

Hope it helps :)
CU26060549-0 on at

Like (0)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

I am also getting the same issue,
Could you please verify the version of newly created Webserver instance
Command:
Get-NavWebServerInstance BC240_Test,

It will also point you to Config file and you can verify the Authentication and Ports on that particular config file.
KL-13060704-0 12 on at

Like (0)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hi Gokulnath,

I had try reinstall several time and double confirm all the port and correct windows authentication.
But still meet the above error message.
I try on different server/local pc also meet this issue.
Tech_BC_Gokul 331 on at

Like (0)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hi

could you please try to reinstall business central with proper steps and ensure business central instances are created with windows authentication and no changes to the web.config file after installation

thanks

gokulnath
KL-13060704-0 12 on at

Like (0)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hi gdrenteria,
Thanks for your reply,
but i'm using ClientServicesCredentialType = Windows and meet the error message.
gdrenteria 14,483 Most Valuable Professional on at

Like (0)

Report

Business Central 24.2 on-premise protocol mismatch between the client and the server.

Hi

I hope this can help you.

"Communication protocol mismatch" Error. (dynamics.com)

Login Error: Communication protocol mismatch between client and server - ArcherPoint

BR

GR