Q. The NaviEdit installation fails with the error message SQL Server does not exist or access denied. ConnectionOpen (Connect()). How to go ahead?
A. The problem is typically either:
- Insufficient access rights to database files.
- Insufficient access rights to the SQL Server.
- Missing configuration of the SQL Server Network protocols.
To 1: Insufficient access rights to database files
The user can manually try to copy an arbitrary file to the folder where database files should be. The SQL Server should also be able to access the files, this part can be tested from the free SQL Server Management Studio, where you can try to attach a NaviEdit database file. If you don’t have one already you could make a copy (Important!) with a different name of these two files:
Renamed copies could be:
Screenshots from SQL Server Management Studio (free download from Microsoft):
If this fails. Retry after you start SQL Server Management Studio in Run as Administrator mode, or ensure more file access rights are available for the relevant folder.
To 2: Insufficient access rights to the SQL Server
This could typically happen if NaviEdit and/or the SQL Server is installed by another user account than the one currently being logged in and trying to run NaviEdit.
If NaviEdit is installed by another account the two ODBC connections LocalSQLServer and JPAdmin should be recreated for the new user. The current user must also have sufficient access rights on the SQL Server.
Below is shown how a user named StandardUser is granted sysadm rights on the locally installed SQL Server by running the Microsoft SQL Server Management Studio.
Note: When creating new NaviEdit databases locally, two different set of user rights are involved. The current user logged in and the service running the SQL Server, both of these should have adequate rights in the directory where the NaviEdit database are created (default is c:\EIVA\NaviEdit\Database)
To 3: Missing configuration of the SQL Server Network protocols
In the SQL Server Configuration Manager the only enabled Network Configuration protocol should be TCP/IP, the other two should be disabled. The installed SQL Server should per default be installed as MSSQLSERVER