on 02-02-2012 2:49 PM
The import was stopped, since an error occurred during the phase
CHECK_REQUIREMENTS, which the Support Package Manager is unable to
resolve without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: CHECK_REQUIREMENTS
- Reason for error: TP_CANNOT_CONNECT_SYSTEM
- Return code: 0232
- Error message: connect failed
Greetings,
This is quite a generic issue while applying SAP patches or upgrading the SPAM...
- Error in phase: CHECK_REQUIREMENTS
- Reason for error: TP_CANNOT_CONNECT_SYSTEM
- Return code: 0232
- Error message: connect failed
As everyone is saying check for R3trans -d and check the trans.log for more informtion and also I would like to ask you to check
Getting "tp connect" to work.
First ensure that tp can connect to the database from the operating system level. Carry out the following steps of action:
login at the operating system level as user <sid>adm
change to directory /usr/sap/trans/bin
verify the correctness of the parameters in the TPPRAM file
test the connection by issuing command "tp connect <SID>"
A tp failure indicates wrong configuration settings in the TPPARAM file or network/database problems.
After a successful "tp connect", test your RFC connection:
login to the R/3 system >> enter transaction SM59 >>select option "RFC destinations -> Internal Connections -> NONE"
click on the button "Test connection"
In case of RFC problems, please refer to the developer traces dev_rfc# and dev_rd which are located in the WORK directory of the application server (transaction ST11). There you will find further information about the RFC failure..
Enjoy !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Please execute R3trans -d. If it fails then review file trans.log. You can find the possible reasons of this issue. I suggest you to check "tp connect to SID" from /usr/sap/trans/bin directory.
Thanks,
Siva Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Above error is common error message on Support packs and hard to provide information with this. Please provide us SLOG* and ALOG* from log directory in trans
Regards,
Arjun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello mutepfe,
In this case, check tp weather it is running or not. generally 232 return code will happen if you have communication or network error.
You can also see tp system log where u will get more clues in resolving your situation.
Post your findings.
Thanks & Regards,
Ananda Swaroop
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
it seems that transport tools cannot connect to your database. From command line on your server please run R3trans -d to test the connection.
There are also test tools within the STMS transaction, click on systems, then your system and then the transport tool tab.
On the left is a test button which checks connectivity of tp and r3trans.
If you face errors post the results here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.