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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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
Best Practices Analyzer selects wrong service
rcverbeek
Member Posts: 32
Hi,
We've installed Navision on a server to use as a two tier solution, so with the SQL database on the same server.
However we also installed a three tier solution on the same machine, with the corresponding database on a seperate server. The extra Dynamics service runs under a newly created domain user and we set up the SPN's according to the MSDN documentation. Also the appropiate SQL Server modifications were made for this user.
The three tier solution however fails to work. When opening the server, SQL server shows the dreaded message "login failed for user nt authority anonymous logon".
I tried to run the BPA, but this seems to select the two tier situation only.
Is there a way to analyze the three tier solution? In other words, is their a way to provide the BPA with which 'instance' to investigate?
Thanks for your reply!
Regards Roeland
We've installed Navision on a server to use as a two tier solution, so with the SQL database on the same server.
However we also installed a three tier solution on the same machine, with the corresponding database on a seperate server. The extra Dynamics service runs under a newly created domain user and we set up the SPN's according to the MSDN documentation. Also the appropiate SQL Server modifications were made for this user.
The three tier solution however fails to work. When opening the server, SQL server shows the dreaded message "login failed for user nt authority anonymous logon".
I tried to run the BPA, but this seems to select the two tier situation only.
Is there a way to analyze the three tier solution? In other words, is their a way to provide the BPA with which 'instance' to investigate?
Thanks for your reply!
Regards Roeland
0
Comments
I would try swapping the config files between instances. You also need to swap over the service accounts if you are using domain users rather than network service.
The next easiest workaround I can think of would be to edit the path stored in the registry to point at your three tier system. There is a key called Image Path at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MicrosoftDynamicsNavServer. I haven't personally tried this, and it is a bit of a hack, so exercise caution and make sure you back up the key you are editing. I know that the service management tools depend on these keys, so if you try this double check which service you are really starting/stopping etc.
If neither of the above work, your only option is to reinstall everything and make sure the instance created by the installer is the three tier instance.
Alex
Thanks for your detailed and expertise reply. Will be testing your suggestions!
Roeland