on 05-02-2013 10:41 AM
Hi,
during XPRA I get the following error:
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client "001" started
A2EEFINB_TR 032 No suitable RFC destination could be found"001"
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client "001" finished
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client "010" started
A2EEFINB_TR 042 RFC error with destination "PR010" -> see long text"Upgrade läuft, keine Anmeldung möglich - No login""possible"
A2EEFINB_TR 032 No suitable RFC destination could be found"010"
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client "010" finished
Any ideas how to solve this issue?
Regards, Bernd
Hi all,
the solution was using user DDIC in RFC connections. In addition I had to change the DDIC PW and unlock this user.
Regards, Bernd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I have checked the note and the RFC destianations are maintained in FINB_TR_DEST.
The error is as follows:
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client "001" started
A2EEFINB_TR 042 RFC error with destination "FINBTR@ESBCLNT001" -> see long text"Upgrade läuft, keine Anmeldung möglich - No login""possible"
A2EEFINB_TR 032 No suitable RFC destination could be found"001"
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client "001" finished
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client "010" started
A2EEFINB_TR 042 RFC error with destination "FINBTR@ESBCLNT010" -> see long text"Upgrade läuft, keine Anmeldung möglich - No login""possible"
A2EEFINB_TR 032 No suitable RFC destination could be found"010"
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client "010" finished
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client "011" started
A2EEFINB_TR 042 RFC error with destination "FINBTR@ESBCLNT011" -> see long text"Upgrade läuft, keine Anmeldung möglich - No login""possible"
Any other ideas?
Thanks ahead, Bernd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Check SAP Note:644610. It should help you.
Regards,
Sohrab Kapoor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bernd,
Refer SAP note 644610.
Steps should be
1. Stop the SUM, Update --> Stop Update.
2. Create an RFC (ABAP) destination to each of the clients like what you see above.
3. No need to specify language. You must explicitly indicate the client number, the COMMUNICATIONS (type) USER plus the password.
4. Use transaction FINB_TR_DEST and fill up the entries and SAVE. No need to specify client 000.
5. Restart SUM. Continue with the upgrade using SUM.
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Deepak,
I've already found this blog where you copied the solution:
But it seems (as you can see in the error message above), that it tries to login to the other clients during update via the specified RFCs but cannot login becaus "update is running"...
Any other ideas?
Regards, Bernd
Hi Bernd,
Could you please help with more details regarding the error log. If you can paste the last few logs related to the phase from the log directory. In addition can you please answer below questions:
1. What is your production client.
2. Can you check whether destination PR010 exists in SM59 and do a connection test for the same.
Thanks,
Manas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.