Error when exporting with Quicktime

I'm having some problems exporting with Quicktime from iMove '08. Here are my settings:
(The highlighted portion says 20,000 kbits/sec)
I have exported using these settings before, but for some reason, it gives me error code -2002 when it finishes exporting now, and tells me that it can't export. Anyone know what error code -2002 is? I can't find it here or on Google. Exporting straight to m4v worked just fine.

I'm exporting at those dimensions because that's just where I had it set (lol). I didn't even realize it was HD until just now, but like I said, I put the lowest possible data rate (32 kbits/sec) and the smallest dimensions possible (160x120) and it still didn't work.
However, I had completely missed the fact that the audio wasn't being exported. I reset the audio settings and tried again on the smallest setting, and that worked. Thanks for your help!

Similar Messages

  • Final cut pro problem when exporting with quicktime movie

    Hello!
    I must have som help beacuse my musicmovie must be finsihed untill today. I have a movie their i had used filters like colour correction and interlace. When i export with USING QUICKTIME CONVERSION and have
    keyfram 10
    bitrate 6000
    faster encode
    size 1920x1080 HD 16:9
    its not a problem the movie works fine all the way.
    But when i export with QUICKTIME MOVIE it dosent work. Some clips are frozen and some are beeing misscoloured. None of them have interlace. Its the same clips that dosent work everytime i had export with QM. I have tried to replace these clips but the same thing is happening. I dont understand why i cant use quicktime movie but it works with quicktime conversion.
    If you have an e-mail i can send you just the part where this happening.
    Please help me!
    Thanks Gabriel

    I am also expriencing the same error. Tried every solution listed so far:
    1. Switch off background rendering. Trash render files. Don't render. Export.
    2. copying the project within Final Cut Pro into another project
    3. remove the following folder: Library > Application Support > ProApps > MIO > RADPlugins > XDCAMFormat.RADPlug
    Nothing worked. I try to export to Vimeo, YouTube, and master. All error right at 9%
    What's going on?

  • Error when exporting as Quicktime

    Help
    This is really frustrating and baffling.
    I have a flash project which consists of a .mov import with graphics mottions over the top.
    First there was no sound when exporting the project as a swf
    I then tried to export the project as a Quicktime .mov but got an error message "could not complete operation because of an unknown error"
    What am I doing wrong?
    I am using Flash 5.5

    I tried the link and it didnt work so here is the url
    http://www.4shared.com/file/NkeNX5Lp/Archive.html
    <a href="http://www.4shared.com/file/NkeNX5Lp/Archive.html" target=_blank>Archive.zip</a>
    [URL=http://www.4shared.com/file/NkeNX5Lp/Archive.html]Archive.zip[/URL]

  • General error when exporting to Quicktime from FCE

    I've built a slideshow with still photos, text, and audio. I've done this at least 20 times. When I start exporting to Quicktime, as I want to burn a dvd in iDVD, the export stops at 27% completed and I get a "General Error". there is no explanation. I've rendered the single sequence many times and it says ok. It plays fine in FCE but won't export to Quicktime. How do I correct the problem?

    I think I had the same problem that you are now having. I would get unexpected errors when trying to:
    1) Log and Transfer videos to external hard drives.
    2) Save my exports to an external Hard Drive.
    3) Copy large video files to the External Hard Drive.
    Assuming that you are using an external hard drive, chances are that isn't formatted correctly. It cannot be formatted in FAT32 or else large files (usually video) over 4GB cannot transfer. It may be that the file you are trying to export is larger than 4GB. If it is currently formatted FAT32 it needs to be formatted to Mac OS Extended. Hope I was of some help.

  • Error when exporting from Quicktime Pro

    I don't really like how any of the Adobe products export H.264 .mov files so my normal workflow that I've been doing for years is to export as a high quality MPEG4 and then open it in Quicktime and export as H.264 from there. I went to do this today and it gave me this error message "Export Controller has stopped working". When I click OK on that it gives me this error in the progress window:
    http://screencast.com/t/N2ZjNjcz
    I've tried this with multiple videos and got the same thing, as a test I tried exporting as MPEG4 and I got a similar error (different code). As I was typing this I tried Export For Web and got the same error. Any idea how to fix this?

    There's another thread here discussing the same error message, though not in exactly the same circumstance:
    http://discussions.apple.com/thread.jspa?threadID=2212899&tstart=0
    Perhaps something in that thread will help you.
    Good luck.
    Message was edited by: Dave Sawyer

  • Error when exporting to QuickTime

    Hello,
    I've seen a few older posts dealing with this exact same problem, but I was wondering if there has been any new development/ideas to work around it.
    I've been putting together a Keynote presentation with animations, video, and audio (all of it synchronized). To my surprise, when I tried to export it to QuickTime I got all sorts of errors. Removing the audio before exporting gets rid of the error, but if I load the generated QuickTime movie into iMovie and add the audio later, nothing is synchronized.
    Has anybody found ways around it? I would have to throw away all the hours I've invested on this presentation.
    Thanks and Regards,
    Julian

    Wow Kyn, that's quite an arsenal of resources! Thanks so much for sharing.
    Unfortunately none of those suggestions did the trick. I have Keynote 3.0.2 just in case that makes a difference.
    What I have found out though, is that the problem is related to slides that contain QuickTime movies. Following the suggestion from your last link, removing the slide that causes problems and (painfully) re-creating it does help. However at some point the recreated slide also becomes "corrupted" and QuickTime export stops working. Quite frustrating...
    One quick question...on the last link, when the author refers to the "speaker icon", where is that? I don't think I've ever seen that before...
    Kind Regards,
    Julian

  • Error when exporting from Quicktime

    I have been trying to export sound from a sound only .mov file but I am getting the error :
    Export Controller has stopped working
    The problem started after I was able to export one file. Anybody know what the problem might be? Any help would be greatly appreciated.
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: ExportController.exe
    Application Version: 7.66.71.0
    Application Timestamp: 4ba1a6fb
    Fault Module Name: CoreAudioToolbox.dll
    Fault Module Version: 7.9.2.0
    Fault Module Timestamp: 4b8efb3c
    Exception Code: c0000005
    Exception Offset: 00273469
    OS Version: 6.0.6002.2.2.0.768.3
    Locale ID: 2057
    Additional Information 1: fd00
    Additional Information 2: ea6f5fe8924aaa756324d57f87834160
    Additional Information 3: fd00
    Additional Information 4: ea6f5fe8924aaa756324d57f87834160
    Read our privacy statement:
    http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

    I have tried re-installing quicktime. Still no luck. I have also tried changing to safe mode in the preferences, again no luck. I have found out the error number from the exporter (progress bar thing) Error: 2147023174

  • I/O Error when exporting to Quicktime

    Any suggestions? Have tried exporting to various drives but same result.

    I'm editing on a Dual 2.7 GHz Power PC G5, 1.5 GB DDR SDRAM, the footage is on an external 500 GB Lacie drive connected by FireWire 400.
    FCP = 6.0.2
    Quicktime = 7.3.1
    Sequence Settings: 720 x 576 PAL, 25fps, DV PAL, 48.0 KHz, 32 Bit Gloating Point.
    Duration is 84 mins.
    Exported via in and out points via Quicktime, self contained file, current settings. Have tried exporting to the hard drive and two externals - same error. Even a small clip half way through results in a general error.
    This is the first time I've encountered this problem.
    Message was edited by: Marc Morris

  • I can not export imovie 11 to youtube. I tried exporting with quicktime so I could upload through youtube,but it had no sound. Very frustrating. When I upload through youtube it looks as if it is working, but I get no confirmation. Tried it many times.

    I can not export imovie 11 to youtube. I tried exporting with quicktime so I could upload through youtube,but it had no sound. Very frustrating. When I upload through youtube it looks as if it is working, but I get no confirmation. Tried it many times. What do I do?

    The "restore disk" is built into the Mac. See About Recovery.
    Need more specifics about what error messages you got while installing Adobe Flash.
    However, you can almost avoid Flash altogether by setting YouTube to play the HTML5 version instead.
    Click the Try something new! link at the bottom of the YouTube page.
    I don't know about the sound issue. Might be hardware as you think. Try other headphones to check.

  • Jittery motion with stills when exported to Quicktime

    I've been producing photographic AVs with FCE for a few years now and I've run into a problem with the latest version (3.5).
    Any time I use keyframes to do a Ken Burns effect it gets all jittery when exported to Quicktime. Everything plays back fine within FCE - it's only when exported that the problem occurs. The problem didn't exist (for me) with version 3. It seems to be exacerbated by adding a transition but it happens even when there's no transition.
    Has anyone experienced this or have any idea what I might be able to do to remedy it.
    regards and thanks
    powerbook 1.5ghz 1.25 GB RAM   Mac OS X (10.4.7)  

    That's what you did when you switched the field
    dominance to none, but you see you didn't see any
    effect when you did that.
    No, none at all.
    I have a fairly major show on Friday night (it's Wednesday pm here now) so I'm thinking I might spend the night redoing it in iMovie. I'm disappointed because I've been doing them in FCE for a few years now and this is the first time I've seen a problem. The only thing which has changed is the jump from 3 to 3.5.
    Many thanks for your suggestions.
    //kk

  • '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 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!
    <br>
    <br>
    Below are 2 procmon.exe outputs, the first when exporting works and the second when it doesnu2019t
    <br>
    <br>
    <br>
    1) Procmon.exe output when exporting works fine
    <br>
    <br>
    <br>HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     Desired Access: Read
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir     SUCCESS     Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     FAST IO DISALLOWED     
    <br>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
    <br>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
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>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
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     FILE LOCKED WITH ONLY READERS     SyncType: SyncTypeCreateSection, PageProtection:
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     SyncType: SyncTypeOther
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Image Base: 0x79260000, Image Size: 0x1073000
    <br>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
    <br>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
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide     SUCCESS     Desired Access: Read
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide     SUCCESS     KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest     NAME NOT FOUND     Length: 20
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide     SUCCESS     
    <br>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
    <br>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
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>
    <br>
    <br>//////////////////////////////////////////////////////////////////////
    <br>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
    <br>
    <br>
    <br>HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     Desired Access: Read
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir     SUCCESS     Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     FAST IO DISALLOWED     
    <br>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
    <br>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
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>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
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     FILE LOCKED WITH ONLY READERS     SyncType: SyncTypeCreateSection, PageProtection:
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     SyncType: SyncTypeOther
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Users\Paul\projects\temp\test\Debug\MSO.dll     FAST IO DISALLOWED     
    <br>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
    <br>C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll     FAST IO DISALLOWED     
    <br>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
    <br>C:\Windows\SysWOW64\MSO.dll     FAST IO DISALLOWED     
    <br>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
    <br>C:\Windows\system\MSO.dll     FAST IO DISALLOWED     
    <br>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
    <br>C:\Windows\MSO.dll     FAST IO DISALLOWED     
    <br>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.

