E301 Symbol type in value file does not match symbol type in layout

Hello Experts,
Please help me. I am getting this kind of error when I am trying to open a report in cg02 using Report From Template option.
Regards
Dheeraj

Dear Dheeraj
Regarding:I am facing this problem only with one specification. For the other specifications I am able to open the report properly from Report from Template option.
Please compare data from one spec to the other. One spec does have more data. This "more" data yield to the result that a different WWI code is used and this WWI code is not "ok" and therefore you get problems.
Regarding; "Maitain Parameter Values" => try to skip or write "hello world" or whatebver; parameter values are needed later; only on "rare" cases they have impact on the e.g. report from template creation so taht you get a problem
Regarding:
I tried creating the report but the report is not created.The status of the report is Error. i went to information tab and clicked on F6 Parameter Values. System has thrown a message saying "No Parameter Symbols found in the template". But system is trying to pass the parameter values. I think because of this I am getting error..
Either you have used the wrong symbol type or used wrong function module to assign it to a own developped report symbol. etc. Please check; what was the last change either in WWI code or in report symbol definition.
Some thread have shown that sometimes the report symbol is prepared as report type "01" but should be "02" (or the other way around). This is one reason for such issues
Only by doing it step by step and checking:
a.) what has been changed in template?
b.) what is the difference in data on sepc 1 in comparison to spec 2
You will succeed. Sorry to say: to debug WWI is not as simple as ABAP code. This is one reason why some developpers might get "frustrated" in WWI;
May be check: WWI for Beginners
as well
C.B.

Similar Messages

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 Message - Value Entered Does Not Match Format of Field

I keep getting an error message in Adobe Pro X: "The value entered does not match the format of the field [JF13]".
I have JF13 programmed as follows:
On Calculate tab:
if(Number(this.getField("ck4").value) > 0) this.getField("JF13").value = Number(this.getField("FL019").value); else this.getField("JF13").value = " ";
It is programmed this way so if the user checks the check box before the field, only then will JF13 populate a value, which pulls from FL019. I also have the settings set to "number" because the data needs to display as a dollar amount $xxx.xx.
FL019 is a hidden field on the form which pulls a dollar amount from a Mainframe, and its settings are also set to "Number" :
I get four pop up windows with the above mentioned error message, and the only way to make the message stop is to remove the "number" format from the fields. However, when this is done, if any number which ends in a zero is entered, it cuts off the zero. This is not acceptable either.
Is there some sort of script I could add or some other way to prevent both the error message and the cutting off of the zero on JF13?
I am not very proficient with javascript, so any assistance would be appreciated!

Thank you so much for your response!!
Forgive me for my lack of knowledge - but where exactly would I add that in the script?
I tried it like this:
if(Number(this.getField("ck4").value) > 0) this.getField("JF13").value = Number(this.getField("FL019").value); else this.getField("JF13").value = ""(empty string);
And I got an error saying I was missing a parenthesis. Should it go somewhere else or am I completely off?

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

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.

Data in spool file does not match output.

This is a strange issue, and I'm not even sure it's a problem in SAP, but I don't know where else to ask and haven't found anything like it online:
We create pick lists on dot matrix printers. Occasionally, the output is missing a digit or character - for example in the middle of the delivery number. If delivery number is 81234567, the dot matrix output might be 8123467. The SAP spool file is not missing any data. And the paper dot matrix output is never skewed nor looks like it has jammed or "hiccuped". There is no space where the missing piece of data should be - it's all run together nice and neat. It occurs on different bits of data (sometimes, delivery#, name, batch, etc.), and it occurs on different printers at different sites. So far, it has always been only one digit or character missing every time it occurs. Reprint from the spool and it comes out fine.
So, SAP data is correct, and it occurs on different printers. Maybe it's a network issue? A printer buffer issue - but it happens on two different units, and that would be a weird coincidence. I really have no ides. Has anyone ever experienced anything like this?
Thanks,
Anke

Hello -
Difficult to answer accurately here as no access to spool data on the affected system and exact methods used. But, perhaps if you can print the RAW (OTF) data to a fileprinter and send that as a .txt file to the printer hardware vendor they could investigate why certain characters do not print.
Regards.

Exported video file does not match audio file in length?

