Directory Registry.cpp-283 error

I am attempting to open Premiere Pro cs6 and am now receiving this error message - [/Volumes/BuildDisk/builds/mightykilt/shared/adobe/MediaCore/ASL/Foundation/Make/Mac/../. ./Src/DirectoryRegistry.cpp-283]
I have searched online and through my computer. From what I have read there is some sort of path that is not connecting, but I cannot figure out how to "re-connect" or find the right pathway.
Please help.

There could be a number of issues going on, most of them related to your operating system.
Which operating system are you using? Have you manually gone to Windows Update to ensure you have even the non-critical updates for your system?
When did you last run maintenance on your computer? An easy way to do this is with Advanced System Care, a free program that fixes a number of things on your computer and cleans off temp files and malware with a single click or two.
http://www.iobit.com/advancedsystemcareper.html
If the problem only occurs when you try to open a project, the problems could be related to your source video.
Also, you should absolutely NOT try to open one of your version 3 projects with version 8.

Similar Messages

Cpp-283 error on newly installed PE8

I have uninstalled PE3 which I have been using for years, and installed PE8.
First time I try to run it I get the error message something-or-other Directory Registry cpp-283.
I have searched the forum and see there are other posts about this but my head is spinning with all the technospeak.
Can anyone suggest how I proceed here?
I know I probably need to check my computer settings but even that leaves me a bit confused.
Sorry to be such an airhead!
Have had great help here in the past so thanks for bearing with me.

There could be a number of issues going on, most of them related to your operating system.
Which operating system are you using? Have you manually gone to Windows Update to ensure you have even the non-critical updates for your system?
When did you last run maintenance on your computer? An easy way to do this is with Advanced System Care, a free program that fixes a number of things on your computer and cleans off temp files and malware with a single click or two.
http://www.iobit.com/advancedsystemcareper.html
If the problem only occurs when you try to open a project, the problems could be related to your source video.
Also, you should absolutely NOT try to open one of your version 3 projects with version 8.

[..\..Src\DirectoryRegistry.cpp-283] error when starting Premiere Elements

