Skip to Content
avatar image
Former Member

Property "sap_xiadapterservice.adapterType" not found

Hi,

We are trying to send proxy message from WAS640 to MQ via XI 3.0 (JMS Adapter). The message fails in XI and we get the follwoing error messages:

<Trace level="1" type="T">exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist</Trace>

<SAP:AdditionalText>Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.<SID>.<dbhost></SAP:Stack>

All caches are refreshed, Adapter Framework is registed in SLD, in SLD log file you could see that the data that SLD sends to client as a response to its request for AdapterEngine object includes field "AdapterType" with value "JMS".

Have anyone experienced the same problem and can help me?

Thanks a lot,

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Aug 02, 2005 at 07:24 PM

    Hi Anna,

    Check if these links help

    /message/574452#574452 [original link is broken]

    rfc-adapter-aedetailsgeterror-no-adapter-engine

    srfcadapter-and-file-adapter-with-error-no-adapter

    error-at-outbound-adapter

    Regards

    Vishnu

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 03, 2005 at 08:02 AM

    Hello Anna,

    I don´t want to disappoint you!

    Do you work with XI 3.0 in SP12?

    I have a similar problem (same error message!) in RFC and file adapter. here is the heading line of my posting:

    "sRFC-adapter and file adapter with error: no adapter found"

    The answers how to solve that were unfortuantely w/o any effect. Now we are waiting for answer from an OSS call.

    Best regards

    Dirk

    Message was edited by: Dirk Meinhard

    Message was edited by: Dirk Meinhard

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 03, 2005 at 11:14 AM

    Hello,

    I got information about that problem from Yoad in my own thread:

    That´s his answer:

    -

    -


    Yoads answer -

    -


    The problem was really with CIM version 1.4..

    The actual reason is that all Properties of CIM classes in the SLD when using the CIM content 1.4 (can be checked in SLD -> Administration -> Details -> Data) are for some reason capitalized in their first letter not like in some properties in CIM 1.3.

    (Please note that if you imported CIM 1.3 (with the small letters) and only then the 1.4 - you will not get the error becuse for some reason it doesn't override the previous entries.)

    Talking specific about our problem - The class "SAP_XIAdapterService" has a property named "AdapterType".

    In CIM 1.3 it appears as "adapterType" (notice the small a). In CIM 1.4 it appears as "AdapterType".

    Now, the ABAP code that get's the Adapters meta data from the SLD (Including Adapter Types) is still looking for "adpaterType" with small a.

    Look in Function module "SAI_AE_DETAILS_GET" in line 241 and you will see:

    -

    -


    property_value = sap_xi_adapter_service->get_property( 'adapterType' ).

    -

    -


    Of course - to fix the problem a repair must be made to this hard coded value - that will solve this specific problem.

    I will post that data to SAP so they can hand out a note to fix it permanently or maybe they will adjust the CIM - what ever...

    P.S some other properties have the same problem (like "purpose" under XIRemoteAdminService) but i guess they are not as critical as Adapter Type...

    Hope i helped you guys.

    for more question - i can be reached at yoadsn@gmail.com

    -

    -


    Yoads answer end -

    -


    Hope this will help you!

    Best regards

    Dirk

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi

      If you are at SP15, then there are two options for solving this

      1. Patch it up tp SP16 or higher, the problem will be solved.

      2.But for some reason if u want the system to reamin at SP15, then you need to install XI(SR1),configure it (which means configuring XI 3.0 SP9) and the patching it up to SP15.

      We faced this problem yesterday and now we are doing the second way as the server needs to be at SP15.

      Hope it solves your problem as it has solved ours 😊

      Regards

      Sunita