Hi All,
When you try to open Microsoft Dynamics NAV Web client, you get the following error:
A fatal error occurred. The connection to SQL server cannot be established or is no longer usable.
There can be various causes of this error. The most common causes are that Microsoft Dynamics NAV Server has stopped or the connection to SQL Server is not configured correctly.
Resolution :
1) Microsoft Dynamics NAV Server connects to the correct database by using the correct login account. You can verify this by using the Microsoft Dynamics NAV Server Administration tool.
2) Login account has the following permissions:
3) SQL Server has the following configurations:
For more information, see Troubleshooting: SQL Server Connection Problems.
Thanks & Regards,
Nandesh Gowda
When you try to open Microsoft Dynamics NAV Web client, you get the following error:
A fatal error occurred. The connection to SQL server cannot be established or is no longer usable.
There can be various causes of this error. The most common causes are that Microsoft Dynamics NAV Server has stopped or the connection to SQL Server is not configured correctly.
Resolution :
1) Microsoft Dynamics NAV Server connects to the correct database by using the correct login account. You can verify this by using the Microsoft Dynamics NAV Server Administration tool.
2) Login account has the following permissions:
- Permission to log on as a service on the computer that is running SQL Server. For more information, see Provisioning the Microsoft Dynamics NAV Server Account.
- Set up as a user in the Microsoft Dynamics NAV database on SQL Server with the following role memberships: db_datareader, db_datawriter, and db_ddladmin.
3) SQL Server has the following configurations:
- TCP/IP protocol is enabled.
- SQL Server executable file is allowed through the Windows Firewall.
- SQL Server Browser Service is running. This is required only when Microsoft Dynamics NAV used a named database instance, such as NAVDEMO, and Microsoft Dynamics NAV Server is on a different computer than SQL Server.
For more information, see Troubleshooting: SQL Server Connection Problems.
Thanks & Regards,
Nandesh Gowda
No comments:
Post a Comment