I'm back with the same problem.
Here are the specs for this project:
Premiere Pro 5
Footage shot in HDV 1080i (Sony FX1)
Edited Timeline length...52:25
Destination: Blu-ray disc
I have tried both formats in the AME...MPEG2 Blu-ray and H.264 Blu-ray
I have tried every combination of Presets within these two formats...Match Attributes, 1440x1080i, HDTV....etc, etc, etc
The machine is spending anywhere from 7 hours to 27 hours to encode these files.
When I open the two files after the operation has finished, I find I have an audio file 52:25 in length and a video file 43:34, no matter what format or preset I have chosen!
Upon playback, you can imagine the frustration...within the first two minutes the two are out of sync.
What am I doing wrong here.
This is my first sortie into the HD world of Adobe. I've been doing Adobe Premiere SD for 10 years...and my deadline for the closed captioning is coming way too soon.
I appreciate any help you might offer.

Jim...Yes! I just did that this morning in frustration and by golly, they are both the same length. There is a note in the Project window after I copy to "Timeline" that says the video file is unencoded! Wierd! Another problem popped up in that the video and audio files are in different sequences in Encore. I cannot get them to play together. One will play and not the other...? I can't seem to drag them to the same sequence.
But, at least they are the same length! Mysteries in this HD business.

The value entered does not match the format of the field

I am trying to do a simple division of profit by sales to find the profit %. Here is the script I am using and it doesn't work.
var v1 = +getField("Profit%").value;
var v2 = +getField("Contract1").value;
event.value = v2 !== 0 ? v1 / v2 : "";
I continue to get the error The value entered doesnot match the format of the field
I have attached the file. Can someone help

Are you very sure?
Using
var v1 = 0.05; // "Profit%"
var v2 = 100000; // "Contract1"
v1 / v2; // result of division;
5e-7
That is 5 * 10 exponent -7 or 0.00000005
Set the format to "None"
Also so please post the values you are using.

