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,
0
Answers
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 + Page
Does the NAV server account have db_owner rights on the database?
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.
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 assist
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.
See link below for more exact steps
https://msdn.microsoft.com/en-us/library/hh166150(v=nav.80).aspx