cancel
Showing results for 
Search instead for 
Did you mean: 

JCO_ERROR_SERVER_STARTUP

Former Member
0 Kudos

Hi Experts,

I got the below error for the RFC sender adapter,

Error: 2008-10-01 16:05:39 CDT: com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Sat Oct 01 16:05:39 CDT 2008.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems.

Will try next startup in 256 seconds.

And on searching SDN found that to resolve the issue we need to maintain the IP of R/3 instead of GWHost (gateway host).

can you please explain the reason of doing so. and also do we need to change both in the RFC destination (of type T) created in R/3 and RFC sender channel in XI .

Thanks in advance,

MK

Accepted Solutions (0)

Answers (3)

Answers (3)

SudhirT
Active Contributor
0 Kudos

Hi MK,

Try to change the RFC destination setting from host to IP for this weekend as suggested by dharamveer and lets wait for one more server restart.

Thanks!

Former Member
0 Kudos

Hi Experts,

Can you please explain how can replacing host with IP will solve the issue, as the problem of the channel is reconnecting if ECC is cycled after the XI system is up.

Please suggest further to rersolve the issue.

Thanks,

MK

Former Member
0 Kudos

Hi Experts,

I have changed the host name with the IP of the R/3 in the RFC receiver adapter, but the error still exsists the R/3 has restarted.

Please suggest further reolve the issue or we have raise a defect with SAP.

Thanks,

MK

SudhirT
Active Contributor
0 Kudos

Hi MK,

Better to raise this parallely with SAP. and wait for some more responses in sdn.

thanks!

Former Member
0 Kudos

Hi

Did you checked https://service.sap.com/sap/support/notes/730870 Question 22 in particular.

This can help in understanding

Thanks

Gaurav

dharamveer_gaur2
Active Contributor
0 Kudos

Check last reply of this thread

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

1 You have to provide IP of R-3 instead of GWHost (gateway host).because u r communicating with a particular R/3 and Gateway host can be same for multiple R/3.

2 TCP/IP Connection: TO connect External System.

use this similar thread

These two blogs for sender RFC should help,

Former Member
0 Kudos

Thanks for the reply.

but the problem occurs because when the communication channel in XI system is started, it establishes a connection to R/3. As long as R/3 is up, this connection will be functional. However, R/3 is restarted every Friday night at 16:00 CST to clear SAP buffers and run a backup. When R/3 goes down, this communication channel fails, and is not able to reconnect.

Please explain why the channel is unable to reconnect and how to resolve the issue.

dharamveer_gaur2
Active Contributor
0 Kudos

Hi

Try one thing in RFC Receiver Adaptere Maximum Connections parameter change from 1 to 3.

SudhirT
Active Contributor
0 Kudos

Hi,

This error is seen whenever your R/3 server restarts.It should be temporary error the main cause of this error is your abap instace of server always starts before java instance and this difference of period causes these errors bcoz as soon as abap instance starts the dialogue processes becomes active and starts processing and java instace is still down trying to starts giving JCO_SERVER_STARTUP error.

If this is the temporary error no need to worry after server is completely up this error should be resolved automatically.

Thanks!

Former Member
0 Kudos

Thanks Sudhir for the reply,

But the channel still shows the error even after the server is completely up and running.

because it does not able to reconnect.

Please suggest further to resolve it.

SudhirT
Active Contributor
0 Kudos

Hi,

Goto Visual Admin --> Services --> SAP XI AF Messaging --> Messaging Connection --> increase the poll attempts from 60 to 100 for AFW and then stop your RFC channel from RWB and restart it. May be this can help.

Thanks!

Former Member
0 Kudos

Hi Sudhir,

By restarting the channel the issue gets resolved for the time until the R/3 server is restarted.

Isn't there a permanant solution to resolve the issue, as we restart the R/3 once every week and we have to restart the channel also.

Thanks,

MK