cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hi again,

I'm still trying to install Solution Manager 3.2.

The installation procedure said it's higly recommended to change the passwords for user DDIC and user SAP*.

For me, it's absolut normal to choose a password not only containing alphatical chars, but also special chars.

So the password of user DDIC starts with an exclamation point (!).

Now the installation procedure stops at the SAP IGS > RFC Connection.

Entering the password for user DDIC doesn't take any effect. The screen does not change and the log says:

WARNING[E] 2006-04-13 16:41:44 [iaxxrfcimp.cpp:450]

CAbRfcImpl::openRfcConn

Unable to open RFC connection.

I opened my saplogon and created a new connection entry for my sap solution manager server.

I get the standard login screen for sap and tried to login with user DDIC.

If I enter password containing only normal chars, I get the expected error message: wrong username or password.

But if I enter the correct password with the '!' as the first letter, the error message says, I must make an entry in every required field.

I entertain suspicion, that using special chars, especially the exclamation point, is not allowed.

How can I change the password without interrupting the installation process?

I only have three buttons: OK (which isn't working at that moment), Cancel and Logoff.

I don't know what happens, if I click on Cancel or on Logoff.

Maybe I can finish the installation and setup the RFC connection later?

Or the system accepts my inputs and goes on.

Any idea?

0 Likes
View Entire Topic
RiccardoEscher
Contributor
0 Likes

Hello Knud,

funny, I nearly forgot it's existance, but a '!' at the first position in a dynpro field is the so called "Rücknahmebengel" from old R/2 days.. (no, don't ask me for an english translation).

If I remember well, you could reset the content of the dynpro field to it's default with the '!' at the first position, for example if some dnypro check forbiddes a value and you don't want to cancel the transaction. You can test it with a date selection field of some report: insert some wrong value like 'ddddddd', you will get an error message blocking all the transaction; now change the first 'd' with '!' and press enter...

It seems that '!' is not a good choice for the first character of any dynpro field.

Bye

Former Member
0 Likes

The question is where can you trace who unlock it and ran the command at database level.

Any specific file that I should be looking at ? Any place I can find the command history ?