Login failed when connecting to SQL with database login

fgudelj

Hi,
I've a problem and need your help.

I've install the SQL2008 R2 and the NAV2009 (both classic sql and RTC). Cronus database is working fine: it connects and opens even the RTC without problems.

Now, we've done NAV 4.0 SP3 upgrade which already had database in SQL. When I tryed to open the database in classic NAV this is what happened:

- with Database Authentication: "The login failed when connecting to SQL Server NAMEINSTANCE"
- with Windows Authentication: everything was ok.

Please, could you help me with this problem?

I've also tried to restore databse with SQL user, setup new users and roles, deleted and recreated old roles and nothing worked.
For some sceptics I've synced logins everytime I made login modifications and reenetered NAV classic client.



Wait for your help...

Filip

fgudelj

I found one issue in end-user licence which could be root of my problemsm, and it is related to codeunit 5150 "Integration Management".
I compared my developer licence (has this codeunit), and end-user licence (doesn't have this codeunit).

I'm a little confused because this codeunit should be available in end-user licence because it is root NAV 2009 functionality, or it shouldn't be available....?

pdj

I think it is unlikely it has anything to do with this codeunit.
Can you login in SSMS using the Database Login credentials?
No: Is the SQL Server in Mixed Mode? (and has been restarted after it was changed?)
Yes: Have you tried Syncronizing Security when logged in with a Windows user?

fgudelj

Yes I can login in SMSS with DB login, and I've also tried syncronizing logins.. Always get same result..
And I've also tried closing and opening NAV client after each syncronization, and also no success..

kriki

You are using a named instance of SQL server.
Try these:
-enable the SQL server browser service.
-instead of the name of the server, try to use its IP address + port on which this named server is listening (something like:10.1.1.15:1427)

fgudelj

Unfortunently, I'm not using named instance of SQL server.

But I've solved issue by removing logins (manualy) from SQL, creating them with assigned User mapping and after that syncronizing NAV users.