cancel
Showing results for 
Search instead for 
Did you mean: 

File --> File sceranio problem

Former Member
0 Kudos

I am having some problem in the file-file scenario at the sender file adapter level. Please look at the following message:

2006-01-09 10:23:17 Error Attempt to parse XI system response failed

2006-01-09 10:23:17 Error Transmitting the message to endpoint http://host:port using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: TEXT/HTML.

Accepted Solutions (1)

Accepted Solutions (1)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

- go to SLD - http://server:port/sld

- open business systems (landscape)

- find your integration engine business system

- fill pipeline url : http://server:<b>httpport</b>/sap/xi/engine?type=entry

httport = 8***

if it's correctly filled go to TCODE - SXMB_ADM - integrationn engine configuration and check if your server is configured as HUB with the same url

Regards,

michal

Former Member
0 Kudos

Hi Micheal,

Thanks for your quick reply. I have tried filling the pipeline url with the path you have specified. In integration engibe ADM I have already setup the role of buisness system as HUB and dest://RFCdestination.

I am still getting the exactly same problem. No change.

I have cleared SLD cache. Nothing works. Any more ideas?

Former Member
0 Kudos

Thanks....I have restarted the J2ee server after making changes to SLD busn system and it worked just great.

MichalKrawczyk
Active Contributor
0 Kudos

great!

Regards

michal

dries_guth
Explorer
0 Kudos

Hi Michael and tny,

I have just read the problem description and I have just the same error..

BUT ON the PCK while module developing.

What can I do on the PCK instead?

I have restarted the AFW Core service, the XI Messaging System and afterall the complete J2EE Server.

I have also restarted the CPA Cache, I thought there lies the problem.

Nothing help, even the same problem.

Any ideas, what I can do? (I was a little bit suprised that the CPA Cach refresh via url doesn't work. Maybe here lies the problem.

Any ideas?

Best regards,

Dries

dries_guth
Explorer
0 Kudos

OK, the problem is solved.

The password of the User for the XI Adapter calling the Messaging System or integration engine has been expired. User has a new password and everything works fine.

Answers (0)