NAV 2013 SQL restore

Capone

Hi!

I can't manage to restore the backup SQL database that comes with.

Well, I can restore it and can connect with the developer client but I can't connect to it with the RTC client:

"You are not authorized to sign in. Verify that you are using a valid credentials and that you have been set up as a user in Microsoft Dynamics NAV"

It seems like the "hen and egg problem". :-k I need to add the user to connect, but I can't connect because I can't add the user.

Text in the eventviewr:
Service: DynamicsNAV70
User: XXXXXX
Type: Microsoft.Dynamics.Nav.Types.Exceptions.NavInvalidCredentialException
SuppressMessage: False
FatalityScope: None
Message: The server has rejected the client credentials.
StackTrace:
at Microsoft.Dynamics.Nav.Service.NSServiceBase.ValidateAndCreateConnection(ConnectionRequest connectionRequest)
at Microsoft.Dynamics.Nav.Service.NSServiceBase.OpenConnection(ConnectionRequest connectionRequest)
Source: Microsoft.Dynamics.Nav.Service

Egnaz

Have you grant execution rights for the service user in SQL?

For Example:
NAV2013 Service is running under "Local Service" Account
In SQL the "Local Service" Login must have the right to access the database (e.g. sysadmin)

Capone

The DynamicsNAV70 service is run with "Network Service"

The "NT Authority\Network Service" login to the SQL server instance have the right public and sysadmin. The login have also been mapped to the database.

However, the error message I recieve says that my own credentials aren't good enough.
My own credentials to the login is sysadmin and that login is also mapped to the database.

It doesn't feel like a SQL credential error since I can connect to the db with the dev client and not with the rtc client

Capone

Found the problem! #-o

Ordinary we have a primary SQL instance. When the installation was done it created a new instance for the NAV7 db.

What I did was that I restored a db to our primary but the RTC tried to connect to the new instance and of course I hadn't updated the rights on that one.
That explains why I could connect with the dev client and not the rtc...

Jaanu

Hi Capone,
I'm facing the same problem.I created a new database in nav 2013 & I restored a db bkup & created instance for same. When i tried to connect to the new instance, i receive the error

"You are not authorized to sign in. Verify that you are using a valid credentials and that you have been set up as a user in Microsoft Dynamics NAV"

And i have appropriate rights in the server.

](*,).

rathin_mca

Hi,

Go to SSMS , Select the database which you restored --> Right click -->New Query

Execute the below query

delete from [dbo].[User]

delete from [dbo].[Access Control]

delete from [dbo].[User Property]

Check the database permission Weather you have dbowner for that database.

Check you have uploaded the correct licence in database

Restart the NAV SERVER

RTC Should Open - After RTC Open don't forget to add the user name in user setup.

hope it will be useful

Thanx,
Rathin

Jaanu

Hi rathin,
I did it. but now receiving this error


Microsoft Dynamics NAV

---

A fatal error occurred. The connection to SQL server cannot be established or is no longer usable. This can be caused by one of the following reasons:

* The server has been shut down manually or because of an error.
* The SQL server connection settings are not correct
* A network failure has occurred.
* A hardware failure has occurred on the server or on your computer.

Try again later or contact your system administrator.

---

OK

---

](*,)

suraj92291

Restart service of Sql server managment studio(Local).and also restart SQL Server Agent.
make sure that your server instance is running.

ajay_rastogi23

USE [Database Name]
GO
delete from [dbo].[User]
delete from [dbo].[Access Control]
delete from [dbo].[User Property]
delete from [dbo].[Page Data Personalization]
delete from [dbo].[User Default Style Sheet]
delete from [dbo].[User Metadata]
delete from [dbo].[User Personalization]

try this

rathin_mca

Hi,

Change the log on a/c as "Local System"

Restart the service

Regards,
Rathin

Jaanu

Hi All,
Thank you. Problem solved. Started working on Upgrade to NAV 2013 R2.