New password for SQL user

[gbelot]

Hello,

this seems to be very simple question, but we can't get it working.

Env: Axapta 3.0 ( 3 tier and 2 tier both working fine)
DB: SQL2000
DB and AOS with application reside on different boxes.

We tried to change password for our default SQL user 'bmssa'. If we change password we can connect to the Axapta DB via ODBC. However, if we start Axapta client (2 tier or 3 tier) we get an error that login for bmssa user failed.

If we change password back to our old password everything works fine.

It almost look like Axapta keeps somewhere an old password and doesn't release it.

Any suggestion is appreciated.
Thanks,
gb

[mazzy]

Use Configuration utility.
Default password is bmssa_pwd.
see screenshot

[gbelot]

We are trying to change password to a new one.

[gbelot]

I just wanted to clarify..

we are trying to change bmssa password to a new one.. and that is when we get an error: "Login for bmssa failed."

As soon as we change password back to the old one, we can start Axapta client.
The question is how release or reset an old password to a new one?

It seems that the issue somewhere on Axapta site, because if I just use ODBC GUI, I can establish connection with Axapta database.

I would appreciate any comments.
Thanks,
gb

[mazzy]

Цитата:

Сообщение от gbelot

we are trying to change bmssa password to a new one.. and that is when we get an error: "Login for bmssa failed."

Are you change password on MS SQL?

[gbelot]

Yes, we are trying to change password for bmssa MS SQL user. As you know, that is a default SQL user account used by Axapta clients.

If it would work as we expected, then we wouldn't have to change anything in Axapta Config Utility. It should pickup default password, as shown on your screen shot above.
But the actual password for bmssa would be new.
However, it doesn't work. We tried to use configuration with default password, tried to specify new password in Config utility. Still not working.

The weird thing is that if I use ODBC GUI I can connect to Axapta database using new password with no problems. That is why I think it is somewhere on Axapta side.
Thanks for keep trying to help.

[mazzy]

Цитата:

Сообщение от gbelot

If it would work as we expected, then we wouldn't have to change anything in Axapta Config Utility. It should pickup default password, as shown on your screen shot above.

No, no, no.
Axapta Config Utility default password is bmssa_pwd always.

IF you use another password for bmssa MS SQL user
THEN enter password in Axapta Config Utility manually

[gbelot]

Yes, we tried that and it didn't work. Any other suggestoins?

[mazzy]

Цитата:

Сообщение от gbelot

Yes, we tried that and it didn't work.

It's strange...

[gbelot]

Here is another strange thing.

I created new SQL account, say bmssa_new, and set password for it.
I created new ODBC profile with bmssa_new. I can connect to my Axapta db and test it successfully.

When I try to open Axapta client using this new account it gives me an error: login failed for bmssa_New.

This is very strange.. I can't believe nobody came across this before.

[mazzy]

It's normal.

IF bmssa is not system administrator
THEN SQL owner of all axapta tables is bmssa (not dmo).

You should change owner of axapta tables, indexes, views and etc...
See http://axapta.mazzy.ru/lib/2db_owner/ (on Russian)

[Junevoful]

Цитата:

Сообщение от gbelot

Here is another strange thing.

I created new SQL account, say bmssa_new, and set password for it.
I created new ODBC profile with bmssa_new. I can connect to my Axapta db and test it successfully.

When I try to open Axapta client using this new account it gives me an error: login failed for bmssa_New.

This is very strange.. I can't believe nobody came across this before.

"Regional and Language Options" go to the "Advanced" tab and change the "Language for non Unicode programs" to an English language.

This should resolve your problem.