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
Intermittent connection with NAV 2009 R2
engsiong75
Member Posts: 143
Hi
I am having a problem in a customer's site. They are on NAV 2009 R2. Periodically they would have problem connecting to Navision. The error message is "The login failed when connecting to the SQL Server [Name of Database server]"
The users will then reboot both the SQL server and NAV server. Then the system will be fine.
The application server is on one server. The database server is on another. I have already done the trusting and the SPN setting for the NAV 2009 R2 server.
I also have the same NAV 2013 R2 running on the same server but using a different port. The NAV 2013 database is residing in the same server but on a different instance.
My question is what can be causing this problem. I have already ruled out the DNS server. (They added another server from an old domain in recently and the Navision failed. But the error message is related to the change listener not like the intermittent error.)
The best part of the story is that the NAV 2013 is running fine.
Thank you,
I am having a problem in a customer's site. They are on NAV 2009 R2. Periodically they would have problem connecting to Navision. The error message is "The login failed when connecting to the SQL Server [Name of Database server]"
The users will then reboot both the SQL server and NAV server. Then the system will be fine.
The application server is on one server. The database server is on another. I have already done the trusting and the SPN setting for the NAV 2009 R2 server.
I also have the same NAV 2013 R2 running on the same server but using a different port. The NAV 2013 database is residing in the same server but on a different instance.
My question is what can be causing this problem. I have already ruled out the DNS server. (They added another server from an old domain in recently and the Navision failed. But the error message is related to the change listener not like the intermittent error.)
The best part of the story is that the NAV 2013 is running fine.
Thank you,
0
Comments
I found that whenever there was this error on the client machine, the database server will produce an information that "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Could not find a login matching the name provided."
I found that the SQL services was starting with the defaulted NT Authority login so I switched it to the domain administrator.
The intermittent problems still persists inspite of the change. However, I cannot find any thing Navision related using the NT AUTHORITY\ANONYMOUS LOGON to start any service or perform any function.
Could you confirm what ports are used by NAV 2009 R2
and what ports are used by NAV 2013.
If it is the same port 7046 that would explain the problem.
It would be also good to doable check what ports are used by the two instances of the SQL server.
Is SQL Browser running ?
Are there any error message in the SQL Server Log ?
I hope this helps.
Could you confirm what ports are used by NAV 2009 R2
and what ports are used by NAV 2013.
Reply: NAV 2009 R2 is using 7146. NAV 2013 is using 70XX. I made sure that there are no conflict with the ports when I installed it.
Are there any error message in the SQL Server Log ?
Reply: Will check it.
Thanks
There is no error surfacing in the SQL server error log.
Thank you,