Keyframe.h-142
Premiere Elements 12.1.620828
Bij het openen van een project krijg ik de fout "keyframe.h-142".
Dit is het geval bij de meeste projecten die enige tijd geleden aangemaakt werden.
ik kan enkel nog projecten openen die in de directory "Adobe Premiere Elements automatisch opslaan" zitten.
Wat is de oorzaak?
Paul
Paul
The keyframe 142 error has been discussed in many recent threads. According to the last thread that I recall, Adobe is working on the problem.
Some a private data recovery company has posted in one of threads. Here is a list of some of what has been happening in the Adobe Premiere Elements Forum on this matter....
http://helpx.adobe.com/premiere-elements/kb/keyframe-h-142-error-opening.html
https://forums.adobe.com/message/6823329
https://forums.adobe.com/message/6849013
https://forums.adobe.com/thread/1609903
ATR
Similar Messages
-
I have just got this error on my Windows 8.1 PC in Adobe Premiere Elements 13:"Premiere Elements has encountered an error" --> [c:\adobe\pre\main\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]. I have found different solution on how to fix it, but it's still hard to find where to change "," to ".". When I try to change my .prel file to a .xml it all shows symbols, letters and numbers, not only numbers like a have seen others. I have a LLOOONNNGGG movie to fix. Can anyone help?
Hoerup
Thanks for the update. Sorry that the news was not better.
There are several cases of keyframe error 142 being reporting, some for version 12 and some for version 13.
In your case, we may be able to get some help from Adobe via its Adobe Chat since you have purchased, registered, latest version
Premiere Elements.13. Let us see what Adobe Chat can do for us. Please click on the following link
Contact Customer Care
Premiere Elements
Premiere Elements
Adobe ID, Signing In
Adobe ID, Sign In, Account Help
Chat Panel
If the link does not hold its set, then you will need to navigate to Chat Panel using the above links.
As of a moment ago, the Chat Panel was seen to be active. The titles are not ideal, but they do lead
to an active Chat Panel. I am hoping that the representative whom you reach can answer your question more
fully or transfer you to an Adobe group which can.
We will be watching for further developments.
Best wishes
ATR -
A keyframe h-142 error appears when opening a archived project in Adobe Premiere Elements 10
Whe I tryed to open a archived project in Premiere Element 10 a popup turned up with the message "Premiere Elements has encountered an error <pad>\keyframe\keyframe.h-142.
The project doesn't open.
Can anybody help me, to resolve this error. Is a patch avallable?Stantonc
There is an Adobe document that deals with this specific error message.
Have you seen it and tried it?
http://helpx.adobe.com/premiere-elements/kb/keyframe-h-142-error-opening.html
Please check it out and then let us know if that worked for you.
Thanks.
ATR -
Premiere Pro has encountered an error - Keyframe.h-142
Hello,
My project is crashing each time I try to open it with the error :
Premiere Pro has encountered an error
[c:\randall\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]
If I use an auto-save project it open normaly but I cannot do a save because the saved project will give me the error.
What can I do. It seems that I'm not alone with this problem but I have not found any solution.
Please Help!
NikhoAs this bug in always present in the CS4 version (16/12/2009). I'm sharing my way to restore the project:
Note that I'm using NotePad++ to edit the project file.
FIRST
Replace all:
<StartKeyframe>-91445760000000000,0,,0,5,0,,0,,0,,0,</StartKeyframe>
With:
<StartKeyframe>-91445760000000000,0,,0,0,5,,0,,0,,0,</StartKeyframe>
NEXT
Edit your OS regional settings and change you decimal separator from comma (,) to dot (.) as this bug is always there too (you will see it again when Adobe Encoder will launch the headerless Premiere and crash with the same error).
And finally try to reload your project.
Note about this:
Some data will be changed to incorrect values in your project, like "Opacity" for Title elements, or "Gain" for some audio tracks...
My message to the developer team:
First, you are not god and your coding is not perfect so please use try-catch things that exists today in every languages, it's amazing to see a software like this crashing. Secondly, why the hell removing a node element of the project file avoid the loading of the entire project ??? And finally don't tell me that I'm the ONLY user in Europe that is using comma as a decimal separator -
Elements 10 Error: d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142
Hi all,
have spent my hole day at my brother but still no idea what this error could be. After having this project in APE 8.0 and editing it now with the newly bougt Verion 10.0, everything was fine... Opened and saved it several time but today there were suddenly problems: Even a complete new project with the same material and same cut is now broken after having saved and exportet it....
When we are trying to open the project, we're getting the error:
"Premiere Elements has encountered an error.
[d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]
CONTINUE
And in the next window:
Project could no be loaded. It's damaged oder has old elements (not same words, cause my brother is using the german version)
I have tried everything so long: new installation, opening the damaged project on another computer with ELements 8.0 (identical error also there), deleting cahe, deleting Prefs, loading Auto-Backup (also damaged) and so on... Another "Test-Project" I have created with 2 clips is working fine.... I have no idea what to to else... The project is just a "normal" HD project with 20 Minutes and 20 Clips...
Everything on google (about 8 sites) I have tried - no success until now... :-(
so: any ideas???
Thanks a lot!
MichaelThanks Steve,
but that's exactly what I did.
I applied SetAdMichael solution first
and after RainerBl solution
and after cloud565 solution
and even several times each. I thank them for their work.
I will completely recreate my project, if I have the same problem again I will choose, with regrets, another video editing software. Indeed Adobe seems unable to explain and fix this bug. Adobe Premieres Element 10 is not sufficiently reliable to be used resulted seriously.
It is unacceptable to lose the result of a several days, including backups.
I feel like I have been deceived by purchasing this version which ultimately cost me a lot of time and money spent unnecessarily.
Best regards,
Kinou
Balma, France. -
Hi everybody,
I'm using Adobe Premiere CS4 Version 4. 2. 1. 0. At the moment I'm working at a very important film-project. After saving and reopening the *.prproj file the debugmessage "\keyframe h.142" occured. Clicking "Continue" leads to a crash of Premiere. I tried opening the autosavefiles with the same effect. After a long search with google I found out, that a missinterpretation of dots and commas caused this problem. I read about many different workarounds to fix the corumpted data with perl-scripts to change the wrong commas into dots but nothing worked. I tried a solution on http://www.vibait.com/contact.php but I think the problem is, that I'm using Premiere Pro instead of Elements.
I really don't know what to do. The Adobe Support told me, that there is no Support for CS4 anymore. Thanks Adobe!
Did anybody have the same problem, or even better knows how to solve it?Hey guys,
after wasting a lot more time I finally got it. Here is what I did. I found this discussion:
Hi Rainer,
that's it - everything is working... What have I done?
I used both (!!) scripts from cloud565 with the following command lines via cmd:
C:\Perl64\bin>perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" D:\We.prel >D:\We1.prel
C:\Perl64\bin>perl -p -e "s/([-0-9]+?)\.([0-9]{12,24});([0-9]{15})/$1.$2,$3/g" D:\We1.prel >D:\We2.prel
Note: C:\Perl64 is the install path of pearl, We.prel is the damaged existing initial project. We1 and We2 are going to be created by the script.
Then I opend We2.prel in notepad++ and followed the instructions of Rainer, but just 2 of them:
search for ,< and replace by .<
search for 0,5 and replaxe by 0.5
And that was all I had to to - after this PE10 was able to open the projects, I didn't have to replace other lines / expressions like Rainer.
So glad that the projects are working again, thanks all of you for helping us and leading us to the solution!
Cheers!
Michael
I did everything up there. Aditionally I search once again in the document after ",," and replaced it with ".,". I think you have to handle the renaming of "0,5" to "0.5" with care because there could be numbers like "...94835,0,0,...". This of course doesn't mean
"...94835.0,0,...".
After doing all that stuff I restarted my system. And in the end that was the final issue, at least in my case.
Hope that will help others who were victims of Adobes horrible Support.
Michael -
Premiere Elements has encountered an error. D:\pre-\mediafoundation\api\inc\Keyframe/Keyframe.h-142
Hi
I have seen the discussions about this bug and how you might fix the coding errror in .prel file with help of editing with or without all the tools helpful people provide. http://forums.adobe.com/message/4155936
These posts are however pretty old and the fixes doesn´t seem to work all the time so I wonder if there is any official bugfix to download? I mean it is a very severe bug - catastropical indeed and I have a very important project to deliver. I fear running into this bug once again. I have already lost one day of production time.
I got my version 10 installed a month ago and the bug is still there. Yes we use "," instead of "." when specifying numbers
ThanksI assume you have the software installed in a non-English locale. If none of those fixes (perl command, web link etc.) worked for you, I think the best solution is to get Premiere Elements 12. We did hear a lot these issues in PrE10, but none in PrE11 and none so far in PrE 12, so they must have fixed it.
Retrieving that older corrupt project will really be a futile exercise though. Even if you open it, the perl commands might have only allowed you to open it and I am not sure how much it corrupts the content. (Removing keyframes etc.) If you have a working project, I suggest you take a copy of that right now because you are right that the results can be catastrophical if not fixed. You can do one of the following:
1. Uninstall the software and reinstall it, this time in English. None of the users had this reported in English AFAIK. You should be able to complete the project this time hopefully. This has not been tried in any of the earlier posts, but seems logical enough to give it a try.
2. Open it in a later version of Premiere Elements and you should be good to go. But you will have to buy the software, rather than use it in Trial mode because the Trial version applies watermarking on the clips (That's a visible mark on the clip that says "Adobe Premiere Elements Trial").
I never like to give the "Buy the newer version" as a solution, but this case could just be an exception...
Good Luck! -
I have created a project in Premiere Pro CS5 and saved it for rendering later in Adobe Media Encoder. And now that project file does not open at all. However the other older projects still do open up. Instead, I get this error(I'm attaching a picture):
And this is the error that I get when I try to render through Adobe Media Encoder:
And here is a partial error message that is displayed at the time of crash:
Process:
Adobe Premiere Pro CS5 [902]
Path:
/Applications/Adobe Master Collection CS5/*/Adobe Premiere Pro CS5.app/Contents/MacOS/Adobe Premiere Pro CS5
Identifier:
com.adobe.AdobePremierePro
Version:
5.0.4 (5.0.4)
Code Type:
X86-64 (Native)
Parent Process: launchd [236]
Date/Time:
2012-05-09 14:27:22.140 -0500
OS Version:
Mac OS X 10.7.3 (11D50b)
Report Version: 9
Interval Since Last Report:
420943 sec
Crashes Since Last Report:
-44
Per-App Interval Since Last Report: 104610 sec
Per-App Crashes Since Last Report: -3
Anonymous UUID:
121AE9D6-9F73-4815-9DC7-BA1798DD94BF
Crashed Thread: 19 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
objc[902]: garbage collection is OFF
Does anybody have an idea as to what would cause this? Any help is greatly appreciated. I can clarify for more information if needed.
ThanksIt may be some corrupt keyframe data in the file. Give Project Repair a try with the default settings. If that doesn't work, try selecting the option to strip keyframes:
http://www.digitalrebellion.com/promaintenance
(note: I am the developer of this app) -
Pe 13 debug event keyframe error h-142
When I open my previously saved and working project, I get a Debug Event with a keyframe h-142 message (see below).
The workaround proposed in adobe help under Keyframe.h-142 error | Opening projects does not work. I guess because PE13's .prel files are not in plain text format as PE12 and previously, therefore the workaround with perl will not deliver the required results.
Same issue with ALL backup files of this project...
Any suggestions?I was able to fix the file with the information from post Re: Elements 10 Error: d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142
Here are the steps I performed:
1) rename my corrupt.prel file to corrupt.zip (when opening the file in notepad++, I saw a lot of gibberish and thought the file might be zipped, which it is. I am not sure whether this is only the case in PE13).
2) unzip the corrupt.zip and rename it to corrupt2.prel
3) download perl and run the following commands:
C:\Perl64\bin>perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" corrupt2.prel >corrupt3.prel
C:\Perl64\bin>perl -p -e "s/([-0-9]+?)\.([0-9]{12,24});([0-9]{15})/$1.$2,$3/g" corrupt3.prel >corrupt4.prel
4) Open the file in notepad++ and
search for ",," and replace it by ".,"
search for "0,5" and replace it by "0.5"
and save the file
There, that did it for me. The fixed file does not have to be zipped again for it to open in PE13. -
Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
Hello everybody,
I just ran into this extremely annoying problem:
Premiere Pro CS6 cannot load my project anymore. It gives the following error message:
Premiere Pro has encountered an error.
f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
My autosave files all refuse to open giving another error
..\..\src\TickTime.cpp-364
When i press continue it says the project might be damaged or contain outdated elements.
I do not know what that means...
I do not know what i did last before the problem started, except for adding some layers (lightstreaks) rendering the file and then stopping that thinking "I'll do it later"
What a mistake. The projectfile didn't open anymore when i got home. All my autosaves now give similar errors.
I got warpstabilizer on some clips but would gladly give that up if there was a way to open these files. I cannot import them to a new project. Essentially the files refuse to open in any possible way.
You can find my latest projectfile here: jajageweetmaarnooit.prproj - Google Drive
I am desperate, this movie needs to be delivered tomorrow and i have to start all over.I even tried to transfer my project to a different computer, but still the same problem.
From what I understand form my google-searches, this error might be related to 'Regional Settings' and Keyframes, where decimal separators "." got replased by "," on non-Eglish Windows systems.
I've tried the solution suggested on some adobe help-page:
Solution
Download perl from http://www.activestate.com/activeperl/downloads.
Run the following command using command prompt on your computer:
perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" damaged.prproj >newfile.prproj
Replace damaged.prproj with the path of the prproj file that you are trying to open. For example, you are trying to open picnic.prproj saved to the Picnic folder of your computer's C drive. The path in this case is C:\Picinic\picnic.prproj.
Replace newfile.prproj with the path where you want the new file created. For example, if you want to create the file in the same location, use C:\Picinic\picnic1.prproj.
You rename the file to avoid conflict arising due to similar filenames in the same folder.Using the above example, the command is:
perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" C:\Picnic\picnic.prproj >C:\Picnic\picnic1.prproj
And I've even tried uploading my file to this page, with no luck: http://www.vibait.com/software/premiere-fix-keyframe.h-142/
Some people are suggesting to open up the project file in a textedior to change the ',' and '.' manually. But I found this to time-consuming as I don't know which commas to keep and not.
Paying € 250 or more to "Recovery for Adobe Premiere Projects with Error" is not an option.
But as mentioned, I've already started this project over once, and would not like to do it again, only to run into the same problem. -
I have encountered a bug in Premiere Elements 10.0:
I was editing a movie project, saved it, exited Elements, then tried to reopen it and got the error message
Premiere Elements Debug Event
Premiere Elements has encountered an error:
[d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]
Looking at my history of auto-saves, I found that the three most recent auto-saves showed the same error, the fourth one could be opened OK. That version was at the state of the project I had before starting to add DVD menus to it.
Looking further at the project files (prompted by this forum entry: http://forums.adobe.com/message/4038119 and the strange solution proposed by it: using Perl to replace certain commas with dots), I found a striking difference between the last working and the first non-working solution:
In the file that couldn't be opened, all decimal numbers in <StartKeyframe> and <Keyframe> tags had been saved incorrectly.
For example, a line like
<StartKeyframe>-91445760000000000,1.,0,0,0.,0.,0.,0.</StartKeyframe>
had become
<StartKeyframe>-91445760000000000,1,,0,0,0,,0,,0,,0,</StartKeyframe>
Obviously, PE was using the current locale's (Germany) settings for the decimal point (which is a comma) to save those values instead of the dot it needed to be able to reopen the file.
So I first tried the solution in the above post, but I found that the regex provided there didn't catch all the incorrect commas. I tried it again with the regex
s/,(?=[,<]|\d{10})/./g
replacing every comma that was either followed by another comma or an opening angle bracket or a decimal fraction (all of which are > 10 digits) with a dot.
This looks like it fixed this problem (at least now there were no differences in the decimals between those two versions when I compared them with Beyond Compare), but the file still refused to open (with the same error message). Of course there are still >2100 differences between the two files (there are about 20 minutes of editing between them), but after looking at about 100 of those, I didn't find anything that looked suspicious (at least nothing in the vicinity of "keyframes"). But of course I don't know if I'm looking for the right thing.
So is there any way to check for other errors that make the file invalid? Any hints?
Also, how come this bug is still there (it looks like it exists since PE 8)?
Thanks and best regards,
TimAh, drat. Posted too soon: I have "fixed it"! On the other hand, maybe others can profit from this solution:
What I had overlooked: There appears to be one case where a decimal number has less than 10 decimal digits, and that's when that decimal number is 0.5. (I'm worrying a bit that there might be other exceptions, but I haven't found any in my files).
So, the following solution worked for me, allowing me to open the project successfully:
Using a decent text editor (one that supports regular expressions with lookahead assertions, for example EditPadPro or UltraEdit (when setting it to Perl regex mode), search for
,(?:(?=[,<]|\d{10})|(?<=\b0,)(?=5\b))
and replace all with a single dot (.)
This regex searches for a comma that is either followed by another comma, an opening angle bracket, a decimal fraction of at least 10 digits, or the number 5 (but only if that comma is preceded by the single digit 0).
This allows me to open the project again. However, as soon as I save it again, the file gets corrupted again.
Interestingly (and possibly related), when I try to open the (repaired) file, a PE information window appears ("PE is updating a component. Information is being transmitted..." or something like that in German) and a Windows 7 UAC dialog pops up, asking me to allow the Windows Regserver to modify my system. It doesn't matter whether I allow or deny that request (which appears twice in succession, by the way), as soon as I save the file again, it's corrupted.
The commands that are asked to be executed are:
C:\Windows\System32\regsvr32.exe /s "C:\Program Files\Adobe\Adobe Premiere Elements 10\mc_dec_mpa_ds.ax" "C:\Program Files\Adobe\Adobe Premiere Elements 10\mc_dec_mp2v_ds.ax"
and
C:\Windows\SysWOW64\regsvr32.exe /s "C:\Program Files\Adobe\Adobe Premiere Elements 10\32\mc_dec_mpa_ds.ax" "C:\Program Files\Adobe\Adobe Premiere Elements 10\32\mc_dec_mp2v_ds.ax"
But at least I can now re-open that file after "fixing" it.
Still it would be nice if Adobe could fix this problem. Is this the right place where Adobe technicians will read it and act on it, or do I have to do something else?
Some system information: Windows 7 Pro 64bit with all current patches, 64-version of PE 10.0 installed.
Cheers,
Tim -
Unexpected severe error in Jdeveloper opening a toplink project
Folks,
I'm getting the following errors trying to open a Toplink project on Jdev 11.1.1.2
Could you please advice ?
Thanks,
Gustavo.
oracle.javatools.db:Jun 25, 2010 11:44:38 AM oracle.javatools.db.marshal.DBObjectSAXHelper logConversionError
WARNING: couldn't parse XML element: oracle.javatools.db.TemporaryObjectID
oracle.javatools.db:Jun 25, 2010 11:44:38 AM oracle.javatools.db.marshal.DBObjectSAXHelper logConversionError
WARNING: couldn't parse XML element: oracle.javatools.db.TemporaryObjectID
An error was detected while opening a persistence file.
java.lang.NullPointerException
o.toplink.workbench.addin.mappings.spi.db.JDeveloperTable.getForeignKeys(JDeveloperTable.java:60)
o.toplink.workbench.mappingsmodel.db.MWTable.refreshReferences(MWTable.java:219)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refreshTables(MWDatabase.java:1182)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refreshRelations(MWDatabase.java:1142)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refresh(MWDatabase.java:1074)
o.toplink.workbench.mappingsmodel.sessions.MWSessionsProject.initializeDatabases(MWSessionsProject.java:501)
o.toplink.workbench.mappingsmodel.sessions.MWSessionsProject.initialize(MWSessionsProject.java:487)
o.toplink.workbench.mappingsmodel.sessions.MWSessionsProject.<init>(MWSessionsProject.java:153)
o.toplink.workbench.addin.application.SessionsProjectContext.buildTopLinkSessionsProject(SessionsProjectContext.java:63)
o.toplink.workbench.addin.application.SessionsProjectContext.initialize(SessionsProjectContext.java:101)
o.toplink.workbench.addin.application.AbstractTopLinkContext.<init>(AbstractTopLinkContext.java:51)
o.toplink.workbench.addin.application.SessionsProjectContext.<init>(SessionsProjectContext.java:45)
o.toplink.workbench.addin.application.ContextManager.openTopLinkSessions(ContextManager.java:1378)
o.toplink.workbench.addin.application.ContextManager.openTopLinkContexts(ContextManager.java:1327)
o.toplink.workbench.addin.TopLinkProjectChangeListener$TopLinkContextWorker.run(TopLinkProjectChangeListener.java:370)
j.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
j.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
j.util.concurrent.FutureTask.run(FutureTask.java:138)
j.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
j.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
j.lang.Thread.run(Thread.java:619)
An error was detected while opening a persistence file.
java.lang.NullPointerException
o.toplink.workbench.addin.mappings.spi.db.JDeveloperTable.getForeignKeys(JDeveloperTable.java:60)
o.toplink.workbench.mappingsmodel.db.MWTable.refreshReferences(MWTable.java:219)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refreshTables(MWDatabase.java:1182)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refreshRelations(MWDatabase.java:1142)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refresh(MWDatabase.java:1074)
o.toplink.workbench.mappingsmodel.jpa.MWPersistenceProject.initializeDatabases(MWPersistenceProject.java:97)
o.toplink.workbench.mappingsmodel.jpa.MWPersistenceProject.<init>(MWPersistenceProject.java:70)
o.toplink.workbench.addin.application.PersistenceProjectContext.initialize(PersistenceProjectContext.java:75)
o.toplink.workbench.addin.application.AbstractTopLinkContext.<init>(AbstractTopLinkContext.java:51)
o.toplink.workbench.addin.application.PersistenceProjectContext.<init>(PersistenceProjectContext.java:43)
o.toplink.workbench.addin.application.ContextManager.openPersistence(ContextManager.java:1188)
o.toplink.workbench.addin.application.ContextManager.openTopLinkContexts(ContextManager.java:1331)
o.toplink.workbench.addin.TopLinkProjectChangeListener$TopLinkContextWorker.run(TopLinkProjectChangeListener.java:370)
j.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
j.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
j.util.concurrent.FutureTask.run(FutureTask.java:138)
j.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
j.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
j.lang.Thread.run(Thread.java:619)
An error was detected while opening a persistence file.
java.lang.NullPointerException
o.toplink.workbench.addin.mappings.spi.db.JDeveloperTable.getForeignKeys(JDeveloperTable.java:60)
o.toplink.workbench.mappingsmodel.db.MWTable.refreshReferences(MWTable.java:219)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refreshTables(MWDatabase.java:1182)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refreshRelations(MWDatabase.java:1142)
o.toplink.workbench.mappingsmodel.db.MWDatabase.refresh(MWDatabase.java:1074)
o.toplink.workbench.mappingsmodel.sessions.MWSessionsProject.initializeDatabases(MWSessionsProject.java:501)
o.toplink.workbench.mappingsmodel.sessions.MWSessionsProject.initialize(MWSessionsProject.java:487)
o.toplink.workbench.mappingsmodel.sessions.MWSessionsProject.<init>(MWSessionsProject.java:153)
o.toplink.workbench.addin.application.SessionsProjectContext.buildTopLinkSessionsProject(SessionsProjectContext.java:63)
o.toplink.workbench.addin.application.SessionsProjectContext.initialize(SessionsProjectContext.java:101)
o.toplink.workbench.addin.application.AbstractTopLinkContext.<init>(AbstractTopLinkContext.java:51)
o.toplink.workbench.addin.application.SessionsProjectContext.<init>(SessionsProjectContext.java:45)
o.toplink.workbench.addin.application.ContextManager.openTopLinkSessions(ContextManager.java:1378)
o.toplink.workbench.addin.application.ContextManager.openTopLinkContexts(ContextManager.java:1327)
o.toplink.workbench.addin.TopLinkProjectChangeListener$TopLinkContextWorker.run(TopLinkProjectChangeListener.java:370)
j.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
j.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
j.util.concurrent.FutureTask.run(FutureTask.java:138)
j.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
j.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
j.lang.Thread.run(Thread.java:619)
oracle.jps.credstore:Jun 25, 2010 11:44:41 AM oracle.security.jps.internal.credstore.ssp.CsfWalletManager openWallet
WARNING: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.
oracle.adf.share.jndi.ReferenceStoreHelper:Jun 25, 2010 11:44:48 AM oracle.adf.share.jndi.ReferenceStoreHelper getReferencesMapEx
WARNING: Incomplete connection reference object for connection:dndStantonc
There is an Adobe document that deals with this specific error message.
Have you seen it and tried it?
http://helpx.adobe.com/premiere-elements/kb/keyframe-h-142-error-opening.html
Please check it out and then let us know if that worked for you.
Thanks.
ATR -
I have problem in space drive in my windows 8
I have a problem in my space drive , it is decreasing very fast .. every day I am checking the storge of my space drive .. I found it lower than the day before ... I made clean up ... but it did not work very well .. I lost till now more than 30 gb of my
space drive .. I closed the offline sky drive .. but I am still losing
plz find a solution for this problem
I bought a new surface pro 3 .. everything is good .. but this thing is bothering me..
thank you in advanceHoerup
Thanks for the update. Sorry that the news was not better.
There are several cases of keyframe error 142 being reporting, some for version 12 and some for version 13.
In your case, we may be able to get some help from Adobe via its Adobe Chat since you have purchased, registered, latest version
Premiere Elements.13. Let us see what Adobe Chat can do for us. Please click on the following link
Contact Customer Care
Premiere Elements
Premiere Elements
Adobe ID, Signing In
Adobe ID, Sign In, Account Help
Chat Panel
If the link does not hold its set, then you will need to navigate to Chat Panel using the above links.
As of a moment ago, the Chat Panel was seen to be active. The titles are not ideal, but they do lead
to an active Chat Panel. I am hoping that the representative whom you reach can answer your question more
fully or transfer you to an Adobe group which can.
We will be watching for further developments.
Best wishes
ATR -
Debug event prevent opening of project
Hei
Suddenly i am not able to open my project. A "debug event" appears:
Premiere Elements has encountered an error.
[d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]
Its importent for me to open this project.
It worked without problems with the 30-days test version of premier elements. After buying the software, this problem suddenly appears.
why? And how can i fix it?
akka heimaFrom what I have read and understood about this error (keyframe.h-142 error) I can assure you that the error is not because of the contents of your timeline. It has more got to do with how Adobe writes the project files. The prel file. That is the one that gets corrupt and there have been umpteen attempts to correct it through a script, a webpage, manually replace some entries etc. but nothing has a 100% fix for all the projects encountered.
We just have to pray that Adobe understands this and provides a fix. It is upto them alone to fix. The only thing I see common in all the cases that I have read through in various forums is that the machine language/installation language is not English. One of the forums was a Premiere Pro forum and there was one post that was 4 years old. So it just seems that it is a problem that Adobe knows but just does not Want to fix/ or know how to fix. Thet should certainly be aware of this. Hope they are because this thread is only growing in all the forums and in Premiere Elements' case it has only surfaced in the latest release, PrE10.
So to summarize, this is my understanding:
1. Only seen in Non-English
2. Been there a long time - (4+ years in Premiere Pro and ~6 months in Premiere Elements)
3. Happens in Premiere Pro (so PrE is not the only product affected).
4. Only project file gets corrupt (because recovery on this alone has worked for some)
5. Has something to do with a comma (,) and dot (.) separator in the project file
6. Happened in some cases where a previous version project was opened.
7. Some say it happened aftyer a render was done and project reopened in the same version.
8. No common steps in any of the reports thus far, to get to this error.
If I were you, I would just complete the process and log a bug in their database and wait for Adobe to finally hear us..
My mistake - Premiere Elements has also thrown this error 5 years back!!
http://www.clubic.com/forum/logiciel-multimedia/bug-dans-adobe-premiere-elements-id404804- page1.html
Message was edited by: VDOSurfer -
Kann laufendes Projekt nicht mehr starten?
Hallo, ich hoffe, Jemand kann mir bei meinem Problem helfen?! Ich habe heute erstmalig ein längeres Projekt ausprobiert, in Premiere Elements 1ß Hierbei habe ich HD-Videos und Digitalfotos zu einem Film "verknüpft. Unterlegt mit mp3-Musik. Hat alles bestens funktioniert. Abgespeichert ist das Projekt unter Luafwerk E (PC ist Win7 Home Premium). Da ich noch nie zuvor eine DVD mit dieser Software erstellt habe, dachte ich mir ich mache das mal probehalber vor Ende des Projektes. Die DVD wurde erstellt, läuft einwandfrei. Später habe ich den PC neu gestartet, jetzt kann ich das Projekt nicht mehr öffnen? Es kommt die Fehlermeldung:
"Premiere Elements has encountered an error. [d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]"
Dann wird das Projekt abgebrochen....
Kann mir Jemand weiterhelfen?
Ich wäre sehr dankbar...
Mit freundlichem Gruß,
DocBBjHallo Old Alf,
hat leider nicht geklappt. Ich hatte allerdings auch das automatische Speichern deaktiviert und immer wieder zwischendrin von Hand gespeichert…
Dieser Speicherort ist dann ja wohl der „Haupt-Speicherort“ (den ich selber vergeben habe)?
Gibt es vielleicht noch irgendwo einen Ordner, wo das Programm eigenständig zwischenspeichert?
Den Ordner, den Du beschrieben hast, habe ich in dieser Form nicht gefunden.
Wäre der in den Installationsordner zu finden (bei mit auf c: \ (dort sind die Ordner alle englisch…, könnte also anders heißen?), oder meinst Du den Ordner,
den ich selber als Speicherordner angelegt habe (dort ist - wie gesagt – leider nichts zu machen…)
Vielleicht sonst noch eine Idee?
Nochmals danke!
Gruß, docbbj
Von: OldAlf [email protected]
Gesendet: Sonntag, 22. April 2012 09:07
An: DocBBj
Betreff: Kann laufendes Projekt nicht mehr starten?
Re: Kann laufendes Projekt nicht mehr starten?
created by OldAlf <http://forums.adobe.com/people/OldAlf> in Deutsche Foren - View the full discussion <http://forums.adobe.com/message/4352325#4352325
Maybe you are looking for
-
If I just wanted to play games and surf the web, would a VGA adapter or an AV adapter be better? For my iPad 2? I asked my family for a VGA adapter for Christmas and I'm not too sure if it's the one I want. Also, what is the difference?
-
My daughter has sent me photos to my iPad mini, when I go to messages it crashes, probably too much data, what can I do?
-
Hi, I work on a second hand macbook pro running on 10.9 and now want office for mac on it, additionally to the sofware I already have. On my old macbook I had office 2004 and since I still have two product codes unused was hoping these can still be u
-
i need some help. im getting error -69 when trying to sync my ipod. i dont kno what to do. ive tried googling as much info as i can on this subject but i cant seem to find a answer to get me off to a good starting point. i back all my music up on a e
-
Solaris upgradaion from 6 to 8
Hi , can any one help me to proceed solaris 8 pre upgradation and post upgradation rules to be performed . Thankx for the help. konda