SAP NetWeaver Application Server ABAP 7.4 on SAP MaxDB - default password

[Former Member]

Hello colleagues,

I have deployed this app.server (see subject) on the AWS cloud but unfortunately I cannot log-in. I've tried all known default passwords for SAP* and DDIC with no result. The documentations says - "You specify the master password during instance creation in the SAP Cloud Appliance Library"... It didn't ask me to specify the password ((

Hence, I have a few questions:

- What's the default password and where should I change it;

- How to unlock blocked accounts in SAP instances (SAP* and DDIC are blocked due to lots of failed attempts);

- How I can access the file system (this VM is on Linux), so... Putty???

[former_member270188 · Accepted solution]

Hi,

You can unlock them:

update <schemauser>.usr2 set uflag='0' where bname like 'username what you want to unlock' ;

You can use emergency SAP* user if you are totally lost with the passwords.

Like this:

update <schemauser>.usr2 set bname='SAPP*' where bname like 'SAP*' ;

and you need to change the parameter:

login/no_automatic_user_sapstar  to value of  '0'

If you do these steps you can logon with SAP* user and 'pass' password....

after you finished you should change back login/no_automatic_user_sapstar  to value of '1' in the profile !

Hope this helps,

Krisztian

[Former Member · Accepted solution]

Krisztian, thanks for your reply!

It might be a dumb question, but how to access the virtual machine's file system?

I'm trying to use documentation provided with VM in the cloud and it says to use WinSCP. So, I've entered my IP, and user 'root'. The password is a problem... again. Then, from the documentation I've read "Use the private key (downloaded during the activation of the instance in SAP Cloud Appliance Library) for login with the root user.". Ok, I have it, but WinSCP doesn't accept it (it says it can use only compatible with Putty keys). I'm stuck...

[ventsislav_ivanov2 · Accepted solution]

Hi Aleks,

You need to use the key generated during the instance creation. Mode details you can find in the last point of CAL FAQ:

Best Regards,

Ventsislav

[Former Member · Accepted solution]

Sorry, I found an answer... I had to convert the key first, before usage to make it Putty-compatible )

Here is the nice topic which describes step-by-step procedure:

Connecting to Your Linux Instance from Windows Using PuTTY - Amazon Elastic Compute Cloud