Matching component versions in PI to note requirements

Weu2019re being asked to put in a patch to our PI 7.1 SP07 systems for the Adapter framework and the Messaging system.
I donu2019t know how to exactly read the version information I get from the NWA system info readout.
I give this from the component readout for our system for Messaging system:
1000.7.10.7.1.20081209195700 MESSAGING SAP AG sap.com
The note says only install the below patch if it matches the level of your system: That patch is for this level:
MESSAGING SYSTEM SERVICE 7.10 SP007 000002
Do these match? Or do I read the version I have for the messaging component as PI 7.0 SP07 P1 20081209. Where 1000.7.10.7  PI 7.1 SP07 and 1000.7.10.7.1  PI 7.1 Sp07 patch level 1. Then the rest is the date? 20081209  12/09/2008? The rest I donu2019t know. Is it a time stamp? 195700?
Iu2019m confused. Any help on how to read these component versions from the note would be greatly appreciated.

Hello George
Please check the note #1381878 How/where to check the patch levels of your XI/PI. Let me know if you have any further questions/concerns.
Regards
Mark

Similar Messages

Does not match component version

Hi,
We have four system landscape. We have already upgrade our DEV and ITT to EHP5.We still have to upgrade our UAT and prod to EHP5. When I see the transport queue on ITT system.I see all the transport that was imported on ITT before the upgrade is showing as "Does not match component version".
I can understand that the version before the upgrade was different so it should show that message.
I just wanted to check if this is normal or I need to make changes to TMS?
Regards!
Ravi

Hi,
You can do as follows:
Switch it off with parameter : SP_TRANS_SYNC = OFF
Procedure:
Call transaction STMS
Goto 'Systems Overview'
Double click <SID> you wish to add the parameter to
Goto 'Transport Tool' tab
Goto 'change mode'
Add SP_TRANS_SYNC to parameter column and OFF to value column
Save, activate and distribute
With Version SAP_BASIS 702 a new feature was added to the TMS system,
tp is now checking the component version of the transport which was
released and the component version of the system where the transport is
going to be imported. If there is a difference, this difference is
highlighted in the import queue (transaction stms_import) and if you try
to import the transport, the import will stop with a warning message
about the difference in the SAPCOMPONENT versions.
If you wish to by-pass with warning then you can choose 'Ignore invalid
Component version'.
Regards,
Aidan

Before using the current Mac version Yosemite, I did not have an Administrator password. It seems now that one is required to unlock and make changes in settings. I have tried all my usual passwords but to no avail. any ideas???

Before using the current Mac version Yosemite, I did not have an Administrator password. It seems now that one is required to unlock and make changes in settings. I have tried all my usual passwords but to no avail. any ideas???

Boot into Recovery. OS X: About OS X Recovery - Apple Support
Select Terminal from the Utilities menu.
At the prompt type,
resetpassword
Hit return.
Follow the prompts in the utility to select hard drive, then user.
Reset the password.
Exit the utility and restart.
You will need to log in with your new password, but your keychain will not be reset.
I’m not sure what access you’ll have to the old keychain since it didn’t have a password. You may be able to get into the keychain and reset the password to match your login password.

DBD::mysql object version 4.013 does not match bootstrap parameter 4.005

