Error Message when logging in on 3 Tier 3 Svr "the remote computer refused the network connection."
engsiong_75
Member Posts: 11
Hi
I have installed NAV 2015 CU10 on 3 different servers. The Database server, Web server and the application server. The strange thing is that the Application Server does not able to be able to detect the SQL server even though it is turned on.
The error message that I get is
"The SQL server is not started.
The database does not exist.
Proper permissions have not been given to the NAV Server Account"
"the remote computer refused the network connection." NativeErrorcode:1225, HResult: -2147467259.
I have checked that my database server. The SQL server allows remote connection to the server. The TCP/IP port is default to 1433. I am able to connect using the ODBC as well as Developer Environment.
Have anyone encountered this error before? Does anyone have any suggestion how to troubleshoot?
Thank you,
I have installed NAV 2015 CU10 on 3 different servers. The Database server, Web server and the application server. The strange thing is that the Application Server does not able to be able to detect the SQL server even though it is turned on.
The error message that I get is
"The SQL server is not started.
The database does not exist.
Proper permissions have not been given to the NAV Server Account"
"the remote computer refused the network connection." NativeErrorcode:1225, HResult: -2147467259.
I have checked that my database server. The SQL server allows remote connection to the server. The TCP/IP port is default to 1433. I am able to connect using the ODBC as well as Developer Environment.
Have anyone encountered this error before? Does anyone have any suggestion how to troubleshoot?
Thank you,
0
Best Answers
-
Let me rephrase the solution.
The IT Admnistrator had set the server so with a short name and a long name. The short name was somehow linked to the SQL server. We were using the long name as the IP address which failed to login to the SQL database from the NAV Application server.
We had to rename the server using the SQL scripts. (See link below:)
https://msdn.microsoft.com/en-us/library/ms143799(v=sql.110).aspx
After renaming the SQL server and checking that the renaming was correct, we could login to the server.5 -
Instructed to reinstall the SQL server. The same error cropped up but this time the server name was correct. Found that the user which starts the NAV Application server needs the View Database State Grant permission as well. Even after checking and restarting the SQL Server, the setting works as fine,
See link below for more exact steps
https://msdn.microsoft.com/en-us/library/hh166150(v=nav.80).aspx5
Answers
-
Hi,
Check These -
1. Is the SQL Port Allowed in Firewall of SQL Server.
2. Does Database Lies in the Default Instance or Named Instance.
Let me know if any queries.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page0 -
And most important, the last point of the error message: Proper permissions have not been given to the NAV Server Account"
Does the NAV server account have db_owner rights on the database?
Cheers
Carsten
==> How To Ask Questions The Smart Way
This post is my own opinion and does not necessarily reflect the opinion or view of my employer.0 -
The Check These -
1. Is the SQL Port Allowed in Firewall of SQL Server.
the Firewall has turned off in both SQL servers and application Server.
2. Does Database Lies in the Default Instance or Named Instance.
Named Instance
Does the NAV server account have db_owner rights on the database?
db_owner rights are given to the Nav database.
@servername. But when we installed using the IP address and the actual long name, the system apparently could not detect the SQL database from the NAV Server.
We had to rename the server using the SQL scripts. (See link below:)
https://msdn.microsoft.com/en-us/library/ms143799(v=sql.110).aspx
Thanks for the assist0 -
Let me rephrase the solution.
The IT Admnistrator had set the server so with a short name and a long name. The short name was somehow linked to the SQL server. We were using the long name as the IP address which failed to login to the SQL database from the NAV Application server.
We had to rename the server using the SQL scripts. (See link below:)
https://msdn.microsoft.com/en-us/library/ms143799(v=sql.110).aspx
After renaming the SQL server and checking that the renaming was correct, we could login to the server.5 -
Instructed to reinstall the SQL server. The same error cropped up but this time the server name was correct. Found that the user which starts the NAV Application server needs the View Database State Grant permission as well. Even after checking and restarting the SQL Server, the setting works as fine,
See link below for more exact steps
https://msdn.microsoft.com/en-us/library/hh166150(v=nav.80).aspx5
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 322 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
