Error when sending message: 404 not found

[Former Member]

Hi,

New to XI, practicing file to jdbc scenario. File is pickedup from the source folder but nothing appearing on the receiver end ms access database.

In the Component Monitoring, tried sending message manually with all the right info in Integration engine, getting an error message saying:

"Error when sending message : 404 not found"

Also tried in Adapter Engine and the result same.

Before doing this scenario, I tried file - file scenario then also the sender file pickedup from source folder but nothing happend at the receiver end.

Any idea's?? what might be the issue????

Thanks,

Venu.

[Former Member]

Hi,

do you have some other FIle->... scenario which works fine?

Peter

[Former Member]

Hi Peter,

No. FILE - FILE scenario is also same, file is picked up from source folder but nothing appeared on the receiver end.

Thanks,

Venu.

[Former Member]

Thought to mention, in Message and End to End Monitoring nothing being displayed. Coming up with "No process is defined".

Do not know but to me it looks like, sender CC picking up the file but for some reason its not able to find IR or probably it may not even getting upto adpater. Is there any possibility happening like this? If yes, then where should I look at and for what?

Thanks,

Venu.

[Former Member]

It seems like you have wrong system configuration. Adapter engine tries to send a message to wrong target address where IE is not present.

Ask basis to fix it.

Peter

[Former Member]

Hi Peter,

Any ideas, to find where Adapter engine actually sending the message to?

Any more reasons for my problem guys?

Thanks,

Venu.

[Former Member]

Hi Venu,

Please try testing your scenario using http client tool and see what is happening. Are you able to see any message in sxmb_moni?

Thanks

Amit

[Former Member]

Thanks all for your suggestions.

My problem still remain the same. Been through all the suggestions mentioned above, all the settings looked fine. Tried clearing cache, checked http port, tested sending message through Adapter engine in component monitoring, double checked the url, checked adapter framework for number of associations and they are 13.

Everything seems fine but surely Iam missing somthing. Experts please help me out of this.

Thanks in advance,

Venu.

[Former Member]

Hi,

If you are testing sending the message to the Adapter Engine, then the Send Message URL should be like this:

http://<server>:<J2EEport>/MessagingSystem/receive/AFW/XI

Also check that the Adapter Engine is successfully registered in the SLD. To do this, call the Content Maintenance function in the SLD as follows:

http://<sld-host>:<sld-j2ee-port>/sld u2192 Administration u2192 Content Maintenance.

Select XI Adapter Framework.

Thirteen associations have to be registered.

(Source: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2498bf90-0201-0010-4884-83568752...

If you can't find all the associations, then you will have to create the associations manually.

For your error, refer to the following threads:

Please reward points if it helsp

Thanks

Vikranth

[Former Member]

HI,

Error: 404 Not Found

Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404

u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)

u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port

u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system

u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.

Regards

[Former Member]

Hi,

While Testing from the RWB--IE, make sure the following

1) You have given the User & Pwd

2) Selected QOS Exactly Once

3) Check the URL is correctly pointing to the IS or not( http://host:ABAP Port......)

Here you can see the ABAP is correcly mentioned or not in SMICM-goto-services

here u can find the HTTP Port which ABAP port

Regards

Seshagiri

[Former Member]

hi,

go thru the below description:

Error: 404 Not Found

Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404

u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)

u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port

u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system

u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.

regards

chandrakanth

[former_member537867]

Hi Venu,

"404 is a not found error", plz make a check of your URL you're using is correct? do you use the right port? Normally the port is 80<SystemNo>, so rather 8001 than 7001.

Also check in transaction SICF, if the node /sap/xi/adapter_plain has been activated, if not, activate it and try again.

If you are testing sending the message to the Adapter Engine, then the Send Message URL should be like this:

http://<server>:<J2EEport>/MessagingSystem/receive/AFW/XI

For your error, refer to the following threads:

Also check that the Adapter Engine is successfully registered in the SLD. To do this, call the Content Maintenance function in the SLD as follows:

http://<sld-host>:<sld-j2ee-port>/sld u2192 Administration u2192 Content Maintenance.

Select XI Adapter Framework.

Thirteen associations have to be registered.

(Source: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2498bf90-0201-0010-4884-83568752...

If you can't find all the associations, then you will have to create the associations manually.

This is a very good blog which answers ur question:

check this weblog

https://weblogs.sdn.sap.com/pub/wlg/4061?page=last&x-showcontent=off [original link is broken] [original link is broken] [original link is broken]

Regards,

Vinod.