Error when exporting RTF to XSL-FO with the template builder for word

I am currently trying to export an RTF file from word 2007 to the xsl-fo format. I am using the latest version of BI Publisher desktop as well since I wanted to see if that solved my problem as well. I currently get the following error when trying to convert the file and I know it is an error generated by windows but I am not sure how to fix it.
The error I receive is: This file does not have a program associated with it for performing this action. Create an association in the Folder Options control panel.
Any help with how to fix this error would be appreciated.

Hi
I dont think this is a BI Publisher issue per se. It looks like Word does not know what to spawn to get the document to open.
You need to create the association - you do that in the Folder Options control panel. Open the Windows Explorer app (I think in Vista they protect you from yourself - you need to dbl click the Computer icon) - I think you can then set file options somewhere in there. Just google it for the specifics
Regards
Tim
http://blogs.oracle.com/xmlpublisher

Similar Messages

Strange error when attempting to add an article to the Folio Builder

I've just installed the trial of InDesign 5.5 along with the Digital Publishing Suite.
I've followed the instructions to add an article to the Folio Builder but I am continually greeted with this error:
Not sure what I am doing wrong, the document is set at 1024x768 and it's the first article I've tried to create. It's very simple, just a single image and some text.
I've tried installing on a seperate machine but I get the same error.
Any help would be appreciated.
Ryan

In some instances, InDesign isn't recognizing the new tools. To fix, restore InDesign preferences:
(Windows) Start InDesign, and then press Shift+Ctrl+Alt. Click Yes when asked if you want to delete preference files.
(Mac OS) While pressing Shift+Option+Command+Control, start InDesign. Click Yes when asked if you want to delete preference files.
http://help.adobe.com/en_US/indesign/cs/using/WSa285fff53dea4f8617383751001ea8cb3f-6d21a.h tml#WSa285fff53dea4f8617383751001ea8cb3f-6d1ba

Error when trying to run UCM from browser -The portal page for your Content

Hi
When I try and run the UCM in a browser using "http://localhost/idc", it showing
"The portal page for your Content Server needs to be rebuilt. Start the WebLayout Editor as a standalone application and select Update Portal... from the Options menu."
I did see a previous message that says to go to Weblayout Editor Applet - Options - Build Home Page - Update -Ok, but I was not able to see the Build Home Page option in the drop down.
Any ideas what may be causing this issue?
Thanks in advance for your help
Cheers
Sylvia

Hi Srinath
Thanks for your reply.
Commenting out the following lines still does not fix my problem.
<div align=center>Welcome to UCM10g for SIF DEV</div> 
 <$if IsLoggedIn$>UserName = <$UserName$> <$endif$>
 <$if IsDynamic$>Current Time = <$dateCurrent()$>
 <$else$>This is a static page.
 <$endif$>
I have installed this product on two environments following the same kind format.
In our dev environment I am able to type in the following to get to the Welcome to Content Server Page
http://devenv/idc/
In the other environment I use the following and I get that the error "The portal page for your Content Server needs to be rebuilt. Start the WebLayout Editor as a standalone application and select Update Portal... from the Options menu."
http://testenv/idc
So the only way to get to the Content Server Page is to type the full path as below which I don't want to do, because I want the welcome screen to appear first.
https://testenv/idc/idcplg?IdcService=GET_DOC_PAGE&Action=GetTemplatePage&Page=HOME_PAGE&Auth=Internet
Is there a way I can configure the application to get to my welcome screen instead of getting the error message detailed above?
Thanks
Sylvia

'file could not be written due to an error' when exporting jpg

I'm working with an Illustrator file in CS2 and after a certain point it has started saying 'the file could not be written due to an error' when exporting to a jpg.
i've tried a couple things like deleting layers and although the file is much smaller, it still says the same error when exporting.
at its highest it was 130mb as an illustrator file and jpgs were 2-5mb.
i''ve tried copying some of the layers into a new file but the error report still comes when i'm exporting.
i have vector and raster based data in the file and tried turning off/deleting either of the layers and there is no difference.
i don't understand why it's started doing this because before it had no problem at all exporting before.
ANY IDEAS ANYONE? I'm trying not to have to reproduce days of work to remake the file.
many thanks,
P

Mylenium,
Sounds like you know a good deal about this product. Is there any way to restore a color profile/setting to an earlier point?
I don't recall changing it and to tell you the truth, wouldn't be able to say which it may have been set to before - if different.
Thanks,
Paul

