cancel
Showing results for 
Search instead for 
Did you mean: 

Problem activating HTTP service in ICM

tobiasmarkussen
Explorer
0 Kudos

I was having a problem connecting the NWBC to the SAP URL, and thus i was trying to deactivate/reactivate the HTTP ICM service.

However, now i can't activate the service again. This is what the service overview looks like:

The ICM monitor tracefile gives me this information:

Any ideas how to solve this?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Please check the profile parameter .

icm/server_port_0                           PROT=HTTP,PORT=80$$

Have you set it to 80. as its showing in the service as 80 but in the log its showing as 8000.

Please check the permission of icmbnd in the kernel.

Please also check the port 8000 is free on the server

Run saproot.sh with root to correct the permission.

Note 421359 - ICM: Binding ports < 1024 on Unix

Have you set the parameter mentioned above with this settings.

EXTBIND=1,

what is your kernel patch level.

Thanks

Rishi abrol

tobiasmarkussen
Explorer
0 Kudos

Thanks for your reply. Please note, that it used to be working and active on port 80, so i don't think the server settings or kernel patch levels could be causing problems!?

This is my ICM parameters:

former_member188883
Active Contributor
0 Kudos

Hi Tobias,

Please check in /etc/services which other service is using port 80.

You need to request OS admin guys to free up port 80 on the server for SAP application.

Hope this helps.

Regards,

Deepak Kori

tobiasmarkussen
Explorer
0 Kudos

Thanks for your input Deepak,

However as noted, it has been activated previously. Thus, i don't think there is any conflict problems in using port 80 from a networks perspective!?

Former Member
0 Kudos

Hi,

Kernel will cause an issue if you don't have the permission set properly as the port is less than 1024.

So please check the note mentioned above.

When did it stop working.

Thanks

Rishi abrol

Answers (3)

Answers (3)

tobiasmarkussen
Explorer
0 Kudos

Apparently the issue was caused because IT had made some configuration changes that required a restart.

Thanks for all your inputs!

tobiasmarkussen
Explorer
0 Kudos

When i create a new HTTP service on port 8080 i is active right away. So it might be something with port 80, though no network settings have been changed by me.

Former Member
0 Kudos

Why in first screenshot service name/port = 80 but in trace file PORT=8000? Can you clarify this?

tobiasmarkussen
Explorer
0 Kudos

Sorry, i should have clarified that. The reason why it says 8000 is simply because i tried to change it to 8000 to see if that would help.

Now it's back to 80.

Former Member
0 Kudos

Can you attach full log for analysis?