Attain 4.0 SP1 user ID and password invalid

jpenn

We recently upgraded a 2.6 version into a 4.0. When the solutions provider upgraded, they did not include the security. Of course I was able to connect to the new SQL DB 4.0 with the sa user and password. I tried again today and it says the user and password i tried is invalid. I know the user name and password is correct because it will not allow me to choose the DB name unless i have a valid user. Any ideas of what could be happening? I even tried to create a login. I cannot get to the security options because they are grayed out as well.

ara3n

Find the user table and add a new record for user sa in enterprise manager.

kine

1) If you can, try to login under windows account with domain admin rights
2) Who is DB_Owner of the database?

DenSter

You should be able to always get into the Navision database with the db_owner account, without even having a database login for it. That's the reason why I always create my dev database with the sa login, so I know I can always get into them. You may not be able to use some of the Navisoin functionality until you have a working login, but at least you can access the database.

kriki

[Topic moved from Navision Attain forum to navision forum]

groover

OK but let's get back to the real problem.
Making everybody DB_OWNER is not what you want to do. [-X If you tell that to your customer, you might be shot right away. Any idea what can be the solution? I have the same problem on BE 4.00 SP2 with update 1, installed on a W2003 server.

ara3n

With 4.0 version the security has changed. If you add a user, you have give them permission and then synchronize their permission with SQL. Tools->security->Synchronize. You don't need to make them DB owner.

DenSter

groover wrote:

OK but let's get back to the real problem.
Making everybody DB_OWNER is not what you want to do. [-X If you tell that to your customer, you might be shot right away. Any idea what can be the solution? I have the same problem on BE 4.00 SP2 with update 1, installed on a W2003 server.

That's not what I said though. I said that you should get in using the db_owner account. By doing that you can get into the database and fix the permissions the right way.