The project could not be loaded, it may be damaged or contain outdated elements.

Hi,
I need help, desperately!
I was working today with a small project. I was almost ready, just some titles missing...
Suddenly I could not load the project anymore. I got these messages (see below).
I´m using Premiere Pro CS 6  from my hard disk. Operating system is Windows 8.1.  
Never had this kind of problems before. I can still load other, previous projects without a problem.
Is there a solution for this?
petrihan

Hi,
thanks for for the comment! In fact I did try this and I also tried to import a sequence only. I haven´t changed anything but I guess the automatic update of windows 8.1. has.
And then I noticed that I´m not at all alone with my problem...
Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
So the final solution seems not to be in my hands ;~)
Cheers,
Petri

Similar Messages

  • Transfer to new PC: The project could not be loaded, it may be damaged or contain outdated elements

    The Problem
    I have transferred a large and functioning Premiere Pro project to a more powerful PC but am unable to run it, stopped by the error message "The project could not be loaded, it may be damaged or contain outdated elements".
    Facts
    The new PC has a 6-core processor and a different hard drive configuration but the operating system on both is Windows 7 and both PCs host up-to-date Premiere Pro CS6 (as part of Adobe Production Premium). The PCs are networked and Premiere Pro on the old PC can successfully load and run the project file located on the new PC, proving that the transferred file is not damaged. Also, preceding versions of the same project generate the same error message when run on the new PC except, very oddly, for earlier versions saved on or before 28 June 2011, when the project was only a fifth of its current size; those versions load correctly. Contemporary notes show that the editing carried out that day was simple timeline editing, ie no After Effects etc (that came later), and the project has worked fine then and since.
    So I don't have a damaged project file and don't know what "outdated elements" means.
    Help
    Any help solving this problem would be much appreciated.

    Hi Vinay
    As suggested I renamed the additional folder, created a new project, set 'Custom' editing mode, 'Microsoft AVI' as the preview format with 'Uncompressed' codec.
    Unfortunately the results were similar to before: On importing the original project into the new project I was sequentially asked for the locations of various files, including After Effects .aep files. The final file location request, for an mp3 audio file, was followed by lots of conforming and indexing. During this process the 'Where is the file XXX.mp3? window stayed locked open. Eventually, with all conforming etc finished, this window was still open and locked. Clicking anywhere on the screen caused a 'ding' and another, smaller, box opened, listing three .aep files. This box asked no questions and gave no options for selecting a file location so, with the topmost file highlighted, I just clicked 'ok' and the box disappeared, leaving the 'Where is the file XXX.mp3?' box still open.
    The importing process took about 30 minutes. I waited another 10 minutes, in case something was happening in the background, but with the Task Manager CPU usage value sitting on 0 or 1%, I used it to shut down the project.
    For what it is worth, I created a simple new project on the old PC – just a few video clips and transitions in a single sequence (no After Effects etc). This project was then transferred to the new PC and it opened successfully.
    Again I remain grateful to you for this and any more advice.
    Best regards
    Dave

  • THE PROJECT COULD NOT BE LOADED, IT MAY BE DAMAGE OR CONTAIN OUTDATED ELEMENTS

    I am trying to open a .prprj worked yesterday but I get this msg: THE PROJECT COULD NOT BE LOADED, IT MAY BE DAMAGE OR CONTAIN OUTDATED ELEMENTS
    I tried to import it in a new project, import it in AE, open an aotosaved project (there are so old, not usefull)
    I know that it can be edited in XML, but I don't understand anythig of that...
    HOW DO I REPAR IT???
    Any help???

    Hi,
    thanks for for the comment! In fact I did try this and I also tried to import a sequence only. I haven´t changed anything but I guess the automatic update of windows 8.1. has.
    And then I noticed that I´m not at all alone with my problem...
    Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
    So the final solution seems not to be in my hands ;~)
    Cheers,
    Petri

  • The project could not be loaded, it may be damaged or contain outdated elements - PLEASE HELP

    Hi Dear Adobe Forum,
    I need help, please
    i cant open my project
    I72600K
    Gygabite Z77Ud5
    Matrox Rtx2
    16Gb ram
    Adobe premiere cs5.0.3
    Nvidia geeforce gtx460
    u can download my file from here[code]http://speedy.sh/Ahkxh/Anahit1.prproj[/code]http://speedy.sh/Ahkxh/Anahit1.prproj

    As a happy user of the Matrox RT.X2 for many years, and later an equally happy user of a Matrox MXO2, I can say from experience that it is highly unlikely that this problem has anything to do with the Matrox hardware!
    Can you open a new blank project, and save it?
    If you cannot import your faulty project into a new project, can you import the sequence from your faulty project?
    Have you tried clearing the Media Cache, clearing your preferences, etc. - all among the techniques used to resurrect a Premiere Pro project that has gone bad???

  • "Project could not be loaded, it may be damaged or contain outdated elements" (CS5.5)

    Hi!
    Yes I'm obviously really kicking myself for not having backed up this project I've spent 100's of hours on (even though I'd been fastidious about backing up all the sequences within the project after changes were made and having multiple copies of all the actual media files)...  somehow it just did not occur to me that the basic project file itself was vulnerable in this way. wow.......
    I was actually on my last evening of editing, working on it since summer.
    Anyway I've checked the auto-save files (corrupted) and tried everything else suggested in countless threads on this topic around the internet and come to the conclusion that the file IS damaged. I've downloaded XML Wrench to try to fix it (I don't have a Mac to do the Digital Rebellion thing) but not knowing anything of XML, it hasn't worked out so far. So is there anyone who might be able to point me in the right direction for getting the file repaired by a third party? I was not able to find a service who might offer such a thing but maybe somebody knows someone?
    Thank you for any help!!!

    Hi James,
    Have you tried creating a new project and then importing items from your corrupted project?
    JamesLassen wrote:
    somehow it just did not occur to me that the basic project file itself was vulnerable in this way. wow.......
    I always taught my students to back up project files to three places (on the HD, on removable media, in the cloud) on a daily basis. You may want to fall into this habit as it has always saved me from losing work. I'm sorry that you weren't aware that project files should be protected with back ups as they can can become corrupt, as you have seen.
    Good luck,
    Kevin

  • Im unable to open the pdf file for the code to redeem Mountain Lion:the '*****'file could not be opened. it may be damaged or in a format that preview doesn't recognise

    I've tried opening the file in ibooks, on ipad, in Safari, and straight from e-mail, but it can't open the .pdf file. Could it be corrupted? I'm brand new to the MBP so may be missing something obvious!

    If Preview won't read the pdf file, try Adobe Reader. It is possible, of course, that the file may actually be damaged, as Preview should be able to open the file.
    Clinton

  • Adobe Premiere Pro CS3 "The editing mode used by this project could not be loaded."

    Hello-
    I am encountering an issue with my Adobe Premier Pro CS3. I am trying to open up a project that another person has created on a different editing system. When I try to open, it comes up with the error "The editing mode used by this project could not be loaded. The project will be opened in Desktop mode." The next window is a Windows Explorer screen, that wants me to choose a file to open. If I cancel that, it brings up a blank looking project with no timeline or anything?
    A quick comparison of systems:
    Mine:
    HP dc7700s desktop
    Windows XP OS
    Adobe Master Collection CS3
    Hers:
    IBM compatible laptop
    Microsoft Vista
    Adobe Premiere Pro CS3
    Adobe Photoshop CS3
    I have googled the error message, but have not found anything to fix this. I have also verified from Help - About that we have the exact same versions of Adobe Premiere Pro CS3 installed.
    I need to be able to view this project on either computer. Any advice would be greatly appreciated!!!
    Thank you!

    >project will be opened in Desktop mode
    I have never used any non-standard files, but from reading here, desktop mode is used when the video files are not standard... in one way or another, but usually pixel dimensions
    What is the codec and properties of the files in that project?
    Are you sure they are 100% standard?

  • The project could not be created,please check the webroot folder(it may overlap with an existing project)

    Error msg: "The project could not be created, please check
    the webroot folder (it may overlap with an existing project)." This
    occurs in the CF/Flex Application Wizard Pproject Information
    Window on a Flex3 application. I checked to make sure that there
    were no overlapping applications and the message still persists.
    There are old threads on this from Flex 2 but the problem still
    exists in newly released Flex 3. Please help!

    I can't help you with this, but you are not alone. A friend
    of mine has exactly the same problem

  • The project could not be prepared for publishing because an error occurred.

    I have just loaded iLife 09 on my MAC. I've edited a movie and now want to export it, put it in iTunes, whatever I can do to move it beyond my laptop. No matter what option I choose under Share I get the same error message, "The project could not be prepared for publishing because an error occurred. (-2009)". I can find the error message online, but not the (-2009) error code. I'm also a longtime PC person who has just switched to a MAC. Can anyone help?

    I also am having the exact same problem. iMovie '09. I have tried changing permissions on all sharing folders, exporting to desktop, sharing to iTunes in all size files - and yet still get "Unable to prepare project for publishing. error (-2009).
    Mac OSX version 10.6.2 Snow Leopard

  • I am trying to send an iMovie project to iDVD and I keep getting the following error msg.  "Unable to prepare subject for publishing:  The project could not be prepared for publishing because an error occurred. (-43)"

    I am trying to send an iMovie project to iDVD and I keep getting the following error msg.  "Unable to prepare subject for publishing:  The project could not be prepared for publishing because an error occurred. (-43)"

    Check out this thread: https://discussions.apple.com/thread/1421870
    It may mean you either your Event or your Project. Have you moved any of the files in the Finder by any chance? That error may come up if you moved anything outside of iMovie. Do you get an error message when you choose Share>Export to iMovie (choose medium size) and save it to the Desktop? If you can export it to the desktop, you can pull that file into iDVD separately and still make it work.

  • How can i fix this problem?? "The project could not be prepared for publishing because an error occurred. (Not enough room in heap zone / )"

    The project could not be prepared for publishing because an error occurred. (Not enough room in heap zone / )
    how can i fix this problem?

    how can i fix this problem?
    Go to the right forum.
    This forum is for mobile iMovie.
    you may need the iMovie Mac forum:
    https://discussions.apple.com/community/ilife/imovie

  • 0x80230729 (The extension could not be loaded.)

    Hi,
    I've been working on this most of the day without any luck. I'm wondering if anyone has seen something like this.
    PCNS can successfully deliver the password change to an AD target, so PCNS should be OK.
    The failure occurs when we add the Oracle EBS Web Service management agent to the password sync targets.
    The error message indicates that the Microsoft.IdentityManagement.WebService.MA.dll cannot be loaded due to an incorrect .NET framework version.
    An unexpected error has occurred during a password set operation.
     "BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(322): 0x80230729 (The extension could not be loaded.)
    ERR_: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(804): Please verify that the password extension dll can be located in the Extensions directory.
    If the extension is present, confirm that the version of the .NET framework that can run the extension is installed on the server and that a supportedRuntimes entry in the configuration files specifies that version. The synchronization engine will not be able
    to load an extension that is built with a newer version  of the .NET framework than the version of the .NET runtime it is hosting.BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(806): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\extensible\export.cpp(2821): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\extensible\export.cpp(2866): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\exportpassword.cpp(474): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\ma.cpp(7961): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\ma.cpp(8410): 0x80230729 (The extension could not be loaded.)
    Forefront Identity Manager 4.1.2273.0"
    I ran an Environment.Version command and it returns that we are using 4.0.30319.296.
    In the dllhost.exe.config file, we have the settings:
    <?xml version="1.0" encoding="UTF-16"?>
    <configuration>
    <configSections>
    <section name="resourceManagementClient" type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
    </configSections>
    <!--
    .NET Runtime startup configuration: If you use a .NET 4.0 runtime, the useLegacyV2RuntimeActivationPolicy attribute is required and must be set to "true".
     When multiple versions of the runtime are listed, the first supportedRuntime element should specify the most preferred version of the runtime,
    and the last element should specify the least preferred version.
    Currently, the Synchronization Service supports the following runtime choices: v2.0.50727 and v4.0.30319. If selected, the version must be found in the \Windows\Microsoft.NET\Framework or \Windows\Microsoft.NET\Framework64 directories.
    -->
    <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0.30319"></supportedRuntime>
    <supportedRuntime version="v2.0.50727"></supportedRuntime>
    </startup>
    <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />
    <bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />
    </dependentAssembly>
    </assemblyBinding>
    </runtime>
    </configuration>
    So, I think it looks like it should be trying to run the dll under the 4.0.30319 framework. The documentation says that framework is required and we are running it.
    The dll is in the Extensions folder.
    Has anyone seen this before or something like it? Any ideas on where else I could check?
    Thanks,
    Sami

    Thank you for your reply. I've tried running in and out of proc with the same error showing up.
    I tried a few different modifications to the miiserver.exe.config (as well as Mmsscrpt.exe.config and the Dllhost.exe.config files). I tried changing 4.0.30319 to 4.0 as per this article:
    http://msdn.microsoft.com/en-us/library/w4atty68.aspx
    Even though we are only on FIM R2 (not on SP1), I tried a variation on the config file changes recommended here:
    http://support.microsoft.com/kb/2772429 but I referenced the newVersion as 4.0.1.0.
    Still no luck.
    Here's the miiserver.exe.config file. Maybe you'll see something glaringly wrong? Thank you for your help!
    <?xml version="1.0" encoding="UTF-16"?>
    <configuration>
      <configSections>
        <section name="resourceManagementClient" type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
        <section name="resourceManagementService" type="Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection, Microsoft.ResourceManagement.Service"/>
        <section name="resourceSynchronizationClient" type="MIIS.ManagementAgent.ResourceSynchronizationClientSection, mmsmafim"/>   
      </configSections>
      <!--
        .NET Runtime startup configuration: If you use a .NET 4.0 runtime, the useLegacyV2RuntimeActivationPolicy attribute is required and must be set to "true".
        When multiple versions of the runtime are listed, the first supportedRuntime element should specify the most preferred version of the runtime,
        and the last element should specify the least preferred version.
        Currently, the Synchronization Service supports the following runtime choices: v2.0.50727 and v4.0.30319. If selected, the version must be found in the \Windows\Microsoft.NET\Framework or \Windows\Microsoft.NET\Framework64 directories.
       -->
      <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0.30319"></supportedRuntime>
        <supportedRuntime version="v2.0.50727"></supportedRuntime>
      </startup>
      <!--
      <resourceManagementService/>
            Additional properties that can be specified for the <resourceManagementService /> configuration section
            PropertyName                                   
    DefaultValue                                Description
            dataReadTimeoutInSeconds                        58                                         
    Database timeout for read operations
    Range: 0-max(int16)
            dataWriteTimeoutInSeconds                       58                                         
    Database timeout for write operations
    Range: 0-max(int16)
            synchronizationDataReadTimeoutInSeconds         1200                                       
    Synchronization operations (FIM MA import / export)
    that read from the FIM Service are tied to this timeout
    to allow these operations extra time to complete if there
    are a large number of objects / values in a batch.                                                                                                   
    Range: 0-max(int16)
            Note: The following registry key : ReadTimeOut , in the registry path : HKLM\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service ,
            overrides the synchronizationDataReadTimeoutInSeconds property.
            synchronizationDataWriteTimeoutInSeconds        1200                                       
    Synchronization operations (FIM MA import / export)
    that write to the FIM Service are tied to this timeout
    to allow these operations extra time to complete if there
    are a large number of objects / values in a batch.                                                                                                   
    Range: 0-max(int16)       
            externalHostName                                Defined by
    Administrator during set-up      This value is used by FIM to define the external host name
    that should be used by clients to connect to FIM when you deploy
    a Load Balanced configuration.       
        -->
      <resourceSynchronizationClient/>
      <!--
            Additional properties that can be specified for the <resourceSynchronizationClient /> configuration section. This configuration is used to configure the FIM MA
            settings.
            PropertyName                                   
    DefaultValue                                Description
            asynchronous                                   
    true                                        This property controls
    whether FIM MA uses the older synchronous channel
    or the new asynchronous channel when communicating with FIM Service.
            aggregate                                      
    true                                        This property controls
    whether FIM MA can send data to FIM Service in batches.
            aggregationThreshold                            1000                                       
    This property controls the number of attributes per aggregated batch.
            delayUpdateAcknowledgements                     false                                      
    This property controls whether the FIM Management Agent sends acknowledgements to
    FIM Synchronization Service immediately upon Request completion, or withholds them
    until the end for Update operations. Setting this to true may reduce the overall time
    to export data, but the FIM Synchronization Service UI statistics are not updated as frequently.
            exportRequestsInProcessMaximum                  50                                         
    This property controls the maximum number of export requests that
    can be in process.              
        -->
        <system.diagnostics>     
            <sources>
                <source name="ForefrontIdentityManager.ManagementAgent" switchValue="Warning">
                    <listeners>
                        <add initializeData="ForefrontIdentityManager.ManagementAgent" type="System.Diagnostics.EventLogTraceListener, System, Version=2.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089"
                             name="MAExceptionEventLogListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, Callstack">
                        <filter type="" />
                        </add>
                    </listeners>
                </source>
                <source name="ForefrontIdentityManager.ManagementAgent.EventTracingForWindowsTraceSource" switchValue="Verbose">
                    <listeners>
                        <add name="MAEventTracingForWindowsListener"
                             type="System.Diagnostics.Eventing.EventProviderTraceListener, System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                             initializeData="{C4D0C1D4-909D-481b-B011-10E682A6009C}" />
                    </listeners>
                </source>
            </sources>
        </system.diagnostics>
        <!-- Instructions for collecting ETW Traces
             To collect ETW traces for Microsoft.ResourceManagement.Service. Run the following commands in the specified order from
             an elevated command prompt.
                1. To start a new etw trace session    : logman start mysession -p {C4D0C1D4-909D-481b-B011-10E682A6009C} -o FIMMAETWtrace.etl -ets
                2. To stop a running etw trace session : logman stop mysession -ets
                To format the collected traces run any of the following commands (from an elevated command prompt) depending
                on the required output format.
                1. tracerpt FIMMAETWtrace.etl -o FIMMAEventTrace.xml -of XML -lr -summary FIMMAEventTraceSum.txt -report FIMMAEventTraceRpt.xml
                2. tracerpt FIMMAETWtrace.etl -o FIMMAEventTrace.evtx -of EVTX -lr -summary FIMMAEventTraceSum.txt -report FIMMAEventTraceRpt.xml
                3. tracerpt FIMMAETWtrace.etl -o FIMMAEventTrace.csv -of CSV -summary FIMMAEventTraceSum.txt -report FIMMAEventTraceRpt.xml  
      -->
        <!--
           Full Diagnostics configuration.
           Uncomment the following section and replace the default <system.diagnostics> configuration to
           enable all trace sources and obtain all available traces for Microsoft.ResourceManagement.Service
      -->
        <!--
        <system.diagnostics>     
            <sources>      
                <source name="System.ServiceModel" switchValue="Verbose"
                  propagateActivity="true">
                    <listeners>                  
                        <add name="ServiceModelTraceListener">
                            <filter type="" />
                        </add>
                    </listeners>
                </source>
                <source name="ForefrontIdentityManager.ManagementAgent" switchValue="Verbose">
                    <listeners>
                        <add initializeData="ForefrontIdentityManager.ManagementAgent" type="System.Diagnostics.EventLogTraceListener, System, Version=2.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089"
                             name="ExceptionEventLogListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, Callstack">
                        <filter type="" />
                        </add>
                        <add name="ServiceModelTraceListener">
                            <filter type="" />
                        </add>
                    </listeners>
                </source>
                <source name="ForefrontIdentityManager.ManagementAgent.EventTracingForWindowsTraceSource" switchValue="Verbose">
                    <listeners>
                        <add name="EventTracingForWindowsListener"
                             type="System.Diagnostics.Eventing.EventProviderTraceListener, System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                             initializeData="{C4D0C1D4-909D-481b-B011-10E682A6009C}" />
                    </listeners>
                </source>
            </sources>      
            <sharedListeners>
                <add initializeData="ForefrontIdentityManager.ManagementAgent_tracelog.svclog"
                  type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                  name="ServiceModelTraceListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
                    <filter type="" />
                </add>
            </sharedListeners>
            <trace autoflush="true" />
        </system.diagnostics>
        -->
      <!--
        .NET Runtime startup configuration: If you use a .NET 4.0 runtime, the useLegacyV2RuntimeActivationPolicy attribute is required and must be set to "true".
        When multiple versions of the runtime are listed, the first supportedRuntime element should specify the most preferred version of the runtime,
        and the last element should specify the least preferred version.
        Currently, the Synchronization Service supports the following runtime choices: v2.0.50727 and v4.0.30319. If selected, the version must be found in the \Windows\Microsoft.NET\Framework or \Windows\Microsoft.NET\Framework64 directories.
       -->
      <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0.30319"></supportedRuntime>
        <supportedRuntime version="v2.0.50727"></supportedRuntime>
      </startup>
      <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />
            <bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />
          </dependentAssembly>
        </assemblyBinding>
      </runtime>
    </configuration>

  • When sharing iMovie11 project  with iDVD inmediately message 'the project could not be prepared for publishing because an error occurred (Error in user parameter list).  Finalize issue?

    When sharing my 60 minutes iMovie project with iDVD inmediately message 'The project could not be prepared for publishing because an error  occurred (Error in user parameter list)' appears. Could not find the user parameter list, so I've no more info about this error.
    Option File - Finalize Project gives inmediately the same errormessage.
    Also option Share - Media Browser - Large/Medium/Mobile give the same errormessage.
    Please advise, thank you!

    Additional info: trying to write to internal disk (268 GB Free out of 499 GB)
    Please advise, alko80

  • The project could not be prepared for publishing because an error occurred. (-108)

    Got the following error while trying to share my project:
    "The project could not be prepared for publishing because an error occurred. (-108)"
    I got this error everywhere: share to idvd, share - export movie ...
    Computer: MAcbook Pro 2.3GHz Intel Core I5, memory : 4 GB (when I start exporting the available memory is about 2Gb, no other app runing)
    Softwer: Mac OS X 10.7.2, iMovie '11 9.0.4 (1635)
    Project: 50min, filmed with Gopro 960HD
    Please help!
    Thanks in advance,
    Lóránt

    Most recently there's been a series of errors -49 being posted to the Discussion Group. I've seen one other -108 error that showed up but without any resolution. The original poster hasn't replied yet to that mesage thread. I don't know if the two are related, but they both have a negative effect on exporting. So I'm going to suggest following the fix for the -49 errors:
    This requires using the Terminal app, in your Applications/Utilities folder
    To turn off Time Machine snapshots type in the following command:
    sudo tmutil disablelocal
    The Mac will likely ask for your password, so type it in and hit the return key. The type the word, exit and hit return. Quit Terminal.
    Open iMovie and try doing another export and see if the same error message pops up.

  • I keep getting this message from Imovie: Unable to prepare project for publishing. The project could not be prepared for publishing because an error occurred. (Error in user parameter list)

    I keep getting this message from Imovie:
    Unable to prepare project for publishing. The project could not be prepared for publishing because an error occurred. (Error in user parameter list)

    Bartirn,
    I called Apple under my Mac support contract.  They were completely unfamiliar with the error you and I were encountering.   Updating to 10.8.5 didn't help.
    I'm stopping my TimeCapsule while I perform these tasks, but I don't know yet if I have a consistent work-around.
    B

Maybe you are looking for