Login problem

jsinisa

hi,
we are using German version of NAV 4.0 with Windows authentification.
We have one user which username contains special German characert: ö
(f.e. König).

he can normaly login to windows, but to NAV his login failes.
in the list of windows users and groups his username is correct: König, but if I pick his username to put it to windows login's list, name is shown as K÷nig.


is it realy not possible to use special characters (ö,ä,ü,ß) for windows authentifaction in NAV? or there is some workaround?

kine

Fastest will be to change the login name.

Login names with local characters are not good in general.

If you are using SQL server, which collation is using your SQL master DB and which your NAV DB?

jsinisa

I know that changing username is faster, but... I have to obey my manager.

how can I check collation (both, on SQL side and NAV side)?
we are using ms sql 2005.

kine

Just open the SQL Server Management Studio, connect to the server, select the database, click right mouse button and select properties (Master database is inside the "System databases" group)

jsinisa

master DB has (sorting): Latin1_General_CI_AS,
but our Navision DB has: Latin1_General_CS_AS

what can go wrong if I change it to Latin1_General_CI_AS?
should I restart SQL Server?

kine

You can change the collation without problem directly within NAV (File-Database-Alter...). You just needs to switch the DB into single user mode, it means there cannot be any other sessions on the DB during the process. The CS is "Case Sensitive" and CI is "Case Insensitive". I think that this is not the source...

Slawek_Guzek

kine wrote:

You can change the collation without problem directly within NAV (File-Database-Alter...).

I woudn't be so sure thet there will be no problems, especially when he is going to change from CS (Case Sensitive) to CI (Case Insensitive)... Other way arond is definitely much more safe..

Regards,
Slawek

kine

Slawek Guzek wrote:

kine wrote:

You can change the collation without problem directly within NAV (File-Database-Alter...).

I woudn't be so sure thet there will be no problems, especially when he is going to change from CS (Case Sensitive) to CI (Case Insensitive)... Other way around is definitely much more safe..

Regards,
Slawek

Yes, I agree with you. The "without problem" means you can change it "without problems", but it doesn't mean that everything will work in same way after that... ;-)

kriki

[Topic moved from Navision forum to SQL General forum]