ImporterProcessClient.cpp-127 Error . Premiere Cs 4 was tun ??

ImporterProcessClient.cpp-127 Error hatte schon  mal jemand dieses Problem ?? habe mastercollection cs 4 installiert !  laüft unter win 7 !
habe kein uptade oder eine sonstige veränderung vorgenommen.
selbst neuinstallation der collection brachte keinen erfolg habe auch clean skript verwendent !
hat noch jemand nen tipp ?? habe schon gegooglt nur zu dem problem gibts 
scheinbar keine vernünftige lösung und vor allem tritts aus den unterschiedlichsten gründen auf....
bei mir kam es wohl im zusammenhang mit bilddateien die premiere nicht  unterstützt, die sind mittlerweile aber raus aus dem projekt u wie  gesagt 2 mal schon neuinstalliert !!!!! 
firewall ist aus und virenschutz gibts auch keinen der stören könnte....
mir fehlt nix mehr ein ausser ein komplette neuinstallation des systems....

Well, the Media Encoder actually works if I choose any video that's NOT in Premiere and want to encode it into something else. Apparently it can't find the media source location. Here is the error message.  Although, I have never changed the location and it has worked fine until I had the previous problem. The only other thing I can think of is that I permanently trashed m prefs folder (*doh* slaps forehead).  Otherwise, nothing has changed and it will not encode anything I exported nor send it to Encore.
Thanks,
Nik
ERROR MESSAGE BELOW:
- Source File: C:\Users\DANIKO\AppData\Local\Temp\New Cat Videos_4.prproj
- Output File: F:\ADOBE PREMIERE PROJECT FILES\DEMO REEL Project Files\Sequence 03.wmv
- Preset Used: NTSC Source to High Quality Download
- Video:
- Audio:
- Bitrate:
- Encoding Time: 01:39:00
3/7/2010 1:14:25 PM : Encoding Failed
Could not read from the source. Please check if it has moved or been deleted.
- Source File: C:\Users\DANIKO\Desktop\Cat Videos (early 2010)\MVI_0901.AVI
- Output File: C:\Users\DANIKO\Desktop\MVI_0901 test.wmv
- Preset Used: NTSC Source to High Quality Download
- Video: 720x480, 29.970 [fps]
- Audio:  96 kbps, 48 kHz, stereo VBR
- Bitrate: Compressed, VBR, 2 Pass, Audiences:1, Avg 1500.00 [kbps]
- Encoding Time: 00:00:10
3/7/2010 1:21:17 PM : Encoding Failed
The Operation was interrupted by user
- Source File: C:\Users\DANIKO\AppData\Local\Temp\New Cat Videos_5.prproj
- Output File: F:\ADOBE PREMIERE PROJECT FILES\DEMO REEL Project Files\Sequence 03.avi
- Preset Used: NTSC DV
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:00:28
3/7/2010 1:21:35 PM : Encoding Failed
Could not read from the source. Please check if it has moved or been deleted.