This error only happens when the laptop is disconnected from our domain. When trying to start Elements I receive error:
Premiere Elements 8.0 has encountered an error.
[..\..Src\DirectoryRegistry.cpp-283]
Then program will not start unless I connect the laptop to the network - which makes a portable laptop useless.
I have uninstalled and re-installed the program with the exact same results.
Anyone got any dieas?
Thankyou in advance.
Crash log file has been included
<?xml version="1.0"?> <!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown"> <time year="2009" month="11" day="19" hour="11" minute="51" second="20"/> <user guid="323c9019-64a6-4b68-8502-a51259f444ab"/> <system platform="windows" osversion="5.1.2600 SP 3.0" applicationlanguage="English (United States)" userlanguage="en_AU" oslanguage="en_AU" ram="2035" machine="Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz" model="x86 Family 6 Model 23 Stepping 10" cpuCount="2" cpuFreq="2394 MHz" busFreq="" locale="English (Australia)"/> <crash exception="EXCEPTION_BREAKPOINT" instruction="0x0097df10"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0x0097df10" symbolname="dvacore::debug::DVA_DebugBreak"/> <stackStatement index="1" address="0x00a0123a" symbolname="dvacore::utility::ThreadSafeMessageDialog"/> </thread> </backtrace> <registerSet> <register name="EAX" value="0x00000000"/> <register name="EBX" value="0x00000000"/> <register name="ECX" value="0x00000000"/> <register name="EDX" value="0x00000000"/> <register name="ESI" value="0x00a0103e"/> <register name="EDI" value="0x00000000"/> <register name="ESP" value="0x00000010"/> <register name="EBP" value="0x00000008"/> <register name="EIP" value="0x00000000"/> <register name="EFL" value="0x00000246"/> </registerSet> <binaryImageSet> <binaryImage start="0x00400000" end="0x00519000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements 8.0.exe"/> <binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/> <binaryImage start="0x7c800000" end="0x7c8f6000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/> <binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6001 .22319_x-ww_f0b4c2df\GdiPlus.dll"/> <binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/> <binaryImage start="0x7e410000" end="0x7e4a1000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/> <binaryImage start="0x77f10000" end="0x77f59000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/> <binaryImage start="0x774e0000" end="0x7761d000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/> <binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/> <binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/> <binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/> <binaryImage start="0x77a80000" end="0x77b15000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/> <binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/> <binaryImage start="0x773d0000" end="0x774d3000" type="__TEXT" path="C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_ 6.0.2600.5512_x-ww_35d4ce83\comctl32.dll"/> <binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/> <binaryImage start="0x10000000" end="0x1013c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/> <binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x -ww_6b128700\msvcp80.dll"/> <binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x -ww_6b128700\msvcr80.dll"/> <binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/> <binaryImage start="0x00350000" end="0x00361000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/> <binaryImage start="0x00370000" end="0x003f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/> <binaryImage start="0x7c9c0000" end="0x7d1d7000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/> <binaryImage start="0x00530000" end="0x005d3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/> <binaryImage start="0x771b0000" end="0x7725a000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/> <binaryImage start="0x77120000" end="0x771ab000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/> <binaryImage start="0x005f0000" end="0x008fb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/> <binaryImage start="0x5b860000" end="0x5b8b5000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/> <binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/> <binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/> <binaryImage start="0x4d4f0000" end="0x4d549000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/> <binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/> <binaryImage start="0x00910000" end="0x0091f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/> <binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/> <binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/> <binaryImage start="0x00930000" end="0x0093f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/> <binaryImage start="0x00950000" end="0x00aa4000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/> <binaryImage start="0x00ac0000" end="0x00b4c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/> <binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/> <binaryImage start="0x00b60000" end="0x00b66000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/> <binaryImage start="0x00b80000" end="0x00b96000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/> <binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/> <binaryImage start="0x74720000" end="0x7476c000" type="__TEXT" path="C:\WINDOWS\system32\MSCTF.dll"/> <binaryImage start="0x01a20000" end="0x01abd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/> <binaryImage start="0x01ee0000" end="0x01f17000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/> <binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/> <binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/> <binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/> <binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/> <binaryImage start="0x01f30000" end="0x01f50000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/> <binaryImage start="0x01f60000" end="0x01f6b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\WS.en_US.DLL"/> <binaryImage start="0x02080000" end="0x02103000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeUpdater.dll"/> <binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/> <binaryImage start="0x605d0000" end="0x605d9000" type="__TEXT" path="C:\WINDOWS\system32\mslbui.dll"/> </binaryImageSet> </crash> <reproSteps> </reproSteps> </crashreport>

Where, and how, is PrE installed? When you launch it, are you running as an Administrator?
First, PrE wants to be installed competely on the C:\ and wants direct access to the My Documents folder. It also wants to be both installed and then launched from an Administrator account.
It is not designed (nor is the big-brother PrPro) to function in a fully networked environment. It will extract media, etc. from an NAS, or from a mapped networked drive, but it does not like to run under most networked environments.
It's my guess that there is something in this installation that it is not comfortable with. More details will likely help.
Good luck, and looking for the answers to the questions above.
Hunt

[..\..Src\DirectoryRegistry.cpp-283] Error on Startup

