SQL Network Interfaces, error: 25 - Connection string is not

ckndr47 · 2009-04-02

I had Nav 2009 installed on my machine.
Have uninstalled everything and reinstalled Nav 09.

I am getting following error when i am trying to open it:

'The Microsoft Dynamics Server cannot connect the Change Listener to SQL server due to the following error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid).

stryk · 2009-04-03

Hi,

well, when you open NAV 2009 - Classic Client, I suppose - and log on to the SQL Server you are doing this with your "Windows Login". This Login has to be defined/setup in SQL Server properly or must belog to the "Administrator" group.
If you have already configured Logins in NAV you must assure those are setup on SQL Server site.

(Same goes for the Service Tier, the service must run with an account which is setup on SQL site to log on)

Regards,
Jörg

ckndr47 · 2009-04-03

Thanks, stryk.
My user was not part of administrator group.

ckndr47 · 2009-04-03

One more thing i forgot to mention, make sure that the "Log On As" for Microsoft Dynamics Nav Server in services is local system account (admin preferred). If it is any other account then again make sure you have admin rights under sql for that account.

Thanks

Dosihris · 2010-04-11

Hi,

i have the same problem. But my user is in the administrator group. What do i really have to do? And do you mea windows users and groups or database users and groups? I have windows authentification too.

And by the way. Is it really right to solve such a problem to add anything to the administrator group? Aren't there better ways??

Nico

stryk · 2010-04-12

Dosihris wrote:

And by the way. Is it really right to solve such a problem to add anything to the administrator group? Aren't there better ways??

No, the "Administrator Group" thing should only apply to administrators and is surely NOT the standard proceeding.
"Standard" proceeding - as described in "Installation & System Management (SQL)" - could be like this:
- Create SQL Server "Login" for the Windows Account (User or Group); only "Server-Role" required is "public"
- Assign "Login" to the relevant database to create the SQL Server DB "User" there; role "public"
- Add "Windows Login" in NAV, assign NAV roles
- "Synchronize" if using "Enhanced" Security Model

Dosihris · 2010-04-12

Well, i still get this error 25 - Connection string is not valid.

What i have.
- Checked that my server accepts remote connections
- Added new Login for my user
- Set serverrole to public, like stryk wrote
- Opend classic client and added my windows user (The Windows user of my local system is Barechen/Nic, but on the server its ATM/Nic. Could that be the problem?
- After that i synchronized the user.

But when i open the role tailored client i get still this error. It seems that he can not connect to the server. i checked the TCP-Settings and activated and enabled the TCP-Connection. Do i have to make an entry in the firewall for the TCP-Port? The TCP-Port seems to be 1433. Thats another one than the Dynamics Service wanted (7046)..

I also tried to start the RTC in administrator mode, but that wasn't the problem... :-(

rrvanzyl · 2012-02-28

Dosihris, were you able to resolve your issue? I am having the same problem now...

Peter_Wibeck_[MSFT] · 2012-03-02

If SQL server is on other machine then the NST, then you need to open up firewall for SQL server (default port 1433). You also need to ensure that SQL serve have TCP/IP enabled (not needed if NST is on the same box).

SQL Network Interfaces, error: 25 - Connection string is not

Comments

Categories