Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
The service could not add service principal names(EVENT 202)
rknabben
Member Posts: 4
my internal domain is in the following format: INTERNAL.COMPANY.COM
the NETBIOS name for the domain is: company (NOT INTERNAL)
However when I view the event log after starting the Service tier, several warnings eventID 202 are logged.
Server Instance: DynamicsNAV
The service could not add service principal names because the service account could not be found in Active Directory.
Account: INTERNAL\NAVSQL-03$
Service Principal names:
http/NAVSQL-03:7047
http/NAVSQL-03.internal.company.com:7047
As you can see NAV assumes my netbios netname is internal instead of company which is wrong.
Is there any way to avoid this potential problem, or at least to let NAV know the correct NETBIOS name?
the NETBIOS name for the domain is: company (NOT INTERNAL)
However when I view the event log after starting the Service tier, several warnings eventID 202 are logged.
Server Instance: DynamicsNAV
The service could not add service principal names because the service account could not be found in Active Directory.
Account: INTERNAL\NAVSQL-03$
Service Principal names:
http/NAVSQL-03:7047
http/NAVSQL-03.internal.company.com:7047
As you can see NAV assumes my netbios netname is internal instead of company which is wrong.
Is there any way to avoid this potential problem, or at least to let NAV know the correct NETBIOS name?
0