This error only happens when the laptop is disconnected from our domain. When trying to start Elements I receive error:
Premiere Elements 8.0 has encountered an error.
[..\..Src\DirectoryRegistry.cpp-283]
Then program will not start unless I connect the laptop to the network - which makes a portable laptop useless.
I have uninstalled and re-installed the program with the exact same results.
Anyone got any dieas?
Thankyou in advance.
Crash log file has been included
<?xml version="1.0"?> <!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown"> <time year="2009" month="11" day="19" hour="11" minute="51" second="20"/> <user guid="323c9019-64a6-4b68-8502-a51259f444ab"/> <system platform="windows" osversion="5.1.2600 SP 3.0" applicationlanguage="English (United States)" userlanguage="en_AU" oslanguage="en_AU" ram="2035" machine="Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz" model="x86 Family 6 Model 23 Stepping 10" cpuCount="2" cpuFreq="2394 MHz" busFreq="" locale="English (Australia)"/> <crash exception="EXCEPTION_BREAKPOINT" instruction="0x0097df10"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0x0097df10" symbolname="dvacore::debug::DVA_DebugBreak"/> <stackStatement index="1" address="0x00a0123a" symbolname="dvacore::utility::ThreadSafeMessageDialog"/> </thread> </backtrace> <registerSet> <register name="EAX" value="0x00000000"/> <register name="EBX" value="0x00000000"/> <register name="ECX" value="0x00000000"/> <register name="EDX" value="0x00000000"/> <register name="ESI" value="0x00a0103e"/> <register name="EDI" value="0x00000000"/> <register name="ESP" value="0x00000010"/> <register name="EBP" value="0x00000008"/> <register name="EIP" value="0x00000000"/> <register name="EFL" value="0x00000246"/> </registerSet> <binaryImageSet> <binaryImage start="0x00400000" end="0x00519000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements 8.0.exe"/> <binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/> <binaryImage start="0x7c800000" end="0x7c8f6000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/> <binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6001.22319_x-w w_f0b4c2df\GdiPlus.dll"/> <binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/> <binaryImage start="0x7e410000" end="0x7e4a1000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/> <binaryImage start="0x77f10000" end="0x77f59000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/> <binaryImage start="0x774e0000" end="0x7761d000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/> <binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/> <binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/> <binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/> <binaryImage start="0x77a80000" end="0x77b15000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/> <binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/> <binaryImage start="0x773d0000" end="0x774d3000" type="__TEXT" path="C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5 512_x-ww_35d4ce83\comctl32.dll"/> <binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/> <binaryImage start="0x10000000" end="0x1013c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/> <binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b1287 00\msvcp80.dll"/> <binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b1287 00\msvcr80.dll"/> <binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/> <binaryImage start="0x00350000" end="0x00361000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/> <binaryImage start="0x00370000" end="0x003f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/> <binaryImage start="0x7c9c0000" end="0x7d1d7000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/> <binaryImage start="0x00530000" end="0x005d3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/> <binaryImage start="0x771b0000" end="0x7725a000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/> <binaryImage start="0x77120000" end="0x771ab000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/> <binaryImage start="0x005f0000" end="0x008fb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/> <binaryImage start="0x5b860000" end="0x5b8b5000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/> <binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/> <binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/> <binaryImage start="0x4d4f0000" end="0x4d549000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/> <binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/> <binaryImage start="0x00910000" end="0x0091f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/> <binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/> <binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/> <binaryImage start="0x00930000" end="0x0093f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/> <binaryImage start="0x00950000" end="0x00aa4000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/> <binaryImage start="0x00ac0000" end="0x00b4c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/> <binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/> <binaryImage start="0x00b60000" end="0x00b66000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/> <binaryImage start="0x00b80000" end="0x00b96000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/> <binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/> <binaryImage start="0x74720000" end="0x7476c000" type="__TEXT" path="C:\WINDOWS\system32\MSCTF.dll"/> <binaryImage start="0x01a20000" end="0x01abd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/> <binaryImage start="0x01ee0000" end="0x01f17000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/> <binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/> <binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/> <binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/> <binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/> <binaryImage start="0x01f30000" end="0x01f50000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/> <binaryImage start="0x01f60000" end="0x01f6b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\WS.en_US.DLL"/> <binaryImage start="0x02080000" end="0x02103000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeUpdater.dll"/> <binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/> <binaryImage start="0x605d0000" end="0x605d9000" type="__TEXT" path="C:\WINDOWS\system32\mslbui.dll"/> </binaryImageSet> </crash> <reproSteps> </reproSteps> </crashreport>

I noticed that your problem is happening when you are starting Premiere Elements. So I recommend that you post your question on the forum specifically for Premiere Elements at
http://forums.adobe.com/community/premiere/premiere_elements

