cancel
Showing results for 
Search instead for 
Did you mean: 

ICF service node "/sap/public/bc/ur" is not active in SOAMANAGER Tx

Former Member
0 Kudos

Hello.

I have an Issue with ICF, when i try to start SOAMANAGER T-code, the Browser show ths follow page:

---------------------------------

500 SAP Internal Server Error

ERROR: ICF service node "/sap/public/bc/ur" is not active (see SAP Note 517484) (termination: ERROR_MESSAGE_STATE)

---------------------------------

In SICF all /sap/public/bc node is active, but when i try to Test some of this (like /sap/public/ping) the browser try to open in https instead http and shown certificate error, i dont want to use https in this case.

The http, https and smtp services are Running in SMICM.

Please Help!

Thanks & Regards

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Christopher,

Can you please cross check with SICF for service /sap/public/bc/ur by <double clicking> on the service. On the create/change service page you will see if the service is active (to the right of Service Name).

Additionally, you could try to deactivate the service and reactivate it.

Let us know how you get on.

Kindest Regards,

Amerjit

Former Member
0 Kudos

Hello Amerjit  Thanks for reply,

the service is active after crosscheck:

I try Deactivate and re-activate service and same issue

Former Member
0 Kudos

Hi Christopher,

Of course that would have been too easy hehehe

Could you provide the following info.

1. Your SAP system version incl SP levels. eg: SAP_BASIS 731 SP05

2. Your current kernel version and patch level.

3. Your ICM parameters from your profile.

You mentioned that when you call a SICF service it defaults to HTTPS. Have you tried calling a service directly ? If you call a service directly via HTTP, does it redirect to HTTPS ?

eg: http://<host>:<ICH HTTP Port>/sap/public/ping

KR,

Amerjit

Former Member
0 Kudos

haha is not too easy.

this is the info:

1. ERP 6.0 EHP 7 SAP_BASIS 7.40 SP06

2. Kernel NUC 7.41 patch 42

3.

Services

icm/server_port[0]             = PROT=HTTP,PORT=8001,PROCTIMEOUT=600,TIMEOUT=120

icm/server_port[1]             = PROT=HTTPS,PORT=8443,PROCTIMEOUT=50000,TIMEOUT=50000

icm/server_port[2]             = PROT=SMTP,PORT=25000,TIMEOUT=180

When I try to access /public/ping with http in a browser shown the follow page:

=(

Former Member
0 Kudos

So if I do a quick summary:

If you access the ping service with HTTP you get a 403 (and you'll confirm that the service is indeed active).

If you try the ping service with HTTPS (not what you want) you get a certificate error (the cert if self signed).

Is your install a fresh install or was the system upgraded to ERP6 EHP7-SP06 or is it a system copy ?

Whilst I scratch my head, could you try the following:

/nSE38 => SIAC_PUBLISH_ALL_INTERNAL

The above will publish all services to the internal ITS. Please try the HTTP ping again after the publishing has finished.

KR,

Amerjit

Former Member
0 Kudos

After run this report, the issue is the same.

This is our DEV enviroment. thi issue start last week, Really i don´t know if some changes where made in Soamanager or ICM parameters, but with this same patch and kernel level, in our QAS env, all works fine.

former_member199290
Participant
0 Kudos

Hi Christopher:

Please check this note if this is helpful for restricting the service from switching to HTTPS.

1789344 - How to disable HTTP -> HTTPS switch for an ICF
service

Thanks.

Former Member
0 Kudos

Hi Christpoher,

With the ping not working I'd be surprised if the changes were made in the SOAMANAGER.

Could post all the icm/* parameters from your profile as I mentioned above.

Now your problem seems to affect all services so I have the suspicion that if a change was made (other than parameters) then it was at default_host / virtual host level.

If you suspect a change was made with SICF then please check table E071 and search for:

Request/Task: <your SID>*

Program ID: R3TR

Object Type: SICF

The above will pick up any transports that would have been created if a change was made to SICF.

Cheers,

Amerjit

Former Member
0 Kudos

I WIll check Transport Orders Table.

here is alll icm parameters in attached file.

Former Member
0 Kudos

Christopher,

Whilst you're at it, could you also upload your dev_icm file. It will also help others who want to try and help.

Cheers,

A.

Former Member
0 Kudos

Sure.

the follow is the dev_icm log with 3 level of trace and trying to open SOAMANAGER T_code events:

cris_hansen
Advisor
Advisor
0 Kudos

Hi Christopher,

Usually the 403 error message means that the service is not activated in SICF.

Have you checked the path /sap/public/ping?

You should also use a traffic sniffer tool, e.g. Fiddler, and see the nodes that are facing 403 HTTP error messages - then check in SICF for them (all must be activated).

Not related to the issue you are facing, I recommend using kernel 7.42, as kernel 7.41 is about to be deprecated.

Cheers,

Cris