on 05-20-2015 8:43 AM
Hi Experts,
We have configured Archive link property in services for object using OAC0,OAC2
and OAC3 transaction ME51n,ME52n & ME53n.
AS its construction Industry,There are many remote construction sites of company.
Document attachment functionality is working properly in Near by location. However same thing
does not work in remote location( Sites with low connectivity ).
It is ending up with the message "RFC desintation SAPHTTP inaccessible: Timeout during allocate".
Can we increase the allocate time while attaching ? If we can, kindly tel me the procedure.
Or is there any other solution ?
The SAPHTTP is an RFC destination pointing to the saphttp.exe file on your front end PC.
Could you please send me screenshot from the command saphttp -V from the workstation where it doesn't work. You can find the saphttp.exe in the SAP GUI installation folder.
And you can create a detailed trace from the SAPHTTP RFC destination as described in note #1947876 and #317250. (Please use the report RSHTTP40.)
You can also try to delete the SAPHTTP and SAPHTTPA destinatins in SM59 and then regenerate them with the report RSHTTP05.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Janos,
I have this same requirement of storing the Quality Incoming Certificates in Content server , i tried to use this Store Business document in QC51 and received this same "RFC destination SAPHTTP inaccessbile" error.
I am not sure if this method will store the certificates in content server directly or not.
Hope you can help in this
Thanks
Benny
Hi Nice,
Try implement this note "Drag and drop issue note 1931683 ". This also gives you an time out error issue when document are uploaded from archive link.
Rgds,
Nayeem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nice,
I think you need to find the root cause of the time out to fix the problem. If it slow connection, you change the timeout from the below screen shot.
2) check if not the content repository is NOT full or reached the threshold level
3) When you are trying to store, ping the server ip (10.100.11.52) from the same machine to see any drop in the connection
4) (my blind guess : ) )There is change in the SAP_CODEPAGE = 4110 to 1160. May be you need to change the kernel level.
5) Check if the even log gives some clue.
6) Check the CPIC trace file for some clue.
The reasons are more situational … you need to keep searching for a clue.
Let us know if it is fixed .
Thanks,
Kolusu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In Windows you can use the SAPHTTP_TIMEOUT environment variable to set the value externally
(in seconds).
For more info please check note 319266.
Best regards,
Janos
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAPHTTP_TIMEOUT are environmental variables. For example on Windows you can set it like described here How to set the path in Microsoft Windows.
For the 1st: please create the trace as described in note 1947876.
And also pelase make sure what timeout is maintained on the IIS (Apache) etc on your content server solution side.
from the trace I cannot see the tiemout error, but what I could find that from kernel 720 you're using patch level 10 of saphttp, but the newest is 23.
on the other hand if you experience issues with saphttp on your frontend, then please make sure that you trace the SAPHTTP RFC destination and not the SAPHTTPA.
SAPHTTPA is for the saphttp running on the applicaiton server, and SAPHTTP is the RFC destination for the saphttp on the frontend server. you have to create the trace on that PC in which you experience the issue.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
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.