I have created some webservices which works perfectly on my computer when calling localhost:7047 from either browser og Visual Studio. Everything is as it is suppose to. Locally it is running on a SQL server with database name "Demo Database NAV (6-0)". I could not see that would change anything when developing.
But now the problem appears. I have made a full backup from Nav2009, and restored it on the actual server. The database name on the server is "NavDB". Everything works perfectly in Nav2009, but when I want to call my webservice in a browser ("http://localhost:7047/DynamicsNAV/WS/Companyname/Services")
to see if the connection is up and running (I have checked that the service on the server is started), then I get an error message which says:
<faultstring xml:lang="en-US">The Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server due to the following error: Cannot open database "Demo Database NAV (6-0)" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.</faultstring>
Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server due to the following error: Cannot open database "Demo Database NAV (6-0)" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.</string>
First of all I do not understand why I get a response that the database "Demo Database NAV (6-0)" is not available. This database never existed on that server. How do I change the code such that it looks for "NavDB" instead of this default database.
Secondly it seems that the problem has to do with some security rights at the SQL server. I am running SQL Server 2008. How can I change the security so that the webservice is allowed ?? I have tried to adjust the rights, but what works locally at my pc does not work on the server.
I am lost here...
Looking forward to get some response
explains how to get rid of the problem
Group Program Manager, Client
Microsoft Dynamics NAV
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.