The issue is with XServe running 10.6.2.
Out of the box Perl doesn't come with DBM::MySQL module installed. To be able to install it, I first had to download MySQL libraries (instructions and link to the file are here: http://support.apple.com/kb/HT4006 ).
After that I was able to install (manually with "make") the latest module DBD-mysql-4.013 which Perl now acknowledges. However, when module is called, following error is thrown:
"install_driver(mysql) failed: DBD::mysql object version 4.013 does not match bootstrap parameter 4.005 at /System/Library/Perl/5.10.0/darwin-thread-multi-2level/DynaLoader.pm line 230.
Compilation failed in require at (eval 3) line 3."
Suspecting that Perl is looking for a 3-year old version 4.005, I did try removing 4.013 and installing 4.005 instead (as I couldn't find any other clear solution) but 4.005 failed to pass "make test" - not very surprisingly as it is that old - so I chose not to try installing it and put 4.013 back in and still got same error.
If somebody could kindly provide/direct me to clear instructions to resolve this problem your help will be much appreciated! Thanks in advance.

Unfortunately, I didn't document right away what I did to get this resolved but this is what I remember. This is a hack, I found a suggestion online that lead me to this. However, a FAIR WARNING - this is dangerous for the system.
I went into the module file mysql.pm located here:
cd /Library/Perl/5.10.0/darwin-thread-multi-2level/DBD
vi mysql.pm
I commented out the line that specifies version of the file, 4.013, and put 4.005 line instead:
#$VERSION = '4.013';
$VERSION = '4.005';
If server is not rebooted, this doesn't change anything, error will still be thrown. So I rebooted the server from command line.
This reboot did not go well, server went into some kind of intermediate state, I lost web access. We had to do a hard reboot by cycling power physically on the server itself. After that server came back up, log was full of all kinds of errors. Now all of a sudden the error "object version 4.013 does not match bootstrap parameter 4.005" wasn't thrown anymore. Apparently, version of this module is not read from the module .pm file itself every time module is called, it is instead stored somewhere else and is looked up there, wherever "there" may be. I suspect one of the files used during boot got confused when version number didn't match and it caused chain reaction and a bad reboot.
Later on I went back into the file and changed version number back to 4.013 as it is supposed to be, and commented the other line out:
$VERSION = '4.013';
#$VERSION = '4.005';
MySQL on Perl functioned fine since then.
Server has been rebooted weeks later during 10.6.3 upgrade and this time it didn't cause any problems with the module. Still works.

Invalid application descriptor: descriptor version does not match runtime version

Hi.
I have writen a very simple AIR app. Its not really an app
just a button on the stage in flex2 as I want to try packaging it
up as an air app from the command line. When i use adl to do this i
get the following error.
invalid application descriptor: descriptor version does not
match runtime version
I have just downloaded the latest version of AIR 1.0.1 and
still have no joy even when i change <application xmlns="
http://ns.adobe.com/air/application/1.0">
to <application xmlns="
http://ns.adobe.com/air/application/1.0.1">
The code for my app is below, i woudl very much appreciate a
little advice as to where i am going wrong.
Many thanks
Barry.
test-app.xml (descriptor file)
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="
http://ns.adobe.com/air/application/1.0.1">


<id>test application</id>

<filename>test</filename>

<name>test app</name>

<version>v1</version>





<initialWindow>


<content>test.swf</content>


























</initialWindow>


























</application>
test.mxml
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Button x="201" y="167" label="Hello AIR!"/>
</mx:Application>

My descriptor version was 1.5.2
(see line <application xmlns="http://ns.adobe.com/air/application/1.5.2"> in file appName-app.xml)
My Flex sdk was 3.2 (see Project->Properties->Flex Compiler->Flex SDK Version)
To support air debugger (adl) version 1.5.2, sdk 3.2 was too old, so i got this same error
so i switched to sdk 3.4 (free download at adobe.com)
and the problem was solved

Can not view a Software Component Version in Enterprise Services Repository

Hello,
I'm trying to import in ESR the software component version created in the SLD. I'm using SAP PI 7.3.
Into to work area select Software Component Version and click on checkpoint Import from SLD. Click in bottom Display (List of Software Component Versions) and it show me the list but cannot view the Name of the SWC created.
I cleared the cache (Environment - clear sld data cache) and the result it's the same, not show the SWC the I created.
Do you have any idea?
Thank you in advance.
--erva

Hi,
as it's a new installation, you certainly missed something. have you did controls of Readiness Check doc and tcode SLDCHECK ([see PI 7.1x oss note|https://service.sap.com/sap/support/notes/1143810]).
and check these post installation controls (but it's for PI 7.1): [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60d2a693-9504-2b10-5ba7-82964bd8370e?QuickLink=index&overridelayout=true]
Mickael

Some Software Component Versions do not show up in transaction sproxy

I have a landscape with a CRM system, a PI system (with the SLD on it) and some other systems.
In transaction sproxy in the CRM system the Software Component Version SAP CRM ABAP 7.0 shows up, but others that should be there like SAP ABA 7.01 are not there.
So I went on the SLD and edited the technical system for the CRM system, I added the product SAP CRM 7.00 and set the checkmark for installed for the relevant SWCVs like SAP ABA 7.01.
I then went to the business system for the relevant CRM client and there also checked those SWCVs.
But still they do not show up in transaction sproxy in the CRM system.
What am I missing?

Hi Monika,
There's several suggestions that you could look at to help resolve your problem in this thread:
[Can't find ESA ECC-SE 603 SWCV;
Regards, Trevor

Error while trying to install NI-VISA driver on SUSE LINUX 11.1(The version of gcc in the path does not match the version of gcc used to compile the currently running kernel.)

hi i am trying to install NI-VISA driver on SUSE LINUX 11.1.
the error message it shows is
******************************** ERROR ****************************************
* The version of gcc in the path does not match the version of gcc used to    *
* compile the currently running kernel. This can cause unpredictable         *
* behavior in kernel drivers and should be fixed.                             *
* gcc version: Linux)                                                          *
* kernel compiled with: 4.3.2                                                 *
******************************** ERROR ****************************************
my kernel source version is
linux-8nes:/home/admin # rpm -qi kernel-source
Name        : kernel-source                Relocations: /usr/src
Version     : 2.6.27.29                         Vendor: openSUSE
Release     : 0.1.1                         Build Date: Sun 16 Aug 2009 03:43:52 PM IST
Install Date: Sat 24 Oct 2009 02:13:12 AM IST      Build Host: rinck
Group       : Development/Sources           Source RPM: kernel-source-2.6.27.29-0.1.1.src.rpm
Size        : 309251954                        License: GPL v2 only
Signature   : RSA/8, Sun 16 Aug 2009 03:57:25 PM IST, Key ID b88b2fd43dbdc284
Packager    : http://bugs.opensuse.org
URL         : http://www.kernel.org/
Summary     : The Linux Kernel Sources
Description :
Linux kernel sources with many fixes and improvements.
Authors:
    Linus Torvalds <[email protected]>
    see /usr/src/linux/CREDITS for more details.
Source Timestamp: 2009-08-15 17:53:59 +0200
GIT Revision: 8a413546901c407e96f7fba18574cceeb40452af
GIT Branch: SLE11_BRANCH
Distribution: openSUSE 11.1
i had also installed GCC 4.3.2.
it shows the error message as i had posted.
please kindly help me on this.
Thanks and regards,
P.karthick

Check this solution

Could not read list of software component versions

Hi,
I am trying to import software components from sld into esr. When i click on display available components i get the error :
Could not read list of software component versions
The details show:
Could not read list of software component versions
from SLD (COULD_NOT_READ_SWCV)
HTTP response code: 403 (Forbidden)
we were initially getting access issue also in details, but that has been rectified by assigning appropriate roles.\
Kindly help.

Hi,
Use t-code SLDCHECK on ABAP stack to confirm the connection of XI system and SLD.
Check whether SLD and XI system are on same server. Refer to OSS note - 720717 to integrate XI with other SLD.
In the Integration Builder page, Click on the Administration and check the following parameters to make sure they are pointing to right SLD system and port.
com.sap.aii.connect.cr.httpport
com.sap.aii.connect.cr.name
com.sap.aii.connect.landscape.httpport
com.sap.aii.connect.landscape.name
GreatDay,
venkatagiri
Edited by: Giriii on Sep 15, 2011 8:14 AM

V5R4M5 does not match InfoAPAR version V5R4M0, import error

Hi All,
We found following warning when PTF check in ECC6sr3 sapinst on v5r4
WARNING: The OS/400 version V5R4M5 does not match InfoAPAR version V5R4M0.
ok Product ID: 5722SS1 - PTF ID: SI22389 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: TL07282 - Status: NOT UP TO DATE
CUMPKG
ok Product ID: 5722999 - PTF ID: MF42358 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42518 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42529 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42394 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42393 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42258 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42043 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF42042 - Status: NOT UP TO DATE
ok Product ID: 5722999 - PTF ID: MF41883 - Status: NOT UP TO DATE
   23 PTFs checked.        11 missing PTFs detected.
The microcode is M5 however OS is M0. We also got similar warning in other host with 2 missing PTFs and SAP installation can successfully completed. But with this M5 host always warns with TL07282 missing (however TL57282 existed)
we checked APAR recomendation for v5r4m5 from IBM, products, and sysval, tmksvrpatch, all are sufficient only this PTF check from SAPinst. When we continue, the import processes are failed
(DB) ERROR: DDL statement failed
(CREATE TABLE "DDNTF_CONV_UC" ( "TABNAME" GRAPHIC(30) CCSID 13488 DEFAULT ' ' NOT NULL , "BLOCKNR" SMALLINT DEFAULT 0 NOT NULL , "FIELDSLG" DECIMAL(5,0) DEFAULT 0 NOT NULL , "FIELDS" BLOB(32600) ) )
DbSlExecute: rc = 99
(SQL error -901)
error message returned by DbSl:
SQL system error. MSGID= Job=009618/SAPINST/QJVAEXEC
(IMP) ERROR: DbSlPrepare/BegModify failed
rc = 103, table "DDNTF_CONV_UC"
(SQL error 204)
error message returned by DbSl:
DDNTF_CONV_UC in R3ECDDATA type *FILE not found. MSGID= Job=009618/SAPINST/QJVAEXEC
TRACE: 2008-09-10 11:14:29 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
/usr/sap/ECD/SYS/exe/run/R3load -i SAPNTAB.cmd -dbcodepage 4102 -l SAPNTAB.log -nojournal
ERROR: 2008-09-10 11:14:32 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process '/usr/sap/ECD/SYS/exe/run/R3load -i SAPNTAB.cmd -dbcodepage 4102 -l SAPNTAB.log -nojournal' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
¢u2014u2014u2122
What seems missing to check? We are on applying the mssing PTF but still stuck with PTF not fuond from media msg . Thanks for reading the details.
Regards,
-asp-

Hi -asp-,
From your description it is not clear to me whether you checked against infoapar.455 or not. If you missed this, follow the descriptions of note 144149.
Regarding the SQL -901 you need to look up the joblog of the failing process and check the messages right before the SQL -901 for the real reason.
HTH,
Thomas

Error in IR Namespace is not defined in the software component version

Hi All,
Please provide your valuable inputs to resolve the issue.
Namespace http://xxx.com is not defined in the software component version xxx_xxxxxx , 1.0 of xxx.com
Though the software component was already created in SLD and imported.All the developers were able to access the software component and create the Namespaces for their scenarios, but when tried to Activate the scenario above mentioned error is displayed.
Below are the checks done.
1.In Exchange Profile checked the properties,
com.sap.aii.connect.cr.httpport
com.sap.aii.connect.cr.name
com.sap.aii.connect.landscape.httpport
com.sap.aii.connect.landscape.name
2. Tried to import the software components once again through IR -- No results
3. Restarted the Java Engine through SMICM -- No results
4.Performed the SLDCHECK no errors.
Inputs please at the earliest
Regards
Shiva.

Hi Jochen,
This is occuring due to that the created namespace is not getting activated. As mentioned in earlier replies that if you have copied objects from somewhere else then all the related information should also be copied. If the problem resists then you can create all the needed objects in IR again and activate it separately instead of activating all at once.
Regards,
Subhasha

Error : Resource not found in the S/W component versions

Hello All,
I am using Pi 7.1 . I have a scenario IDoc to File . When i execute my end to end scenario i am getting the following error :
Unable to find resource bce2fba0-80bd-11de-93f0-e5e70ad6cb21 in the following software component versions: http://NANCO/N001/CMS_Customerscom/sap/xi/tf/_MM_N001_DEBMAS06_TO_CMS_Customers
whereas the mapping is working fine in the Operation mapping.
Can anybody hwlp me with this?
regards,
Loveena

Hi Loveena,
                    I hope you are doing good.
                    Try to test your interface Mapping. It should also work fine and should find Operation Mapping.
                     Test your configuration in Integration Directory.
                     If above steps does not work, change a mapping name by bit and check it after that.Even then it does not work.
                     Go for cache refresh.
Regards,
Anurag

Error : software component version does not support this object type.

Hi ,
We are getting error as software component version does not support this object type when we try to create Business Object in PI 7.1 ESR .
How can we solve this error.
Regards,
Syed
Edited by: Umar Syed on Jun 11, 2009 12:01 PM

Hi Srinivas,
We are working on Modelling in SAP PI, but we are unable to create any Business Object.. is there any specific steps need to be followed.
Once we login to our ESR from index page we have this option to choose
Available Profiles :         Process Definition
                                   Service Definition
                                   Unregistered.
We are getting the option of new types (_Business Object_) only if we select Unregistered Profile and not in other Profiles . Is there some settings need to be done.
Regards,
Syed

Error /lib/libgcc_s.so.1 : version 'GCC_4.2.0' not found (required by /usr

Hi,
I have written a cpp plugin to call when the deactivate workflow is processing I have the OAM 10.1.4.3 version installed.
I am able to compile the file. But when try executing it from the workflow i am facing the below issue.
Error /lib/libgcc_s.so.1 : version 'GCC_4.2.0' not found (required by /usr/lib/libstdcc+.so.6)
Help me resolve this issue
Thanks.

Hi,
I think you are in the wrong forum here :-)
Regards
Patrick

Getting descriptor version does not match runtime version error

Thanks,
I am Using Adope Air SDK2.0 and Runtime Air 1.0.7,
i have created one HelloWorld application using Adope sample
code.
When i am trying to run this using commands :
i have used : adl HelloWorld.html
i am getting this error:
invalid application descriptor: descriptor version does not
match runtime version
Plz help me out.. :-)

The issue I had in Flashbuilder4 has been solved.
The easiest but possibly not the neatest was too copy the AIR 2 Beta SBK folders and files, then paste the over the flex4.0 sdk file structure. Achieves the same thing and I assume that you have copies of the SDK else where, if you need to roll back.
The other thing is to make sure the -app.xml that flex creates has the correct 2.0beta description.
Cheers
Elliot

Matching component versions in PI to note requirements

Similar Messages

Maybe you are looking for