SAP * logon restriction Solution

The previous two days, because of viruses in the system, caused a lot of Windows 7ProgramIt cannot be opened, and SAP is also paralyzed. It is depressing to think about it. Reinstalling Windows 7 is simple, but reinstalling sap will crash. But there is no way to do it. I have to redo it. This time I learned it, and I got a ghost!

After sap is installed, the client-888 is created. The default sap * account password is pass, which is OK. Copy the 000 data. Later, I found that sap * was not logged in even though it could not use pass or 06071992. At the end of the day, I was prompted that I could not log in with a password because I had tried too many errors. Faint ~ Later I found that I was able to log on to 888 using a ddic account, but I found that this account has no permissions and is depressed. The thought must be that the sap * password of 000 has replaced the 888 password.

So I had to log on to the sql2005 Enterprise Manager and find the usr02 table, which contains the login information. Two columns are commonly used: locnt and uflag. Locnt is the table that stores the number of errors, and uflag is used to lock the account. If the value of uflag is not 0, the system cannot log on. If the value of uflag is 0, the system can log on. So I directly update the uflag of the sap * account and reset it to 0. After the sap service is restarted, it is found that the entered wrong password does not prompt to restrict login, but prompts a wrong password.

I was thinking that the 000 system was probably the password I entered when I installed sap, so I tried it and it went in !!!

In this case, you can only create a new user to feel at ease ~ SAP * And ddic are too disturbing!