Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
WebService Error: The target principal name is incorrect
tfranzen
Member Posts: 25
Hi all,
I've managed to consume a NAV-WebService from NAV when the WebService is running on the same machine as the consumer (means 2 different Services for 2 different databases on my local notebook). Now I try to consume a WebService which is provides from a different machine (but in same domain) and I'm receiving an error "Der Zielprinzipalname ist falsch" (The target principal name is incorrect)
Does anyone have an idea how to solve this?
Thanks
Thomas
I've managed to consume a NAV-WebService from NAV when the WebService is running on the same machine as the consumer (means 2 different Services for 2 different databases on my local notebook). Now I try to consume a WebService which is provides from a different machine (but in same domain) and I'm receiving an error "Der Zielprinzipalname ist falsch" (The target principal name is incorrect)
Does anyone have an idea how to solve this?
Thanks
Thomas
0
Best Answer
-
Optionstfranzen
Member Posts: 25
Hi all,
the solution for my problem was the following:
- Enable "Use NLTM Authentication" in ServerConfiguration (solved the problem with the target principal Name)
- Be aware of NAV using the ServiceUser when using DotNet-Variables with property "RunOnClient" set to No
Greetings
Thomas5
Answers
It has details about this particular issue. Maybe it will help you resolve your issue.
Ishwar Sharma
My Blogs: Dynamics Community Blog | Blogspot
Connect: Google + | Twitter
Anyone here who has a link to and/or can write a really simple explanation on what they do and why?
the solution for my problem was the following:
- Enable "Use NLTM Authentication" in ServerConfiguration (solved the problem with the target principal Name)
- Be aware of NAV using the ServiceUser when using DotNet-Variables with property "RunOnClient" set to No
Greetings
Thomas