I have installed NAV2009 and am getting the following error when I try to open it.
'The Microsoft Dynamics Server cannot connect the Change Listener to SQL server due to the following error; An error has occurred while establishing a connection to the server. When connecting to the SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to the SQL Server).
I have installed the demo version and the data is attached to a local install of SQL2005 Server.
Has anyone come accross this error?
Thanks
0
Answers
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
Yes, I was only installing the 2009 demo version.
(if you have had that, then maybe there is an old database lying around which it reuses)
Are you running SQL 2005 express or normal?
It sounds to me like a SQL permission problem - you might have an entry in the event log coming from SQL when this happens - maybe that will tell you which user it tries to connect as.
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
The Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server due to the following error: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
I am not sure which SQL Server permissions are restricting to login.
Hemant
MCTS (MB7-841 : NAV 2009 C/SIDE Solution Development)
This help file is located in the "Documentation\Install Guides" folder of the installation cd. The name of the help page is "Configuring Microsoft SQL Server" located in the "Configuring" node.
These steps have to repeated for every database the service tier (the account which is used for it) connects to.
In one case these permissions weren't enough and I just granted the user owner permission. It is only a development system so the security wasn't an issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
Referring to the MS Dynamics NAV2009 Installation and Configuration Help documentation, in the 'Configuring Microsoft Dynamics NAV Server' section - it says:
DatabaseServer: 'Identifies the COMPUTER running the SQL server'
By changing this to the name of the SQL server instance where my demo database was attached, I was able to resolve the issue.
I have a question. I'm new in navision. Now i'm working on 5.0
But i heard Navision 6.0 already using and Nav 2009 is the newest version and it's in the Visual Studio. Am i right? is it true?
It's mean now i can work on navision in visual studio.NET?
best regards
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n