Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

BW transport falling and locking user DDIC

Hi Experts,

I am facing below problem

when importing one BW trasport it was falling with below error and it was locking DDIC user , please suggest what need to do

Error

Start of the after-import method RS_ODSO_AFTER_IMPORT for object type(s) ODSO (Activation Mode)

The creation of the export DataSource failed

Name or password is incorrect (repeat lo gon)

Name or password is incorrect (repeat lo gon)

Error when creating the export DataSource and dependent Objects

Error when activating DataStore Object CICRACT2

The creation of the export DataSource failed

Name or password is incorrect (repeat lo gon)

Name or password is incorrect (repeat lo gon)

Error when creating the export DataSource and dependent Objects

Error when activating DataStore Object CICROPP1

The creation of the export DataSource failed

Name or password is incorrect (repeat lo gon)

Name or password is incorrect (repeat lo gon)

Error when creating the export DataSource and dependent Objects

Error when activating DataStore Object CICROPP2

The creation of the export DataSource failed

Password logon no longer possible - too many failed attempts

Password logon no longer possible - too many failed attempts

Error when creating the export DataSource and dependent Objects

Error when resetting DataStore Object CICRACT2 to the active version

The creation of the export DataSource failed

Password logon no longer possible - too many failed attempts

Password logon no longer possible - too many failed attempts

Error when creating the export DataSource and dependent Objects

Error when resetting DataStore Object CICROPP1 to the active version

regards

vamsi

Former Member
replied

Hi,

I just faced the same problem. In order to solve I performend the following actions:

-Unlock DDIC user in specific client

-Go to SM59, RFC -> delete trace (to clean up an already existing trace).

-Perform the transport, the transport will fail again

-Check the RFC trace in SM59 to identify the RFC connection responsable for the locking.

-Log on to client 000 with user DDIC

-Go to SM59 and the specific RFC connection

-Try remote logon: In my situation a logon popup was shown to logon to the specific client (this caused the user to be locked eventually). If the popup is shown then check the RFC destination, tab Logon & Security. Make sure the fields Language, Clientsand User are empty and that the password is initial. Try remote logon again. In my sitiuation the client number and language field were filled in the RFC destination. After removing these the logon popup did not appear and the user was not locked anymore.

After above steps, try to retransport.

Good luck!

Regards,

Bart

3 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question