(Minor?) Bug: ACR Preferences file does not match ACR version number

This may be of no major consequence (I don't know one way or the other) but the preferences file for ACR 4.2 on my Mac shows up as "Adobe Camera Raw 4.1 Prefs", even after trashing it and letting ACR rebuild it.

The question mark should have been after "Bug", I reckon. (As in "Bug?")
The reason I brought it up was that it has caused confusion to at least one user over at the Bridge Macintosh forum.
The Adobe Bridge team has been suggesting to purge the ACR cache as a means to alleviate a very significant bug in Bridge (it's showing the wrong thumbnail and preview in some instances, speciously calling up thumbnails and previews of totally unrelated images in very different folders).
Therefore, that user (and I suspect others) tried nuking the ACR preferences file as well.

Similar Messages

AddOnsLocalRegistration.sbo file does not match data in the common datab...

We are receiving the following error everytime we logon our pc for the first time: Add-On Outlook_Integration: This Add-on cannot be upgraded. AddOnsLocalRegistration.sbo file does not match data in the common database for this add-on. See SAP Note 1323680 for more information.
A few months ago, SBO Server was moved from one server to a new virtual server, but we had no problems with the addons. The other day, we upgraded from SBO 2007 to 8.8 and now we are having problems with the Outlook Integration.
I have followed the directions in the message noted above, and did find the AddOnsLocalRegistration.sbo file in some odd places, with a reference to the old server. I cleaned this up, on the server and the client and I can get it running...however, after the user shuts down the pc and logs back in the next day, the problem is back.
In the process of cleaning this up (un-registering the addon and removing the addon references in the local .sbo file) I noticed at times that we would still receive this error, when there really shouldn't be an reference to it.
Thanks for any help.

Hi Vaughn.........
I guess you need a re installation of Outlook Integration Addon.
Whatever version addon of OI you installed just uninstall it and Install it freshly from 8.8 setup package......
Regards,
Rahul

Planning Quick Win Error: Registration file does not match the app version.

Gents,
I have a Fusion 11.1.2 install on a Windows 2003 server environment.
After creating the Planning App in Classic mode, I logged back in to Initialize the App... and I got this.
This occurred when I tried to log on to the Planning App in Workspace. (I was about to go Create/Refresh the app) :
"An error occurred while processing this page. Check the log for details.Please close the current tab and open application again. Single Sign on Validation failed"
The SharedServices_Security.log goes as follows:
2009-05-12 16:08:11,437 ERROR [http-28080-Processor3] com.hyperion.css.common.CSSUtils.checkValidArgument(Unknown Source) -- 26:1002:Invalid value for identity. Enter a valid value.
2009-05-12 16:08:11,468 WARN [http-28080-Processor3] com.hyperion.css.spi.impl.nv.NativeProvider.getHierarchicalRoleTree(Unknown Source) -- Exception getting Child Roles in hierarchy [Root Cause: 26:1002:Invalid value for identity. Enter a valid value. ]
2008-05-12 16:42:47,781 WARN [http-28080-Processor9] com.hyperion.css.spi.impl.nv.XMLRoleRegDocumentModel.recurseDocumentTree(Unknown Source) -- The Product 'Hyperion Planning' Version 'HP-9.5.0' in the Registration file does not match the application version '9.5.0'
Any suggestions?
Thanks.
Eric.

Hi,
If you are running on a Microsoft OS, have a look the log :- :\Hyperion\logs\services\HyS9Planning-sysout.log
Not sure how much information it will give though.
Cheers
John
http://john-goodwin.blogspot.com/

Public-yum ol6_latest Metadata file does not match checksum

Update: public-yum is working today and manual checksum is matching as well.
I am trying to apply the latest Oracle Linux 6 patches to a fresh 6.4 install from the public-yum. I am able to successfully apply the latest Oracle Linux 6 UEK from the ol6_UEK_latest repository on public-yum. I am unable to access the ol6_latest repository on public-yum because I receive a "Metadata file does not match checksum" error. I have attempted to manually verify the checksum and receive a mismatch as well. See below for more details.
Thanks,
Erick
$ ### clean up yum cache directory
$ yum clean all
Loaded plugins: refresh-packagekit, security
Cleaning repos: ol6_UEK_latest ol6_latest
Cleaning up Everything
$ ### attempt to check for updates
$ yum check-update
Loaded plugins: refresh-packagekit, security
ol6_UEK_latest                                                                           | 1.2 kB     00:00
ol6_UEK_latest/primary                                                                   | 8.0 MB     00:00
ol6_UEK_latest                                                                                          183/183
ol6_latest                                                                               | 1.4 kB     00:00
ol6_latest/primary                                                                       | 29 MB     00:02
http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
ol6_latest/primary                                                                       | 29 MB     00:02
http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/primary.xml.gz from ol6_latest: [Errno 256] No more mirrors to try.
$ ### manually verify checksum by downloading gz for UEK repository
$ wget http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/x86_64/repodata/primary.xml.gz
--2013-06-13 09:49:17-- http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/x86_64/repodata/primary.xml.gz
Connecting to 10.87.79.250:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 8409269 (8.0M) [application/x-gzip]
Saving to: “primary.xml.gz”
100%[======================================================================>] 8,409,269   11.1M/s   in 0.7s
2013-06-13 09:49:18 (11.1 MB/s) - “primary.xml.gz” saved [8409269/8409269]
$ ### now download xml for UEK repository
$ wget http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/x86_64/repodata/repomd.xml
--2013-06-13 09:52:14-- http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/x86_64/repodata/repomd.xml
Connecting to 10.87.79.250:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 1240 (1.2K) [text/xml]
Saving to: “repomd.xml”
100%[======================================================================>] 1,240       --.-K/s   in 0s
2013-06-13 09:52:14 (106 MB/s) - “repomd.xml” saved [1240/1240]
$ ### get published checksum from xml
$ grep -nA1 primary.xml repomd.xml
16:    <location href="repodata/primary.xml.gz"/>
17-    <checksum type="sha">c8fc85aa170c9da4a04e8a58ab594f67c319e874</checksum>
$ ### generate checksum for gz
$ sha1sum primary.xml.gz
c8fc85aa170c9da4a04e8a58ab594f67c319e874 primary.xml.gz
$ ### UEK checksums match, clean up UEK files from directory
$ rm primary.xml.gz repomd.xml
$ ### manually verify checksum by downloading gz for ol6 repository
$ wget http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/primary.xml.gz
--2013-06-13 10:04:59-- http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/primary.xml.gz
Connecting to 10.87.79.250:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 30474994 (29M) [application/x-gzip]
Saving to: “primary.xml.gz”
100%[======================================================================>] 30,474,994 6.64M/s   in 4.5s
2013-06-13 10:05:04 (6.40 MB/s) - “primary.xml.gz” saved [30474994/30474994]
$ ### now download xml for ol6 repository
$ wget http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/repomd.xml
--2013-06-13 10:05:10-- http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/repomd.xml
Connecting to 10.87.79.250:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 1429 (1.4K) [text/xml]
Saving to: “repomd.xml”
100%[======================================================================>] 1,429       --.-K/s   in 0s
2013-06-13 10:05:10 (55.7 MB/s) - “repomd.xml” saved [1429/1429]
$ ### get published checksum from xml
$ grep -nA1 primary.xml repomd.xml
16:    <location href="repodata/primary.xml.gz"/>
17-    <checksum type="sha">c8b3d8c353045b6e96f1eb6ed519c5d6e75faad3</checksum>
$ ### generate checksum for gz
$ sha1sum primary.xml.gz
47c33491455170c1460646ab3652e40087a4aa19 primary.xml.gz
$ ### ol6 checksums do not match, clean up ol6 files from directory
$ rm primary.xml.gz repomd.xml
$
Message was edited by: esigfrid

Thank you for your advice. Currently public-yum is working again for my two systems (without any changes on my side). If I run into this problem again I will give it a try.
Erick

"Source File does not match XML Schema"

Using MDM 5.5 SP4 Patch 2 (Build 5.5.34.26) on a 32-bit system (WinServer 2003, Enterprise Edition SP1.
This source file and schema have been verified by SAP Tech Support and again using Altova XML Spy. The schema was loaded into MDM through the console and the source file was successfully mapped against it and the data manually imported into MDM. The customer record was then cleansed using the Data Manager and the import map was used to create an inbound port. However, when the Import Server goes to import the file using the map, the following error is dropped into the log: "Source File does not match XML Schema". Has anyone else seen this error?
Thanks, Don
IMPORT LOG ENTRY:
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="MDM_Log.xsl"?>
<MDM_Log version="1.0" path="H:PROGRA~1SAPMDM~1.5IMPORT~1TempMDIS_TASK@@U@[email protected]"
>
     <Open ts-long="18:24:35 GMT, Saturday, February 03, 2007" ts="2007/02/03 18:24:35.108 GMT" pid="8640" host="bp1tulap452" compile-type="RELEASE_32">
          <Trace ts="2007/02/03 18:24:35.249 GMT" tid="7216" entry-no="3">[BP US FUELS CUSTOMER MASTER] Import Task Started. Chunk size[50000], No. parallel chunks[1]</Trace>
          <Trace ts="2007/02/03 18:24:43.890 GMT" tid="5980" entry-no="11">xSaxParser: Starting.</Trace>
          <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="19">xSaxParser: Ending.</Trace>
          <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="20">Source file does not conform to XML Schema!<LINE-FEED/></Trace>
          <Trace ts="2007/02/03 18:24:45.312 GMT" tid="7216" entry-no="29">[RESPOSITORY]Import Task Finished. Chunk size[50000], No. parallel chunks[1]</Trace>
     </Open>
</MDM_Log>
SOURCE FILE:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:CustomerCreateResp xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
- <CUSTOMER>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<MDMCUSTOMER>2463</MDMCUSTOMER>
<CREATE_DATE>22/01/2007,11:43:49</CREATE_DATE>
- <RETURN>
<TYPE />
<MESSAGE />
</RETURN>
- <PT_CONTPART_RETURN>
- <item>
<MDM_CONTACT>0000000001</MDM_CONTACT>
<CONTACT>0001111119</CONTACT>
</item>
- <item>
<MDM_CONTACT>0000000004</MDM_CONTACT>
<CONTACT>0002222229</CONTACT>
</item>
</PT_CONTPART_RETURN>
- <PARTNERS>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>RE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001333329</PARTNER_NUMBER>
<DEFAULT_PARTNER>X</DEFAULT_PARTNER>
</item>
- <item>
<CUSTOMERNO>0090154474</CUSTOMERNO>
<PARTNER_FUNCTION>WE</PARTNER_FUNCTION>
<PARTNER_NUMBER>0001555559</PARTNER_NUMBER>
<DEFAULT_PARTNER />
</item>
</PARTNERS>
</item>
</CUSTOMER>
</ns1:CustomerCreateResp>
SCHEMA:
   <?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" targetNamespace="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" elementFormDefault="unqualified">
<xsd:element name="CustomerCreateResp" type="CustomerCreateResp" />
- <xsd:complexType name="CustomerCreateResp">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">682cc2d0aa6e11db9b800015c5888624</xsd:appinfo>
</xsd:annotation>
- <xsd:sequence>
- <xsd:element name="CUSTOMER">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f68988f0a02e11db94bb00166f98336c</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b20a75811dba9d400166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b21a75811db9c4800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MDMCUSTOMER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b22a75811dbcbac00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CREATE_DATE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b23a75811dbcc0300166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b24a75811db8d5500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="TYPE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b25a75811db876d00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="MESSAGE" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b26a75811db85c400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PT_CONTPART_RETURN" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b27a75811db8ca900166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b28a75811dbaae100166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="MDM_CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b29a75811dbaade00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="CONTACT" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2aa75811dbc24c00166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
- <xsd:element name="PARTNERS" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ba75811dbb74500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ca75811db9f6500166f983d94</xsd:appinfo>
</xsd:annotation>
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2da75811db9bd800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_FUNCTION" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ea75811dbb84100166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="PARTNER_NUMBER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2fa75811db852800166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="DEFAULT_PARTNER" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">72ea9b30a75811db968400166f983d94</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

You have to define the namespace in the URI field of XML Schmea in Console.
In MDM Console,
Admin -> XML Schemas -> Create XML Schema
You have to specify the namespace urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100 in the URI property.
Please update this post if fixed your problem.

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

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

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

The Dreamweaver client version does not match this version of the BrowserLab client

Cannot use BrowserLab
I have followed the upgrade instructions on this page
http://labs.adobe.com/downloads/browserlab.html
Deleted the MeerMeerDW folder, downloaded and installed the latest MXP files.
But when I try to use BrowserLab from Dreamweaver after program loads error message says
"The Dreamweaver client version does not match this version of the BrowserLab client.
Please download and install the latest version of the Dreamweaver MXPs"
I have tried several times, even tried removing the extensions from Extension Manager, quiting the program,
deleting the MeerMeerDW folder, restarting Extension Manager and reinstalling the MXPs, then starting Dreamweaver
and trying the Preview in Browser>Adobe BrowserLab. Same problem, program loads and then get error message.
Macintosh OS 10.5.8
Dreamweaver CS4
Extension Manager CS4 (2.1.115)

Hello toni7,
I'm sorry to hear you're having problems. Are you prompted to replace the existing extensions when performing the installation? The error message you are receiving when using the service is expected if the new versions of the extensions are not installed.
What is the version number of the extensions displayed in Extension Manager?
Are you deleting the MeerMeerDW folder in the user library prior to installing the new version of the extensions? And just to be sure, are you logged in as the same user? [(user)\Library\Application Support\Adobe\CS4ServiceManager\extensions\MeerMeerDW]
Do you have more than one MeerMeerDW folder at the path above?
Also, be sure that all adobe applications are closed before trying to install the new extensions. I would also make sure that CS4ServiceManager, Extension Manager and Dreamweaver are not running when you delete the MeerMeerDW folder and prior to installing the updated extensions. Go to Applications\Utilities\Activity Monitor and Quit Process on any of those three running prior to installing.
It's critical that the MeerMeerDW folder is manually deleted, rather than removed using Extension Manager before updating the extensions.
Best regards,
Corey

The version of SOS does not match the version of CLR you are debugging.

I have a 32 bit crash dump file that I have loaded with WinDbg X86 (I'm running on Win7 63 bit).
When I open the crash dump file I do the following:
.loadby sos clr
then when I try to run any other command I get the following error:
The version of SOS does not match the version of CLR you are debugging. Please
load the matching version of SOS for the version of CLR you are debugging.
CLR Version: 4.0.30319.269
SOS Version: 4.0.30319.296
How do I load another version of the SOS dll? and
How do I find out what version of SOS I need to load?
Thanks

I see that there is another version of sos.dll located in:
C:\Windows\Microsoft.NET\Framework\v2.0.50727.
So I have tried to add this path in File-->Symbol File Path like so:
srv*c:\symcache*http://msdl.microsoft.com/download/symbols;C:\Windows\Microsoft.NET\Framework\v2.0.50727
It doesnt seem to make any difference.
When I type !chain I dont see this path output.

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

The serial number on my new boxed photoshop bought from Staples does not match the required number of numbers to install. Help

The serial number on my new boxed photoshop bought from Staples does not match the required number of numbers to install. Help

You’ve posted your comment in the Adobe Creative Cloud forum. Adobe Creative Cloud doesn’t use serial numbers. Does this page help with determining what to do with the number you have:
http://helpx.adobe.com/x-productkb/global/redemption-code-help.html

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

JNI generated header file does not match the class file

We have had a JNI project for many years and all has been fine. Within our libraries we have several classes that have inner enum classes.
Recently we have moved to JDK1.7. Up to now when JNI generated the methods where the signature used the inner enum class, and it was an oveloaded method, we would get something like the following as the signature:
Java_PackageName_ClassName_methodName_OuterClass_00024InnerEnum_2
And the class file result of the build would look like the following:
methodName(OuterClass$InnerEnum)
Since we have moved to JDK 1.7 the header file looks like the following:
Java_PackageName_ClassName_methodName_OuterClasss_InnerEnum_2
The class file is still the same, and because of that when we run the program we get an UnsatisfiedLinkError. I understand that this error is because the VM cannot find the implementation. So why JDK 1.7 generates a header file that does not match the class file?
Thank you in advance.

I don't have 1.6 to verify but your statements about what is generated for 1.7 for the header appear correct.
The 000024 represents the '$' and for 1.7 the inner class is still named using '$'. So for example after compiling in 1.7 the inner class file is named the following...
MyClass$InnerEnum.class
So a one to one conversion should have kept the 000024 (presuming it does in fact do it that way in 1.6.)
You might want to look at the release notes for 1.7.
If you need a solution you could add a post javah step that renames the file.

KG843 Currency type does not match plan version

Dear all,
we try to set up a CO-PA-planning in company code currency CZK / our operating corncern-currency is EUR - in the operatin concern we have maintained currency EUR and we have set the flag "Company-code currency" (TA KEA0).
As actual/plan-Version we use Version 0 with the following settings for operation concern: Currency type B0 (Operating Concern currency).
Now we try to plan our CO-PA characteristics and value fields with TA KEPM. Therefore we have created a planning layout. Here we receive the error message: KG843 Currency type does not match plan versionThe planning layout (TA KE15) is set up like this:
1. By creation of the layout we selected "Operating concern currency / Company code currency" because we would like to plan in CC-Currency
2. In the General data selection I have selected currency type = 10 = Company code currence because we would like to plan in CC-Currency
3. In the value field I selected Plan/Act. Indicator = 1 = Planning data and Version = 0
Do you know why I receive message KG843 - or what can I do so that I am able to plan with currency type 10 and version 0?
Thanks for a soon feedback.
Best regards,
XmchX

Ok, here's what SAP help has to say about multiple currencies in COPA planning:
http://help.sap.com/erp2005_ehp_05/helpdata/EN/7a/4c3d494a0111d1894c0000e829fbbd/frameset.htm
Basically it says you have to define one version for OC currency and one version to use CC currency. Then plan in one version and copy to the other. Currency conversion will happen when copying.
REgards
Nikolas

(Minor?) Bug: ACR Preferences file does not match ACR version number

Similar Messages

Maybe you are looking for