NAV18/Docker Debugger (Protocol Mismatch)
maze93
Member Posts: 24
Hi there,
When trying to use debugger from docker installation of NAV2018 (CU6) I am getting an error when trying to access it from development environment:
"Cannot connect to the server because of a protocol mismatch. This can be caused by the client and server having incompatible credential settings (ClientServicesCredentialType). Contact your system administrator. "
When trying from the RTC --> Sessions I get the following message:
"The company name must be specified if the server and instance are specified"
I tried to add ServicesDefaultCompany via the attached powershell prompt but that did not change anything.
Then I tried to change the ClientServicesCredentialType to Username instead of NAVUserPassword. This only made it worse with me unable to open the RTC.
Then I changed back and now I am back at the same issue.
Any suggestions?
Thanks,
Regards from Mattias
When trying to use debugger from docker installation of NAV2018 (CU6) I am getting an error when trying to access it from development environment:
"Cannot connect to the server because of a protocol mismatch. This can be caused by the client and server having incompatible credential settings (ClientServicesCredentialType). Contact your system administrator. "
When trying from the RTC --> Sessions I get the following message:
"The company name must be specified if the server and instance are specified"
I tried to add ServicesDefaultCompany via the attached powershell prompt but that did not change anything.
Then I tried to change the ClientServicesCredentialType to Username instead of NAVUserPassword. This only made it worse with me unable to open the RTC.
Then I changed back and now I am back at the same issue.
Any suggestions?
Thanks,
Regards from Mattias
0
Answers
-
I have the same issue. Any further information about this Issue?0
-
Same for me. Solution someone...?0
-
Same issue here. Did someone found something?0
-
@Maria-S,
HI Maria,
Do not start windows debugger inside developer enviroment.
If you use NAV-Containerhelper to create your container, you should have a shortcut called "XXX WindClient Debugger".
If you are running Docker direct then you can create a shortcut with a correct ClientUserSettings file with the parameter of debug.For help, do not use PM, use forum instead, perhaps other people have the same question, or better answers.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