(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.

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

Audio sample rate does not match (HDcam to dvcam)

I'm trying to import clips and keep getting this message:
"The audio sample rate of one or more of your captured media files does not match the sample rate on your source tape. This may cause the video and audio of these media files to be out of sync. Make sure the audio sample rate of your capture preset matches the sample rate of your tape."
Footage was originally shot on HDCAM and transferred to DVCAM elsewhere. Using FCP 5, am importing via firewire from a Sony DSR-11 deck. Using DV NTSC 48kHz Anamorphic as capture settings (though I've tried everything that I thought might possibly work with no success). The audio does not seem to drift over the course of several 5 minute or so clips. Clip settings show audio at 48 kHz (don't know if that's from capture settings or from actual data). Seems to me all audio should be 48 kHz 16 bits, so can't figure out what's going on. I have to export an EDL for the project to be finished in HD. Read some similar threads that ended in December, seemingly without much resolution. My broader concern is why this is happening; my immediate concern is do I need to worry about this right now since the media files will need to be recaptured in HD anyway. Any thoughts?
Thanks

A little more info. I'm having this problem on 4 tapes (from different cameras) that were transferred to DVCAM in a squished format to appear full screen on a 4x3 monitor. Video that was letterboxed and I can bring in with the standard DV NTSC capture settings does not have this problem. Still have the problem if I try to import the clips from the squished video with standard settings. Any thoughts?

Content Organizer bug - PDF files does not get routed correctly if autodeclaration is on and library level default values are set

It looks like whenever one specifies Column default values at a library level then the content organizer routing goes a bit awry SPECIFICALLY FOR NON OFFICE FILES [e.g. PDF] . Below are the observations and issues
1. Column level default value set on a record library with auto declaration of records turned on. The content organizer routes the document to the library but also keeps a copy of the document in the drop off library. It does not remove it from the drop
off library. The instant we clear the default value settings at the library level of the target library the content organizer works as expected again.
2. If default value settings are specified on a column in the target library then the PDF file gets routed to the document library but all the metadata is blanked out. The copy of the file that remains in the drop off library has all the correct metadata but
the target library has blanked out metadata.
Are the 2 observations described above by design or are they bugs? If so is there any documentation that is available that proves this because this does not make logical sense and proving this to a client in the absence of any documentation is a challenge.
The problem goes away if we shift the default value to the site columns directly at the site collection level. It's just the library level defaults that the pdf files do not seem to agree with

Hi Lisa,
Thanks for responding. This can be replicated in any environment but is only replicable for a specific combination of content organizer settings . The combination of settings I am referring to can be seen in the screenshot below. If you turn off redirect
users to the drop off library for direct uploads to libraries and if you turn on sharepoint versioning then you should be able to replicate the issue. Also we are using managed metadata site columns. I simplified this use case to a custom content content type
with just 2 custom managed metadata columns and can still replicate the issue in several environments. Also note the issue does not occur if the default values are set at the site or site collection level. It only occurs if you set the column value default
at a library level. I was able to replicate this on a completely vanilla Enterprise records site collection freshly created just to test this. Also note that the issue is not that the file does not reach the destination library. The issue is the
document does not get removed from the drop off library after it is transfered to the destination library which technically should have gotten removed.

Selected file cannot be linked because its type (video) does not match the original file's type

I've been using Premiere Elements 9 for a couple of years now, and a few months ago I began having problems importing AVI files created from a BlackMagic Intensity Pro capture card. (These issues were not previously occurring, and since they surfaced, I have exhausted the various settings for the BlackMagic card, used various software such as BlackMagic's own Media Express as well as the freeware VirtualDub, and still have the following problems.)
In addition, these AVI files play just fine, in their entirety, using Windows Media Player and in Quicktime.
The problem (or possibly two, but I suspect they could be related) is that most of the AVI files I attempt to import will either (1) import all video and NO audio, or (2) import ONLY a short segment of audio and video, and the length that Elements imports varies. Usually only in the range of a minute or two. The rest of the file is not imported at all.
After much digging in forums, and testing various settings in trying to figure out the issue, I decided to back up all of my files and completely wipe all hard drives and start over with a fresh installation of Windows and Premiere Elements 9. I haven't installed much else yet, as I wanted to first find out if the reinstallation improved things with Elements.
For the first project I created in Elements after the reinstallation, Elements successfully imported an entire AVI that was nearly 2 hours long, audio and video. This was a file that previously would not import properly into Elements. This suggested that my earlier installation of Elements must have been corrupted somehow. At this point I was very hopeful that all was well.
I proceeded to edit the video as I had wanted, saved the project, and exported it to an MPEG format file. I had originally wanted to export it as an MOV, but I hadn't yet installed Quicktime, so Elements couldn't do that just yet. The MPEG export was successful and plays fine.
However, I then installed Quicktime, and once it was finished, I restarted the PC and reloaded the same project. This time, Elements claimed the media was offline. I double-clicked on a segment of the video, and directed Elements to the raw file, but then an error message popped up: "The selected file cannot be linked because its type (video) does not match the original file's type (audio and video)." This was the same file I had JUST edited and of which I created an MPEG.
I tried creating a new project and the "Get Media" function to import the AVI again, but this time only the video imported with NO audio. (This would explain why the error message said what it did, but not why the audio wasn't imported.)
What in the world is going on with Elements??? I am baffled since the ONLY task I have done on this machine after a complete reinstallation of both Windows and Elements is edit one AVI. I find it very hard to believe that just installing Quicktime caused this.
Some info on my system:
System: Asus P6T w/ Intel i7 920 and 12 GB memory
OS: Windows 7 Ultimate
Video Software: Premiere Elements 9
Capture Card: BlackMagic Intensity Pro (PCI-e)
Capture Software: AVIs recorded with either BlackMagic Media Express or VirtualDub (only prior to the reinstallation, as neither of these programs are currently installed)
I'm getting to the point with Elements that I might need to just abandon it and find something else that is more reliable. Anybody have suggestions to help with this, so I won't have to migrate?

mtnsports
We think that we need to start off with definiting the properties of these .avi files that you are importing into Premiere Elements 9.0/9.0.1 (assumed that you are working for the required 9.0.1 Update).
You say that the "avi" was created from a "BlackMagic Intensity Pro capture card". What are the properties of this .avi that you imported into Premiere Elements? Not all .avi are created equal. What is the video and audio compression, frame size, frame rate, interlaced or progressive, pixel aspect ratio, typical duration?
Based on the properties of the video what have you been setting as the project preset?
Let us start here.
More later.
ATR

E301 Symbol type in value file does not match symbol type in layout

Similar Messages

Maybe you are looking for