Similar Messages

  • ImporterProcessClient.cpp-127

    ImporterProcessClient.cpp-127
    Allowed the Premiere update yesterday, and now I'm crashing at start up with the ImporterProcessClient.cpp-127 error.  Someone feel like enlightening me?
    CS4 Premiere Pro
    Windows Vista

    I am having the same issue.  Tried removing prfes.. no luck.  My edit session last for five minutes, then cra
    sh and restart.  So happy.  Thats me over there smiling.  Happy Happy.

  • Windows 8.1, CS4, [..\..\Src\ImporterProcessClient.cpp-127]

    A previous issue for CS4 on earlier versions of Windows has evidently recurred after a recent Windows Security update. Here's one evidently resolved previous instance: Premiere Pro CS4 (Vista) error [..\..\SRC\ImporterProcessClient.cpp-127]
    Is anyone else currently experiencing this issue?
    My own system specs are as follows:
    Windows 8.1
    Processor: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz 2.80GHz
    Installed memory (RAM): 8.00 GB
    System type: 64-bit Operating System, x64-based processor
    I am running Premiere CS4 version 4.0.0
    There have been no issues loading and using Premiere since I installed it on this computer, which was done shortly after a full hard-drive formatting several months ago.
    This morning, Windows requested that I install a security update and restart. Upon restarting, Premiere has refused to open citing the following error:
    Premiere Pro Debug Event
    Premiere Pro has encountered an error.
    [..\..\Src\ImporterProcessClient.cpp-127]
    The workarounds cited for previous version of windows, such reducing UAC settings and running Premiere as administrator are not resolving the issue. Based on the previously mentioned thread, I attempted the following command prompt solution:
    'cd' to C:\Program Files (x86)\Common Files\Adobe\dynamiclink\
    dynamiclinkmanager.exe /REGSERVER
    processcoordinationserver.exe /REGSERVER
    regsvr32 dynamiclinkmarshal.dll
    I received error code 0x80070005, and have followed several Microsoft guidelines for resolving it to. Currently, I remain unable to open Premiere.
    I have deactivated, and am in the process of uninstalling, running Clean Script CS4, and re-installing. I will also be checking for updates, but recent attempts at doing so have indicated none were available. Do updates get taken down over time?

    UPDATE:  While the following information should correct the initial issue reported, a new problem has come up and stopped production yet again.  Premeire  is prompting me to install additional codecs, but the prompt always fails,  and asks me to contact Tech Support. My footage is rendering incorrectly now as well.
    Note that my footage  was editing and rendering just fine before this mess  began.
    FIXED. I think this is the crucial step, but I'll review everything I did afterwards:
    Given that CS4 (via Photoshop, as Premiere is currently not working) seems unable to detect any updates (despite being a fresh installation), and the manual updates seem to all be failing, I found this item about a similar issue for CS3:
    https://helpx.adobe.com/creative-suit/kb/cs3-updater-detect-any-updates.html
    Adobe recomends setting your computer clock back to October 1, 2011, and checking for updates again. It seems to have done the trick, and my CS4 is installing 12 updates.
    ALL STEPS TAKEN:
    I cannot reliably point to any one step as the "definite fix" for this, so here's a review of what I did in the order that I did it:
    1) Deactivate, uninstall, reinstall, reboot.
    2) Lower your User Account Control settings. In 8.1, you can simply run a search in the Start screen for "UAC".
    3) Activate the hidden administrator account for Windows 8.1. Open cmd.exe as administrator. Press Window+X and select the appropriate option, then run the command (with no quotes) "net user Administrator /active:yes".  Once everything has been fixed, you can repeat this and replace "yes" with "no" to hide the admin again.
    4) Log in to the Admin account.
    5) Reset your computer's date to "October 1, 2011". Be sure to set it back to the real date once everything is done.
    6) Open any CS4 program that still opens (as in, not Premiere Pro).
    7) Check for updates. A restart will be required.
    8) As mentioned, you'll want to reset the things you've changed on your computer. Set the UAC to whatever it was before the issue, hide your Admin account, and fix your clock. After doing so and rebooting, my Premiere Pro CS4 continued to function normally on my personal user account.

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

  • Premiere Elements Timecode.cpp-1014 error when adding media

    Software: Premiere elements 11
    Camera: Sony DCR TRV22E
    OS: Windows 7
    When selecting add media I get: [..\..\Src\Timecode.cpp-1014] error multiple times, when the capture window eventually comes up it says the capture device is offline.
    This happens not only when the camera is connected and powered but also when camera is not connected.
    I have tried the different IEEE1394 drivers available in windows 7 and none of them work.
              1394 OHCI Compliant Host Controller
              1394 OHCI Compliant Host Controller (Legacy)
              VIA 1394 OHCI Compliant Host Controller
    The connection to the camera through firewire is ok because I can download video from it using Nero Video Essentials, I just cannot do it through Premiere Elements 11.
    Message was edited by: foradobeuse
    Oops, I put the wrong error code in the title, it should be timecode.cpp-1014

    There is absolutely no reason you can't use this camcorder with Premiere Elements. It's a miniDV! There's clearly something going on with your computer that's unrelated to Premiere Elements.
    For instance, this appears to be a European camcorder. Is your program installed for PAL rather than NTSC? It's an obvious question but one that needs to be asked.
    Also, PLEASE try using the free program WinDV to capture your video over a FireWire connection. If it does,we know something is wrong with your Premiere Elements installation. If not, we know it's something more basic.
    Nero, by the way, it notorious for not sharing certain hardware resources. I've never known it to block access to the FireWire -- but I suppose it's possible.
    So, please, instead of just flipping off Premiere Elements, do a little basic troubleshooting. Problems with a FireWire/miniDV capture are virtually unheard of, and I'm really curious what's going on with your system!

  • [..\..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

  • "No Disk" Error (premiere elements 11)

    I have successfully installed Adobe Premiere Elements 11 on my PC:
         Dell XPS 8300 
         Intel Core i7-2600 Quad Core (3.4 GHz, 8MB Cache)
         • 1GB Radeon HD 6450 Graphics
         • 16GB DDR3 1333 RAM
         • 1TB 7,200RPM Hard Drive (2 x 500GB RAID 0)
         • Windows 7 Home Premium 64-Bit
    When I open the application and click "New Project" I get the following error message:
    AdobePremiereElements.exe - No Disk
    There is no disk in the drive.  Please insert a disk into drive
         \Devices\harddisk2\DR3
    I can "cancel", "try again", or "continue".  The only thing that works is to hit "cancel"  (several times).  Premiere Elements will then open, but the error message will keep recurring.   Adobe Support (Chat) has not been much help.
    Anyone else come across this?  This seems to be a common error in earlier versions (version 9), but I can't seem to find any good solution to it.   HELP!!!!
    UPDATE:   Just as an FYI..while it's possible (but doubtful) there is preloaded software interfering, there is no other software (or viruses) installed on this computer.
    Message was edited by: [email protected]

    Boomps, I installed from here and it worked fine:     http://helpx.adobe.com/premiere-elements/kb/installing-smartsound.html There are even step-by-step instructions.  Good luck.
    Date: Mon, 7 Jan 2013 04:46:21 -0700
    From: [email protected]
    To: [email protected]
    Subject: "No Disk" Error (premiere elements 11)
        Re: "No Disk" Error (premiere elements 11)
        created by BoompsXXX in Premiere Elements - View the full discussion
    Not an answer!! I am new to this. I get the same error message and from what I can gather reading the traffic, I have to reinstall Smart sound. Can anyone help a simpleton. I searched the DVD for all files referencing Smart sount, there is plenty. I don't really understand how I reinstall and what??Any help would be great!!ThanksTara
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4973936#4973936
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4973936#4973936
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4973936#4973936. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Premiere Elements by email or at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Error while installing the WAS 640 SR1 unicode

    Hi,
      When I am trying to install WAS 640 SR1 On windows xp sp2. The following error I am getting. Can you help to fix this issue. I am attaching the trace file.
    SAPinst is getting started.
    Please be patient ...
    guiengine: login in process.
    INFO       2006-08-04 21:35:28 [syxxcfile.cpp:325]
               CSyFileImpl::copy(const CSyPath & q0w9e9r8t7.1.xml, ISyNode::eCopyMode 3, ISyProgressObserver*) const 
    Copying file C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.xml to: q0w9e9r8t7.1.xml.
    INFO       2006-08-04 21:35:28 [syxxcfile.cpp:446]
               CSyFileImpl::copy(const CSyPath & q0w9e9r8t7.1.xml, ISyNode::eCopyMode 3, ISyProgressObserver*) const 
    Copying file C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.xml to: q0w9e9r8t7.1.xml.
    INFO       2006-08-04 21:35:28 [synxcpath.cpp:834]
               CSyPath::createFile()
    Creating file C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\CI\q0w9e9r8t7.1.xml.
    INFO       2006-08-04 21:35:29 [syxxcfile.cpp:325]
               CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.1.xml, ISyNode::eCopyMode 3, ISyProgressObserver*) const 
    Copying file C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.xml to: C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.1.xml.
    INFO       2006-08-04 21:35:29 [syxxcfile.cpp:446]
               CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.1.xml, ISyNode::eCopyMode 3, ISyProgressObserver*) const 
    Copying file C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.xml to: C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_ABAP_ORA_UC/CI/keydb.1.xml.
    INFO       2006-08-04 21:35:29 [synxcpath.cpp:834]
               CSyPath::createFile()
    Creating file C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\CI\keydb.1.xml.
    INFO       2006-08-04 21:35:30 [ianxbusprv.cpp:337]
               CIaNtUserPrivileges::add_impl(., MALLI-01UIT2PDX\malli, SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege)
    Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'MALLI-01UIT2PDX\malli' on host '.'.
    INFO       2006-08-04 21:35:30 [synxcpath.cpp:834]
               CSyPath::createFile()
    Creating file C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\CI\summary.html.
    PHASE      2006-08-04 21:35:30 [iaxxcwalker.cpp:416]
               CDomWalker::printPhaseInfo()
    Prepare the installation program.
    INFO       2006-08-04 21:35:38 [iaxxcwalker.cpp:59]
               CDomWalker::walk()
    Installation start: Friday, 04 August 2006, 21:35:26; installation directory: C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\CI; product to be installed: SAP NetWeaver '04 Support Release 1> ABAP System> Oracle> Unicode> Central Instance Installation
    INFO       2006-08-04 21:35:39 [iaxxbhosts.cpp:434]
               CIaOsHosts::getInfo()
    Host operation t_HostInfo_SHARED processed successfully.
    ERROR      2006-08-04 21:35:56 [syxxsyshlp.cpp:56]
               syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
    FSL-00001  System call failed. Error 1 (Incorrect function.
    ) in execution of system call 'GetVolumeNameForVolumeMountPoint' with parameter (B:\), line (276) in file (synxcfsmnt.cpp).
    ERROR      2006-08-04 21:35:56 [iaxxbmount.cpp:153]
               CIaOsMount::handleMount(PKdbClientTable table, PSyMount const& mount) const
    MOS-01236  Could not determine information about file system MALLI-01UIT2PDX:, mounted at unknown.
    WARNING    2006-08-04 21:35:56 [iaxxccntrl.cpp:477]
               CController::stepExecuted()
    The step GetMountInfo with step key SAPSYSTEM_CI|ind|ind|ind|ind|ind|0|SAPSYSTEM|ind|ind|ind|ind|ind|0|SAPComponent|ind|ind|ind|ind|ind|0|SAPComponent_Waps_System|ind|ind|ind|ind|ind|0|SAPComponent_Waps_Instance_Dirs|windows|ind|ind|ind|ind|0|GetMountInfo was executed with status ERROR.
    SAPinst component stack:
    ========================
      Preinstall|ind|ind|ind|ind|ind|0
    Current script:
    ===============
    var client = ;
    client.keymap["tOS_Mounts"] = "=t_MountPoints_PRIVATE";
    installer.setKdbClient(client);
    var args = new Array();
    var c_hostsCall = ;
    installer.invokeModuleCall(c_hostsCall);
    // Copy Template table
    waps_copy_template_table("tNT_DriveMapping_TEMPLATE", context.get("tDriveMapping") );
    WARNING    2006-08-04 21:36:05 [iaxxcsihlp.hpp:250]
               main()
    An error occurred during the installation.
    Exit status of child: 1
    Appreciate for your quick reply.
    Thanks,
    Mallikarjun.M

    Hi Malisetti,
    This look like a problem with the installation target, seems like somehow the installation can't find or deal with the mounted volumne.
    Are you trying to install WAS in an external device/storage?
    Hope this help!
    Juan
    PS: please reward points if helpful

  • [..\..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

  • 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

  • AudioPrefetch.cpp-87 Error

    Hi everyone, I've been having this error: Src\AudioRender\AudioPrefetch.cpp-87 with Premiere CS5. It happens when I zoom in the timeline past a certain point. Does anyone have any suggestions?

    >AudioRender
    I would suggest you provide project and file DETAILS... actually, LOTS of details
    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

  • How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

    This is a guide to repair projects that get a "TickTime.cpp-290" error after opening a specific project.
    Prerequisites:
    Project repair tool (download link below)
    WinRAR or any file archiver
    Damaged project file
    As an example, let's say the name of my damaged project is 'test.prproj'
    Steps:
    1. Download the project repair tool here: https://www.dropbox.com/s/3fyja0ws7l5gkbt/pp-repair-0.1.35.zip?dl=0
    2. Rename your project file extension from 'test.prproj' to 'test.zip' (a warning appears saying the file might become unusable. Do not be concerned about the warning. Click OK and move to the next step.)
    3. Extract the contents of 'test.zip' to a location on your computer. (Right click on the file and select ‘Extract files’ > Choose a location > Click OK).
    4. Go to the extracted location. Note the file 'test' has no extension.
    5. Rename the file, 'test.prproj'.
    6. Launch the project repair tool, and then select the file 'test.prproj' (the one that we renamed in the last step).
    7. Deselect all the check-boxes in the project repair tool.
    8. Click the Repair button.
    9. After a few seconds you see a message saying 'Success'.
    10. Open the repaired file in Premiere Pro and then reset the workspace. Choose Window > Workspace > Reset Current Workspace.
    11. Click the Save button to reduce the project size.
    12. Your project is now repaired.
    NOTE: If a file containing letters such as ã, å, ê, í, ú don’t repair, rename the file to something that doesn't contain these letters.

    Hi Rameez,
    first of all thanks a bunch for the tool - it saved our neck this morning on a tight deadline.
    One minor note: I did get a message that the (already uncompressed + renamed) file is not uncompressed until I ran the tool as Administrator so you might want to add that to the FAQ entry...
    Other than that I'm very much interested in what triggers this bug so we can potentially prevent it.
    Background:
    Specs: Windows 8.1, German locale (ie comma is decimal symbol), Premiere Pro CC 2014.2 installed in English
    My colleague who ran into the TickTime.cpp-290 error remembers having created a new workspace while working on the project. That seems to have triggered the issue as we haven't had any trouble on other projects yet. It also got saved into the project file:
    <MZ.Project.WorkspaceName>Bearbeitung</MZ.Project.WorkspaceName>
    Any autosaves after he added the workspace were corrupted as well while the ones dating back to earlier still open fine.
    I'd like to mention that Premiere did import previous (German language) workspaces - dating back until CS5. Not sure if that comes into play.
    On the other hand, the debug log looks like there only is an issue with the decimal symbol:
    10:08:06: Input: C:/temp/trouble/uncompressed/final.prproj
    10:08:06: Path: C:/temp/trouble/uncompressed Basename: final Extension:prproj
    10:08:06: 19852-> from: <PlaybackSpeed>0,069148936170212769</PlaybackSpeed>
    10:08:06: 19852-> to:   <PlaybackSpeed>0.069148936170212769</PlaybackSpeed>
    10:08:06: 23970-> from: <PlaybackSpeed>0,0062741915889604422</PlaybackSpeed>
    10:08:06: 23970-> to:   <PlaybackSpeed>0.0062741915889604422</PlaybackSpeed>
    I really need to make sure that this is no general problem with German locales as we have multiple users on this kind of config and can't afford projects breaking.
    Or do we "just" need to watch out to get rid of the old workspaces? I'm a little puzzled to be honest.
    Maybe it helps to mention that we are on CC Enterprise
    Best regards,
    Mike

  • Why getting NumericSupport.cpp(86) error?

    I am upgrading a program from Labview 7.1 to Labview 2011.  After calling a Graph, it begins to read data or plot (I can't figure out which one before it crashes), then crashes.  Upon restart, I get the following error:
    C:\builds\penguin\labview\components\mgcore\trunk\11.0\source\NumericSupport.cpp(86) : DAbort: ConvertNum called with non-numeric
    $Id:  //labview/components/mgcore/trunk/11.0/source/NumericSupport.cpp#3  $
    See the attachments for more.
    Any ideas to help?  Thanks in advance.
    John......
    Attachments:
    lvlog.txt ‏2 KB
    1339d798-abd3-4859-bf7c-69d50d5ca1f8.txt ‏1 KB

    John:
    I don't know if you're still looking for a solution, but I just found one for a similar problem.
    I was converting a program from LabView 8.2 to 2011 and kept getting the same crash you got when trying to read the Property Node of one of the graphs.
    It turns out that Graphs in 8.2 have a different set of properties (X Scale range, min, max, flipped, format and precision, etc...).
    I think the problem in my case was that Range used to be defined as Min, Max and Increment.  It's now defined as Increment, Max, Min, Minor Increment and Start.
    Trying to use the old property node to read the properties of the new chart caused an error because the data was not formatted as expected.
    To fix this, I deleted the old property node, created a new one, read the new properties in their correct format and then bundled them together as they were before.
    Works perfectly. 

  • When i click on an excel or word file in 2007 the program begins to open but then an error message says There was a problem sending the command to the program

    when i click on an excel or word file in 2007 the program begins to open but then an error message says There was a problem sending the command to the program.
    i am using office2007  with windows7 premium home edition.  i have checked file associations., all DDE settings. i have even tried this in safe mode. the same thing happens. please note once i see the error. i can then go back to the file click on
    it a second time and it WILL open. AND i can open any file if i open excel and and find the file from there. i uninstalled and re-installed office 2007 from scratch. And i checked the compatibility mode (all un-checked) still the problem persisits. this is
    a real PITA.   anyone have any solution for this? Thanks 
    ken yanow

    Hi,
    Have you try to un-select the Ignore other applications that use Dynamic Data Exchange (DDE) setting?
    Click the Microsoft Office Button, and then click Excel Options.
    Click Advanced, and then click to clear the Ignore other applications that use Dynamic Data Exchange (DDE)
    check box in the General area.
    Click OK.
    If the problem cannot resolve, the Run as administrator may selected.
    Go to Office default install location: C:\Program Files\Microsoft Office\Office12.
    Right-click EXCEL.EXE > Properties >
    Compatibility tab.
    Under Privilege Level, uncheck Run this program as an administrator
    check box.
    Best regards.
    William Zhou
    TechNet Community Support

Maybe you are looking for

  • ITunes Match unable to stream music or download songs from?

    Trying to stream music from itunes match it doesn't play.  Try to download a song from itunes match and get error - We're sorry, we cannot complete your request on the iTunes Store at this time.  Thoughts?  Everything was working a few minutes before

  • The Itunes will not update to the newest version of Itunes?

    I did all my updates for Windows. I deleted the 'temp' file. I am not getting an error message I will just try to download it through the apple website and it does nothing, or through my itunes and the bar pops up for like a milisecond and dissapears

  • Preview Slideshow

    Whenever I open a batch of pics in Preview and choose the option to view them as a Slideshow the pics display in a completely random order. Is there any way that I can get them to display in numerical order? i.e the order I took them in.

  • REG: File Adapter

    Hi All,         I have a scenario where i need to pick 2 files from 2 different folders and process them in a particular sequence. Can anyone suggest me a method how this can be achieved. Thanks, Siva.

  • I can not get Java applets to run on my MAC

    I am running OSX 10.9.1, Safari Mountain Lion 7.0.1 and have Java 7u51 and can not figure out how to get applets to run.  I am taking classes for work and they all use applets.  Any ideas how to enable applets?  Blogs have recommended using java pref