sapcontrol NIECONN_REFUSED

[nicola_blasi]

Good morning

I'm upgrading the EA-FINSERV from 600 to 604 and this activity is like an upgrade using the same tool .

I didn't have problem during the prepare but at the end of this before downtime in phase MAIN_DTTRANS/STOPSAP_TRANS! an error occurs:

Last error code set: Process 'sapcontrol' exited with 1, see '/sapmnt/M1E/tempexp/EHPI/abap/log/SAPehpi.ECO

looking the SAPehpi.ECO i have the error:

**

EXECUTING /usr/sap/M1E/DVEBMGS48/exe/sapcontrol (/usr/sap/M1E/DVEBMGS48/exe/sapcontrol) -prot NI_HTTP -host mo1r3db -nr 48 -function StopWait 10000 10

23.03.2010 07:41:58

Stop

FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()

Process with ID 3913 terminated with status 1

*

Reexecuting the same program on OS Sun Solaris i have the same error:

***

sapcontrol -prot NI_HTTP -nr 48 -host mo1r3db -function StopWait 10000 10

23.03.2010 08:23:27

Stop

FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()

****

I don't understand why and i didn't find any solution ....the system is open now

but i can't go in downtime phase for this error. any workaround or solution? thanks

Nicola

EHP4 FOR SAP ERP 6.0 / NW7.01 on Sun Solaris

Oracle 10.2.0.4 all fixed last patches

kernel 7.01 level 81

[former_member126060 · Accepted solution]

Hi NIcola,

I've also seen this problem many times. for now i'll suggest you to bring down your system manually and retry the phase. It will proceed ahead for sure.

Best Regards

Niraj

[nicola_blasi · Accepted solution]

Thanks Niraji

But it's not so simple....i tried many times in all manners but the problem remains.

I'don't know hot to bypass this problem

thanks

Nicola

[former_member126060 · Accepted solution]

Hi NIcola,

When i faced this problem, i cleanly brought my instance down and then i was able to proceed ahead.

Try this, check if sapstartsrv is up and running for your instance ? if not start it. if it is running then stop it, make a cleanipc run and then start the sapstartsrv again.sometimes it happens that sapcontrol is not able to communicate with the sapstartsrv and this causes the problem.

check and let me know.

Regards

Niraj

[nicola_blasi · Accepted solution]

Hy Niraji

yes the problem was the startsapsrv....it didn't start so i had to do it manually

startsapsrv pf=.......

and the step was passed

thanks

Nicola

[former_member126060 · Accepted solution]

Great .... Cheers !!!

Regards

Niraj

[Former Member · Accepted solution]

I encountered same issue when doing EHP4 applicaiton, did same thing , manually did staqrtsrv pf= , and could bypass the error and continue the upgrad.

Big Thanks.

Theresa

[Former Member]

Hello All,

I have faced similar issue, I could not stop/start the system using standard commands. I've seen that something is not right with sapstartsrv process, afterwards I've stopped hostagent using:

/usr/sap/hostctrl/exe/saphostexec -stop

It seems that it kept/locked sapstartsrv.

Then I could proceed with stop/start the system.

I hope that my solution will help you to solve this issue.

Good luck,

regards,

Karolina

[Former Member]

Hello,

I ran into the same problem during an EHP4 upgrade.

I got around it by patching /usr/sap/<SID>/SYS/exe/run/sapstartsrv.

(I even just took the 701 executable; the system was on a 700 kernel at the time)

- stopsap

- kill sapstartsrv

- cp .../EHPI/abap/exe /usr/sap/<SID>/SYS/exe/run/sapstartsrv

- startsap

- repeat the phase

Regards,

Thomas.

[shouvik]

Thank you Thomas. Your solution worked for me. I had a distributed system where the CI was on a different host than the ASCS. Logging in the ASCS, I proceeded to restart the DB and the instance, and did the same from <SID>ADM in CI, and voila!!

BR,

Shouvik