Adobe Premiere Elements 10 Error 1 or [..\..\Src\DirectoryRegistery.cpp-283.

I installed Adobe Premiere Elements 10. When I double click on the shortcut icon , I get configuration error 1 which tells me to uninstall/reinstall and then contact Adobe support if it happens again. Uninstalling/reinstalling did not resolve problem so I contacted Adobe support. First time spent about 45 minutes on hold while the person consulted with other colegues and was then disconnected. After waiting about 1.5 hours for call back, I recalled. After about 30 minutes on hold was told that I should call a different number and pay $39 and I could talk to someone who might be able to help me but that this support line did not support this type of problem. Went to online support. Was told to add a new password protected user account, uninstall/reinstall and try to open program using new user account. No joy. Present status : If I double click on shortcut icon, get configuration error 1. If I rignt click and try to 'run as current user get 'debug error [..\..\Src\DirectoryRegistery.cpp-283. If I 'run as the password protected user account get configuration error 1. Note that during the first call, I was sent an email with a 'case number' and a link to check status but the case number has never showed up on the adobe website. Questions:
1. Any suggestions to resolve problem?
2. If I pay the $39, is it likely that I will get the problem resolved or simply get the same run around? I have now uninstalled/reinstalled/restarted at least 6 times and there have really been no other suggestions from Adobe.
3. Suggestions for alternative video editing software if I can't ever get Adobe to boot up. Thanks for your support.

You will find best advice over on the video forum. Most of us here are photographers.
Click on the link below and copy and paste your question again. Good luck.
Video questions: Click here for Premiere Elements Forum

On my Mac, after the installation i get this error when i start - Premiere Elements 13.0 has encountered an error. [/Adobe/pre/main/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283] any ideas how to fix this

On my Mac, after the installation i get this error when i start - "Premiere Elements 13.0 has encountered an error. [/Adobe/pre/main/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283]"
any ideas how to fix this, i don't know or haven't faound out how to contact Adobe supporet....

Here's the contact link for Adobe support. It's just three clicks from the site's home page.
Contact Customer Care

Premiere Pro CS5.5 startup error. (DirectoryRegistry.cpp-283)

When i start up Premiere Pro CS5.5 on my iMac with OSX Lion it immediately shows this error:
Premiere Pro has encountered an error.
[/Volumes/BuildDisk/builds/Mulder64/shared/
adobe/MediaCore/ASL/Foundation/Make/Mac/../../
Src/DirectoryRegistry.cpp-283]
I don't really know what it means but i think it is because premiere can't find a file to start up because it doesn't have the right privileges. (When i login my mac as root user i can start premiere without any problems also in my administrator account with terminal starting it with sudo works without problems).
Did someone had this problem before? And how do i fix the problem?
Thanks in advance, Levi.

I have run into the same problem. I am running a late 2008 MBP with 2 480GB OWC SSD's and 8GB of OWC RAM. I have 10.7.5 installed and am running in 64 bit mode. I get this pop-up when I try to open Premiere or Bridge:
Premiere Pro has encountered an error.
[/Volumes/BuildDisk/builds/Mulder64/shared/adobe/MediaCore/ASL/Foundation/Make/Mac/../../S rc/DirectoryRegistry.cpp-283]
I am the Admin on this computer. I don't know how to give myself more admin rights than I already have? Photoshop starts up without issue.
Any suggestions?
Thank you,
Scott

Premiere elements 10 crashes on startup error DirectoryRegistry.cpp-283

I bought premiere elements 10 yesterday on mac app store and until now i wasnt able to use it.
It crashes on the startup and this error apears.
[/Users/ramyadav/perforce/premiere/elements/molecules/pre10-bullseye/molecule-17/MediaCore /ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283]
Need help with this!
I'm running a macbook pro 13"
mac os 10.7.3
4gb
500gb
thanks

Please report back into this thread, as we can all possibly learn something. This can be very useful, as most of the "regulars" are PC-only users, and only a few are fluent in things Mac. However, even we PC-users, try to learn of fixes for the Mac.
Now, that is not saying that your issue is platform-centric, as it might be a problem that we have just not seen on the PC.
Good luck,
Hunt

CS3 Error [..\..Src\DirectoryRegistry.cpp-283]

Hi, I need your help. After crashing Premiere CS3 I tried to re launch it and this appears [..\..Src\DirectoryRegistry.cpp-283]
Can you please help me?

I noticed that your problem is happening when you are starting Premiere Elements. So I recommend that you post your question on the forum specifically for Premiere Elements at
http://forums.adobe.com/community/premiere/premiere_elements

Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better title

Hi Kevin,
I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
What were you doing when this error started to occur?
          Nothing special I remember. The only thing I do recall, is:
          I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
          Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
          After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
Do you have iCloud installed?
          No.
Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
          It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
Do you have a copy that can be opened in an earlier version?
              An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
Do you get the same error in that earlier version?
               No error here, the file opens properly.
              Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
Did you use any unusual footage types in your project?
     I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
If you remove them, do you still get an error?
              When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
Was the fps interpretation changed in any of the clips?
     Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
If so, restore them to their original fps and see if you still get the error.
              Unfortunately, since I can't open the project anymore, I can't test that.
Did you use Warp Stabilizer?
          No.
Do you have any browser plug-ins?
          What do you call browser plug-in in Premiere?
Are there any third party plug-ins used?
          I have Magic Bullet Looks 2, and I'm using it on this project.
If so, remove the effect from those clips and see if it improves the situation.
              Unfortunately, since I can't open the project anymore, I can't test that.
Some additional infos on my computer.
I use Windows 8.1 (64-bit), all Adobe softwares installed have the last update (for video apps, it's 2014.2)
The language settings are configured in French, but Windows and CC apps are in English.
If needed the 2014.2 project file is here:
https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
Thanks in advance to help us to resolve this weird bug.
Christophe.

.\TixRestore.cpp(71): Error FC060002 - Errors while trying to restore A215-S5807

Bro-in-law wiped HDD and tried to load XP Pro. Didn't work, no drivers. I ordered retore disks. Tried Toshiba Recovery Wizard. Got
Toshiba Recovery Wizard
<Error>
An error has occurred.
ERROR: 03-EEEE-0000
An error has occurred.
Please press [OK] to turn off the computer.
Did -
1. Boot the Recovery disc or HDD image and select System Recovery Options.
2. Follow the prompts until you get to the menu and then select a command prompt.
3. Copy the \zzimages\zzimages directory for all recovery discs to a temp directory on the hard drive (c:\temp).
4. Change to the Bin directory on the first recovery disc and run "tosimagex /apply c:\temp\preinst.swm 1 c:\ /ref c:\temp\preinst*.swm" without the quotes.
(Of course I had to create the c:\temp folder.) I tried without also.
Got -
WIM File: c:\temp\preinst.swm(1)
Dst File: c:\
App Name: /ref
Total Parts: 11
Add splited image: c:\temp\preinst2.swm
Add splited image: c:\temp\preinst3.swm
.\TixRestore.cpp(71): Error FC060002
D:\BIN>
I talked to TOshiba tech support and after going through this for a while. The tech ended up saying that the MBR is messed up and that I needed to buy a new hard drive. I can still access it via command prompt and SYstem Recovery. I booted up to DOS prompt with a WIN98 CD and did FDisk and format. Still got error. Tried startup repair. Received an "does not have a valid system partition" error.
I booted up to Ultimate Boot CD. Fixed partition problem. Now getting BOOTMGR missing. It has been too long since I worked computer support and do not know what to do to get this fixed. I find it hard to believe that I need new hard drive if I can do all of this with it. Please help.
Thank you.

hi. Here's the answer to your problem i think. when you are copying the zzimages files to the temp folder you have to copy the zzimage files from ALL the restore disks, or you'll get that error message. and you can use the bootrec tool to fix the boot record. here's a link that tells how to do that. good luck. http://support.microsoft.com/kb/927392

Failed to set security on SQL Server registry key. Error: 2

Hi,
I have a Primary site (mixed mode) running SCCM 2007 SP1 for many months now with no issues.
This site is made up of two Win 2008 sp2 servers sharing the SCCM roles:-
SCCM01 - Site server, DP, RP, PXE and SQL2005 hosting the SCCM database
SCCM02 – SUP, MP, FSP, SLP
The SQL2005 on SCCM01 is running under a domain service account called
domain\service_sccm which is also a sysadmin in SQL as is the SCCM02 server.
In an effort to resolve the isse I have made this account a Domain Admin.
I have also used this account to log onto SEC01 to run the Secondary Site installation and to be the SQL Service account.
I'm now trying to add a Secondary Site on a Domain Controller called SEC01 (also Win2008 sp2) and on the same LAN as the SCCM01/02.
This is where I get problems.
I run the installation locally on the Sec Site server (DC) as a Domain Admin and the installation completes OK (all green ticks),
the ComponentSetup.log and Pre-Reqs are all good as well however when I check the ConfigMgrSetup.log I see the below -
Failed to set security on SQL Server registry key. Error: 2.
<11-09-2010 22:46:59> SMS Setup full version is 4.00.6221.1000
<11-09-2010 22:46:59> Successfully set security on Setup registry key.
<11-09-2010 22:46:59> Failed to set security on SQL Server registry key. Error: 2
<11-09-2010 22:46:59> Successfully set security on Identification registry key.
<11-09-2010 22:46:59> Creating SMS Inbox Source registry key ...
<11-09-2010 22:46:59> Installing SMS Site Component Manager ...
<11-09-2010 22:46:59> Installing Site Component Manager under acct <NT AUTHORITY\SYSTEM> path <C:\Program Files (x86)\Microsoft
Configuration Manager\bin\i386\sitecomp.exe>
<11-09-2010 22:47:01> Started Site Component Manager service
<11-09-2010 22:47:01> SMS Site Component Manager installation completed.
<11-09-2010 22:47:01> Done with service installation
Adding the PMP role to SEC01 also fails to install and no MPSetup or MPControl logs are created.
WebDav and win2008 roles, features all added and server fully patched.
Despooler.log on SCCM01 seems good and passing keys.
Tried installing to default path and to shortened path such as C:\SCCM
The new secondary site is listed in the console and an address can be added for the Secondary Site
BITS Server Extensions and Remote Differential Compression Features are enabled.
The Group memberships all appear ok:-
SCCM01
Local Admins
contains the sec site server SEC01, SCCM01, installation accounts
SMS_SiteToSiteConnection_001
SEC01 (the sec site server)
SMS_SiteSystemToSiteServerConnection_001
SCCM02
SEC01
No Local Admins as a DC
SMS_SiteToSiteConnection_002
SCCM01
SMS_SiteSystemToSiteServerConnection_002
empty
SQL 2005
This has the account logged in during installation as a sysadmin
SCCM02 is also sysadmin
The fundamental issue appears to be that the SEC01$ server account is not being added to SQL Logins (and therefore SCCM database Roles)
therefore the installation cannot complete.
I have tried to manually add the SEC01 account to SQL Logins before installation of Sec Site but this did not work.
Not sure if the fact that SEC01 is a DC may be a factor.
Appreciate any help if anyone has seen this before or can suggest a resolution.
Thanks

After a lot of digging around and head scratching I eventually found the resolution.
The original thread title Error turned out to be a bit of a red herring in that my failure to deploy Sec Sites came down to two separate issues seemingly unrelated to the error message of the thread title.
The first part of the resolution was to manually create the SQL Server accounts for the Sec Site Servers and assign them to the smsdbrole_MP DB role to
let the SQL side of the SCCM install complete a s these were not being created automatically.
This then left the fact that that the installation of the Sec Site completed successfully according to the install logs in C:\ however the DP and MP would
never install.
The big clue was eventually contained in the mpfdm.log errors relating to
**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER
and
**ERROR: Cannot find path for destination inbox Asset Intelligence KB Manager on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER
Thankfully the errors led me to these two blogs:
http://myitforum.com/cs2/blogs/scassells/archive/2009/07/20/error-cannot-find-path-for-destination-inbox-sms-amt-proxy-component-on-server-registry.aspx
and
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/5fcc53d4-8629-4b34-9eaa-6cb020eedc13/
As it turned out the SCCM installation registry and folder creation does not complete and I had to manually enter the reg settings as detailed in the
links above to complete the installation. Once I did as described everything worked a treat – all my MPs and DPs are 100% now.
Solutions
Add the following reg keys to each of your effected secondary sites.
Inbox Fix
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\MPFDM\Inboxes]
"Asset Intelligence KB Manager"="E:\\Program Files\\Microsoft Configuration Manager\\inboxes\\AIKbMgr.box"
"SMS_AMT_PROXY_COMPONENT"="E:\\Program Files\\Microsoft Configuration Manager\\inboxes\\amtproxy.box"
Asset Intelligence fix:
Note: you will need to identify the next largest key value.
In my example it was key 49
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Definitions\49]
"Inbox Name"="Asset Intelligence KB Manager"
"Relative Path"="inboxes\\AIKbMgr.box"
"NAL Path"=""
"User Rights"=dword:00000000
"Service Rights"=dword:00000004
"Monitoring Enabled"=dword:00000001
"Location Type"=dword:00000001
"Guest Rights"=dword:00000001
AMT registry Fix.
  Note: you will need to identify the next largest key value.
In my example it was key 50
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox Definitions\50]
"Inbox Name"="SMS_AMT_PROXY_COMPONENT"
"Relative Path"="inboxes\\amtproxy.box"
"NAL Path"=""
"User Rights"=dword:00000000
"Service Rights"=dword:00000004
"Monitoring Enabled"=dword:00000001
"Location Type"=dword:00000001
"Guest Rights"=dword:00000001
Big thanks to Shaun Cassells and John Marcum for these blogs