Maybe you are looking for

  • Why doesn't Firefox close tabs when I use the command-w shortcut keys?

    Every so often, on random sites, I would have 2 or three tabs open. I would command-w (on a Mac) to close the front most tab, and it would close. Bringing the next tab to the front. But when I hit command-w again, I get the warning sound on my Mac, a

  • Syntax error "$P0000E0 ".

    Syntax error in program "$P0000E0 ".                                                          | What happened? Error in the ABAP Application Program The current ABAP program "SAPLV61B" had to be terminated because it has come across a statement that

  • Problem in TCODE-SM30

    Hi Experts, I came across a strange problem. I am going to SM30 and using this view BSPWDV_EHSET_ASG and making entry inside tht for the enhancement... i saved it..but i am not able to see the entry inside it... wht can be the problem..?? Its urgent

  • Joining tables in Oracle BI Discoverer Plus 10g

    My company just implemented Oracle Business Intelligence Discoverer Plus 10g and I'm a little confused. It looks like this new version of Discoverer was created with the idea of "simplifying" things for the end user. But it seems to be lacking crucia

  • Possible to burn book pages to disk?

    I am about half way through a book but need the person for whom it is being done to look at it before I continue. Is there a way to burn it to disk so I can mail it to her? She's PC, not Mac, and I think a disk would work best. Thanks to anyone who c