Error in phase: ADD_TO_BUFFER in SPAM during import of SAPKB70017 and 18

Question

Hello
What is problem in this case? During import of SAPKB70017 and SAPKB70018 I get following error(there is no SLOG file in /usr/sap/trans/log):
The import was stopped, since an error occurred during the phase
ADD_TO_BUFFER, 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: ADD_TO_BUFFER
    -   Reason for error:
    -   Return code: 0211
    -   Error message:
Notes on phase ADD_TO_BUFFER
In this phase the queue is placed in the transport buffer of your
system. This phases can terminate due to the following reasons:
o   TP_INTERFACE_FAILURE: The tp interface could not be called. There is
     an RFC error.
o   CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be included
     in the transport buffer. The program tp is trying to open a file in
     the file system. For more information, refer to the SLOG log file in
     the directory /usr/sap/trans/log.
A prerequisite of the Support Package Manager is that the Change and
Transport System (CTS) is configured correctly. For more detailed
information, read the online documentation available from Help -> SAP
Library -> mySAP Technology Components -> SAP Web Application Server ->
Change and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.

Answer 1

Hi Jan,
First, check whether your STMS is configured properly. Next check the transport directory and the transport tool from within STMS (system -> check in menu options).
If these 2 are ok, then you might check from within the OS layer by manually adding to buffer (tp add to buffer <Request No> <SID>).
Also, I am assuming you are doing this from client 000 with a non-standard user having proper authorizations.
I believe this to be an issue of permissions at the OS layer.
Regards
Siva