Regarding Adobe Media Encoder CS4 [../../src/component/component factory.cpp-119] error.

Hi iam using adobe premire cs4 when i finished editing nd tried to xport my video as usual adobe media encoder opened for encoding . i clicked start quere and i recieved this [../../src/component/component factory.cpp-119] error. every time i try to encode this error appears. please help me solve this problem ASAP.

CPU:
Graphics Card and Motherboard
Memory and Ram:
And 250gb of hdd and 115gb free

PProHeadless.exe, FileImporter.cpp-1132 errors exporting short video

Hi,
I'm getting an error when I try and export my 3 minute movie. The error goes as follows:
PProHeadless.exe
AppVer: 0.0.0.0
ModName: dvacore.dll
Mod Ver: 2.0.0.0
Offset: 002de00
Encoding Failed
Error compiling movie
Unknown Error
I tried removing the two clips from the timeline at which it always seemed to crash, and it did export but only as an mp4. I tried re-converting those clips thinking they were corrupted, and still get the error with the new clips. In this same area there are crossfading .jpgs, but they have been sized to 72dpi and are concurrent with the video size, so this shouldn't be the issue, correct?
It also has listed a FileImporter.cpp-1132 error.
I've never had this issue before. I'm running Premiere Pro CS4 on a windows xp machine. Should I be converting these videos to a specific format before using them in the timeline? Right now I'm importing them as mpeg2, after converting them in Media Encoder.
Thanks for your help!
-J