Error when exporting and importing TS

Hi I am running SCCM 2012 SP1 and am trying to export a Task Sequence including with the Windows 7 wim, the boot wim, some applications and drivers. When I exported the TS I selected to export dependencies and content.
I have setup dev SCCM environment (same spec as production) and am trying to import the .zip that was created when I completed the export. When doing the import I am getting the below error on both the Windows 7 wim and the boot wim :
Error Imported Operating System Image (1):
Create new Windows 7 Enterprise x64
Generic failure
instance of SMS_ExtendedStatus
Description = "Failed to get the image property from the source WIM file due
to error 80070003".
ErrorCode= 2147942403;
File="e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\
\sspimagepackage.cpp";
Line = 483;
Operation = "Putinstance";
ParameterInfo = "";
ProviderName = "ExtnProv";
StatusCode = 2147749889;
The applications and drivers have been imported into the Dev SCCM server however I cannot find the actual content so I am not sure this has worked properly. I am wondering if I would be better off using the Migration wizard to take the TS and
content across. Would appreciate any advice on either a) how to fix the issues with the importing of the TS or b) whether I should just be using the migration wizard.
Thanks
G

The applications and drivers have been imported into the Dev SCCM server however I cannot find the actual content so I am not sure this has worked properly.
When you exported did you choose to "Export all content for selected task sequence and dependencies".
80070003 = The system cannot find the path specified.
See here for exporting and importing task sequences
http://blogs.technet.com/b/inside_osd/archive/2012/01/19/configuration-manager-2012-task-sequence-export-and-import.aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Error when exporting reports using MAPI

We created a .NET class that wraps CR 2010 .NET Crystal Reports functions and made it COM visible. This class is used to create a COM object in a js script which in turn used to export reports to a PDF file with the destination MAPI.
It exports reports just fine without any errors however if prior to instantiation the exporting class we instantiate a class that has nothing to do with the Crystal Reports functions, our exporting object throws u201CExternal component has thrown an exception.u201D error when exporting. It appears that it has something to do with the SideBySide feature. I was wondering if somebody knows what causes this and if there is a way to fix this problem.
Thanks for your help!
 
 
Below are 2 procmon.exe outputs, the first when exporting works and the second when it doesnu2019t
 
 
 
1) Procmon.exe output when exporting works fine
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 7:16:30.7403615 AM test.exe 4396 FASTIO_QUERY_INFORMATION C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Image Base: 0x79260000, Image Size: 0x1073000
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryNameInformationFile, Name: \Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest NAME NOT FOUND Length: 20
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 
 
 //////////////////////////////////////////////////////////////////////
 2) Procmon.exe output when exporting doesnu2019t work, notice that it tries to open MSO.dll at the same location as in the output above but fails, it tries then to open it at several other locations and fails
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll FAST IO DISALLOWED
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll FAST IO DISALLOWED
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\SysWOW64\MSO.dll FAST IO DISALLOWED
 C:\Windows\SysWOW64\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\system\MSO.dll FAST IO DISALLOWED
 C:\Windows\system\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\MSO.dll FAST IO DISALLOWED
 C:\Windows\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

I tried to run exporting code in a .net application and got the same error. I first created the COM object that causes the problem and then ran exporting CR functions. It works fine if I run the code without creating the COM object.
Below is the code I used.
 Type objClassType = Type.GetTypeFromProgID("ebms.main");
 object objMain = Activator.CreateInstance(objClassType);
 try
 object[] p = new object[4];
 p[0] = "C:\\ebms\\co1";
 p[1] = "C:\\ebms\\co1";
 p[2] = "Administrator";
 p[3] = "";
 objClassType.InvokeMember("LoginToCompany", System.Reflection.BindingFlags.InvokeMethod, null, objMain, p);
 catch (Exception ex)
 this.RPTDoc = new ReportDocument();
 this.RPTDoc.Load(@"C:\\Users\\Paul\\Desktop\\AR Customer List.rpt");
 PdfRtfWordFormatOptions pdfOpts = ExportOptions.CreatePdfRtfWordFormatOptions();
 MicrosoftMailDestinationOptions mailOpts = ExportOptions.CreateMicrosoftMailDestinationOptions();
 ExportOptions exportOpts = new ExportOptions();
 pdfOpts.UsePageRange = false;
 exportOpts.ExportFormatOptions = pdfOpts;
 mailOpts.MailMessage = "something";
 mailOpts.MailSubject = "something";
 mailOpts.MailToList = "emailaddress";
 exportOpts.ExportDestinationOptions = mailOpts;
 exportOpts.ExportDestinationType = ExportDestinationType.MicrosoftMail;
 exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
 try
 this.RPTDoc.Export(exportOpts);
 catch (Exception ex)
 MessageBox.Show(ex.Message, "Error", MessageBoxButtons.OK, MessageBoxIcon.Error);

