Error Importing SWCV SAP BASIS 6.40

[Terry_KPMG]

I am configuring a new installation of SAP XI. When we get to the step of installing the SAP BASIS components into the repository we run into the following error:

Tools --> Import Design Objects

XI3_0_SAP_BASIS_6.40_09_00.tpz

<i>Transport Error

Attempt to save object "<b>Adapter Metadata XiConnectivity | HTTP://sap.com/xi/XI</b>"; failed

You can proceed with the transport though objects with errors will be ignored. This may cause inconsistencies in other objects after import. Do you want to proceed.</i>

Points awarded for helpful answers!

[Former Member · Accepted solution]

check the steps as mentioned in note 817920 and then execute the import...

Thanks,

Renjith

[Terry_KPMG · Accepted solution]

Before asking for help, I searched SDN and found references to the "readiness check" document. We printed a copy and ran through all 19 pages of the assessment.

• SLDCHECK looks good

• SXI_CACHE is good

• RFC Connections are now good - we discovered a misconfigured AI_RUNTIME_JCOSERVER rfc destination

All of the other tests were good.

The tests for the adapter monitor in the runtime workbench were inconclusive. It's impossible to test the adapters if the adapter metadata hasn't been loaded from the .TPZ file first. That's why in our system, the only adapter listed was the JPR (Java Proxy Runtime) ....all of the other J2EE adapters (file, http, etc.) were missing.

[Former Member · Accepted solution]

Hi Terry -

Look at your XI Java components to make sure they are aligned in terms of SP level. Use http://host:port/sap/monitoring/ComponentInfo to check.

If you see discrepencies, align them first before proceeding with the SAP BASIS content import.

Regards,

Jin

[Terry_KPMG · Accepted solution]

Shortly after the base installation was completed, we patched the ABAP stack to SP19 and J2EE stack to 10

Here's the list of components:

Software Components

sap.com LM-TOOLS 6.40 SP19 (1000.6.40.19.0.20061016102754)

sap.com NWMADMIN 6.40 SP19 (1000.6.40.19.0.20060929141849)

sap.com SAP-JEE 6.40 SP19 (1000.6.40.19.0.20061027073233)

sap.com SAP-XIAFC 3.0 SP9 (1000.3.0.9.1.20041028052722)

sap.com SAP_XITOOL 3.0 SP9 (1000.3.0.9.0.20041026233717)

sap.com SAP-JEECOR 6.40 SP19 (1000.6.40.19.0.20061027073059)

sap.com SAP_JTECHF 6.40 SP19 (1000.6.40.19.0.20061027073345)

sap.com SAP_XIAF 3.0 SP9 (1000.3.0.9.0.20041026233659)

sap.com SAP_JTECHS 6.40 SP19 (1000.6.40.19.0.20061027073538)

[Former Member · Accepted solution]

Patch the SP9 components (SAP-XIAFC, SAP_XIAF, and SAP_XITOOL) to SP19. Then import the SP19 version of the SAP BASIS 6.40 XI Content. Hopefully, that will take care of this issue.

Importing of the XI content is usually the last step of the patching process and probably relies on SP level consistency of the underlying J2EE engine and XI components.

Regards,

Jin

[Terry_KPMG · Accepted solution]

That did the trick Jin!

After applying the support stack and refreshing the cache - we get the following:

sap.com SAP-XIAFC 3.0 SP19 (1000.3.0.19.8.20070223123719)

sap.com SAP_XITOOL 3.0 SP19 (1000.3.0.19.4.20070124155110)

sap.com SAP_XIAF 3.0 SP19 (1000.3.0.19.6.20070216064828)

I was able to import the BASIS components and life is good!

...now off to break something else!