Everyone may have already got what they wanted from the answers given in the post but I thought I'd add my PAL experience of this.
I tried to media export a timeline to one large mixdown file. (blackmagic mjpeg) the timeline had simple premiere titles fading up and down to black before each video module. The media encoder worked fine but none of the dissolves from timeline to title worked - they translated as cuts in the mixdown. In the end I dropped premiere generated black video over the titles and used variable opacity to bring them in and out. This worked fine and proves that you can export with black at the front.
What it proves however is that CS4 really is working differently to CS3 in lots of ways.
As far as media encoder is concered, I'm sure this is a grandmother sucking eggs business but it's critical for performance that the USE PREVIEW FILES option in the settings box is selected. Otherwise CS4 starts to re-render everything and seems to be much slower at doing it than a basic timeline render. Including metadata files doesn't seem to offend too much but I only evr include this when I'm exporting final versions anyway.

Src/Win/WinFile.cpp-754" error

I’m using PPRO in Production Premium CS4.
I’m getting the “Src/Win/WinFile.cpp-754” error” when I AME starts or shortly after it starts. System worked fine since I installed the CS4 upgrade 4 months ago but today a project is due and this happens.
My system: Dell Precision 690, 3Ghz Xeon processor, 4 GB ram, Internal HDs (1) 300 and (1) 400 GB, External HDs (2) 1 TB.
I’ve read and searched the forums and now I’m frustrated and in need of some help. Has anyone found definitive solution to this “Src/Win/WinFile.cpp-754” problem?
Thanks,
Tony

Hi,
I searched the internet with that error mssg and it seems a lot of them have to do with video card drivers. There was some information about matrox drivers and that problem on the internet...
Also some 'Axio' card driver problems related to that error message...
Have you recently updated your video card drivers ?
Rod

Directory Registry.cpp-283 error

Similar Messages

Maybe you are looking for