Error when exporting file from LR5.2 - file created

After updating to LR5.2, I receive an error when exporting files to another disk drive. a file is created, but a warning appears "Unable to Export: "An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute". I also have CC iunstalled for other applications, but originally installed LR5 as a standalone Adobe application. I tried removing the program and reinstalling through CC, with no change in this behavior.

The answer is in the thread:
http://forums.adobe.com/thread/1303578?tstart=0

Error when exporting to flat file in ODI 11g

This works ok in ODI 10g. I'm using IKM SQL to File Append on Windows Server 2008 R2
Getting the following error when exporting to a flat file in ODI 11g: ODI-40406: Bytes are too big for array
I've seen a couple of threads like this on the forum, but I've never seen an answer to the problem.

Problem is with the difference in behaviour for the IKM SQL to File Append KM between 10g and 11g.
Our 10g target file datastore had a mixture of fixed string and numeric columns. Mapping from the source to target was simple one to one column mapping. It generated the desired fixed format flat file; numerics were right adjusted with embedded decimal point and leading spaces. Each numeric column in the generated flat file occupied the exact space allocated to it in the layout. This gave the desired results, even though documentation for the 10g IKM states that all columns in the target must be string.
When we converted to 11g and tried to run this interface, it generated an error on the "numeric" columns because it was wrapping them in quotation marks. The result column was being treated as string, and it was larger than the defined target once it acquired those quotation marks.
In order to get 11g to work, I had to change all the numeric columns in the target data store to fixedstring 30. I then had to change the mapping for these numeric columns to convert them to right adjusted character strings (i.e. RIGHT(SPACE(30) + RTRIM(MyNumericColumn),30).
Now it works.

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
~/Library/Application Support/Aperture/Plug-Ins/
where ~ is the home location for the current user account. All the other plug-ins however were installed in
Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

I get an error when exporting imovie

I get an error when exporting a project from iMovie, Error: "Unable to prepare project for publishing. The project could not be prepared for publishing because an error occurred. File already open with write permission". How do I fix this?

Hello !
Could you please be more elaborative for explaining your issue?

Error when exporting to hard-drive

Lightroom 4 was working fine before I tried to export to Flickr. The export was NOT successful, and after that, I encountered an error when exporting to hard drive. Although this error appears, the export to hard drive is always successuful. It is annoying to continuously receive this error message. Any help will be much appreciated. Thanks

That is the small trouble with screenshots: as unambiguous and helpful as they are they are hard to search for their content.
But it looks identical to several other posts here (http://forums.adobe.com/message/4341436#4341436, http://forums.adobe.com/message/4318154#4318154, http://forums.adobe.com/message/4285253#4285253, http://forums.adobe.com/message/4261252#4261252, http://forums.adobe.com/message/4177871#4177871):
In your export manager select "Do nothing" i.o. leaving it blank. down at the bottom where it asks for what to do in Post Processing After Export.
This should have the message go away.
For the sake of searchability I spell out the error message, so that others could find this being answered:
Unable to Export:
An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute.
Cornelia

Error when exporting slideshow (OSStatus error -9459)

I put together a slideshow in iphoto without problem. The problem starts when I want to export the slideshow - in order to make it available in iTunes. The export process seemingly randomly stops with the error message (OSStatus error -9459).
The slideshow is rather large (500 pictures and some videos), I was not able to recreate the error when trying on a small selection, incl. movie clips.
Is the pure number of the pictures or the resulting file the reason for this? Anything else?
How can I solve this? Did anybody else have that problem?
Btw I am running Lion (but the error also happened with SnowLeopard).
Thanks for any advice.
Florida712

In your SystemPreferences -> Energy Saver set your Mac and screen to never sleep.
Regards
TD

Error when tryying to burn ny dvd with Encore

I am getting a error when tryying to burn ny dvd with Encore
PCG "baseball_and_more" has an error at 00;00;00.
Internal software error:0% line basball_and_more -PGC Info name == baseball_and_more ref == Bpgc, time 00;00;00
Anyone know what this is due to?
If I add another clip before the base_ball_and_more then I get the same erro but at 16:45:0I 4
This seems related to changing the M/N field in the adobe media encoder. If I use defaults while encoding in premier
I dont get them error in Encore. But if I change the defaults ( hope fully to get better DVD results) I get the error.

First, back on the main page http://forums.adobe.com/community/encore enter
pcg
into the SMALL forum search window on the right and read previous discussions
Second, try exporting from Premiere as DV AVI type 2 and give that to Encore... use the Automatic encoding setting and let Encore make the decision on what will best fit on a DVD

Out of memory error when exporting to QT self contained movie

When I export to QT self contained movie the program runs for about an hour then brings an "out of memory" error. My project is 1hour 10 min. I have 650 GB on the external drive I'm saving to and another 145 GB on my imac's drive. There are also photographs I've included in the sequence but I have removed them all from the sequence to see if the format was the problem but the error still comes up. I would appreciate any help.

Well I don't have to render as I go, it is just a choice. I checked to see if all the video and stills were rendered. I re-rendered after making sure all of the options were checked, removed all of the stills from the timeline just in case the still format was the problem, then attempted to export again. It took about 2 hours. I watched with activity monitor and it took almost all of the available disc space then my computer shut itself down. When I rebooted there was a Quicktime file 320 GB in size but would not open. I got an error message that it was not a mov. file.
But to answer your question:
Video is 29.97fps DV/DVCPRO
Frame size is 720 x 480
3.0 mb/sec
16 bit Integer
Aplha= None /ignore
Composit is Normal
NTSC-CCIR 601
Stereo
Stills are at 25.0 fps JPEG

Problem when exporting to Vimeo I get message "The share operation has failed. Quicktime error: -50" The file only gets to 8% before this happens any idea how to fix I have a movie deadline to meet!

Hi all,
Finished editing a short movie.
Then went to share on vimeo but got this message - see also screenshot when I tried to export to desktop.
Problem when exporting to Vimeo I get message "The share operation has failed. Quicktime error: -50" The file only gets to 8%.
Have tried deleting my render files for the project and also another fix mentioned of deleting any black space files on the edit itself but neither work?
Just upgraded to OS Mavericks could this be causing it? If so how to downgrade?
thanks
Louis B

Thanks for your help both, I called Apple tech support and spoke to a really helpful chap called Andrea who helped me out. Now got my Master file sorted and am trying Vimeo upload again.
Just to clarify points for people out there with the same issue:
First steps
- Ensure background rendering is turned off in preferences
- Delete project and events render files
- If upgraded to Mavericks then go to FCPX in finder under applications hit buttons 'CMD' and 'I' together and tick the 'prevent App Nap' box.
Next Steps
I had already done all of this when Apple Tech spoke to me so we discussed the message 'Quicktime -50' and what it meant. It wasnt a purely generic error message but was not detailed enough to point to one specific issue. This problem had occurred in previous years (so Mavericks not wholly to blame) and patches were issued over the years by Apple to help resolve some of the problems.
The message essentially is indicating that there is a problem somewhere with the media in some way shape or form.
My export went to 8% then failed. Apple's answer was that the project settings were corrupted in some way.
So what they suggested (so simple I could kick myself) was to select all the media files by 'CMD + A' then copy them 'CMD + C' then create and open a new project timeline, and then paste in 'CMD + V'.
Then we tried export again this time to a master file with some settings detailed by Apple.
The difference now was it got to 40% then failed but due to a different reason 'error -1 frame 10124 error'
At last we get past the project issues and into the event media issues, it seems that when I loaded the compact flash last night, the iMac kept ejecting the reader so had to copy files over quickly and seems that some of the file clip I used although showed on the viewer, didn't seem to have loaded all the correct media, so selecting this clip frame 10124 on the viewer I found that it showed as red on the frame row which implied an issue. So I simply bladed it off and deleted it.
Then I reran the export to Master file and it worked, though jumping from 40% to 100% complete was a shock to me!
Now am trying the export to Vimeo - hope this helps some of you out there. Worst case pick up the phone to Apple and speak to the Final Cut Pro guys they can help.
best wishes,
Louis B

Error when exporting RTF to XSL-FO with the template builder for word

Similar Messages

Maybe you are looking for