Winfile.cpp-759 error when exporting .flv files

Hi,
Just got over the P2 file problem (stopped using them in CS5, gone back to CS4) and a new problem has occured.
I have been exporting .flv files since I first installed CS5, suddenly today Premiere crashes when trying to export individual .flv files and so does the media encoder.
Any ideas?
Thanks

The given problem doesn't have the obvious cause. But it can be avoided.
The problem emerges after Premiere import video clips with attached audio files, while 'confoming audio'. After the conforming, the 'broken' audio files cannot be heard with playback, or incorporated in export.
There are two solutions to this problem.
First: While ripping material, or importnig previously ripped material, import separately audio and video data.
Second: If you, while working, run into audio stream that doesn't hear ( because of the given 'conforming' ), edit audio of original clip in some sound editing program ( Adobe SoundBooth, for instance ) by cuting it to new file, resampling it, saving to *.wav ( for example ) and importing it to your Premiere project, replacing the broken audio data.
That should do the trick. At least, it did it for me.
Cheers!

Similar Messages

Error When Exporting Motion File To Compressor

I don't know if this is a Motion issue or a Compressor issue, so I'm asking in both forums, I hope that's OK. I have a short Motion file I am exporting to Compressor. When the file get's to Compressor I get an error message: "Error trying to open source media file". I've exported this file many times successfuly, now suddenly I'm getting this. I've checked the files listed in the Media tab of the Motion project (control click, reveal in Finder) and all the source files seem to be where they are supposed to be. Any ideas would be greatly appreciated as I've got to get this project out the door! Thanks

I got the same problem so I hope theres somekinda solution or something I overlooked

Error when export DART file

Hi,
i m workin in project to use the DART for extract tax data and Documentum to store theses extractions and I have a problem when i export file to documentum
0) i m configuring the oac0 transction the content repository with the :
basic Path : /usr/sap/appFA1/DART/Tests1
archive Path : /usr/sap/appFA1/DART/Tests1
1) with the transaction FTWP, i configure Directory set with more one path directory :
ID , repertoire
0, /usr/sap/appFA1/DART/Tests1
1, /usr/sap/appFA1/DART/Tests3
2) i generate extaction with transaction FTWA1; this opération create 6 files. The first in the /usr/sap/appFA1/DART/Tests1 and 5 files in /usr/sap/appFA1/DART/Tests3
and the job is terminate correctely
3) i try to export this extraction to documentum with FTWF; the system transfert the first file to Documentum and the 5 others files for this extraction
This configuration work well for all DART extraction that generate only one file, but for other extraction I have the message error and the system transfert only the first file to Documentum
I hope i m clear and thank you for your help
Mohamed Karray
the job is terminate with code 9999; and i have the following message : Could not to archive (error code 5)
thank for your help

Unless you can get the code from Adobe, there's not much you can do...
I am not sure if this is what you need, but the source code for Export as XHTML can be found in InDesign SDK. (See Feature Development with Scripting.pdf)
At least, I found above-mentioned XHTMLExport.jsx file in SDK for CS3.
The source code for Export as XHTML is included in <SDK>/source/public/components/xhtmlexport.
Export as XHTML is used throughout this document to illustrate what it takes to implement a new feature using ExtendScript.
Kasyan

Error when exporting design file

I get the follwing message when trying to export a design file. Anyone knows why?
Failed: TypeError: Error #1089
Thanks!

Hello BloomandSpeak.
I am one of the developers on the FormsCentral team. If you could share your form with me ([email protected]) I can make a copy of it and dermine the cause of the problem for you.
Cheers
Chris.

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

Exporting AVI clips (error: "[\Src\Win\WinFile.cpp-759]" after 4 %)

The following problem:
I have 2 adobe premiere project. both have the same film and film length but different video codecs.
1. project (low quality video codecs (mpeg4)
export works fine
2. project (high quality video codecs (avi)
export stops every time after 4% with the following error notice:
"Premiere Pro has encountered an error.
[..\..\Src\Win\WinFile.cpp-759]"
or if I want export the project with other codecs, eg H.264 then Adobe premiere freezes and I can close Adobe Premiere then.
Premiere memory settings (valid for both premiere projects):
Installed RAM: 3,7 GB
RAM reserved for other applications: 1,5 GB
Ram available for Adobe: 2,2 GB
Optimize rendering for: "Memory"
computer details:
system type: 64 Bit
installed RAM: 3,75 GB
processor: AMD Athlon, 2 x4 635 processor 2.90 GHz
graphics card: ATI Radeon HD4200
windows edition: 7
How can I solve the problem, so that I can export my whole project in AVI codecs without freezing problems or error problems?
Is it a hardware or software problem?
Thanks in advance for your help

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 SOURCE FILE codec used... see Question 1

Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
"Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
(Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
Regards
Jouni Juntunen

CS4 Adobe Media Encoder & FMLE are two different softwares - you can post your query here:http://forums.adobe.com/community/ame

Bug report: Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
"Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
(Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
Regards
Jouni Juntunen

OK, I've reported the bug in the linked location. However, I had to use "Creative Suite" as the application, because "Adobe Media Encoder" was not an available option.
Jouni Juntunen

AVI clips export (Fehlermeldung: "[..\..\Src\Win\WinFile.cpp-759]") Premiere friert ein beim export

The following problem:
I have 2 adobe premiere project. both have the same film and film length but different video codecs.
1. project (low quality video codecs (mpeg4)
export works fine
2. project (high quality video codecs (avi)
export stops every time after 4% with the following error notice:
"Premiere Pro has encountered an error.
[..\..\Src\Win\WinFile.cpp-759]"
or if I want export the project with other codecs, eg H.264 then Adobe premiere freezes and I can close Adobe Premiere then.
Premiere memory settings (valid for both premiere projects):
Installed RAM: 3,7 GB
RAM reserved for other applications: 1,5 GB
Ram available for Adobe: 2,2 GB
Optimize rendering for: "Memory"
computer details:
system type: 64 Bit
installed RAM: 3,75 GB
processor: AMD Athlon, 2 x4 635 processor 2.90 GHz
graphics card: ATI Radeon HD4200
windows edition: 7
How can I solve the problem, so that I can export my whole project in AVI codecs without freezing problems or error problems?
Is it a hardware or software problem?
Thanks in advance for your help
Ich bin Deutscher. Ich brauche schnelle Hilfe. deshalb habe ich aus dem englischen forum mein eintrag kopiert und hier eingefügt.
Vielen Dank im Voraus

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 SOURCE FILE codec used... see Question 1

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

Float4() causes "error saving Pixel Bender Byte Code file" error when exporting for flash player

Simple test
<languageVersion : 1.0;>
kernel untitled
< namespace : "Your Namespace";
 vendor : "Your Vendor";
 version : 1;
>
 input image4 src;
 output pixel4 dst;
 void
 evaluatePixel()
 dst = float4(sampleNearest(src, outCoord()));
The above code will produce a "error saving Pixel Bender Byte Code file" error when exporting for flash player in Pixel Bender Toolkit 2.5.449694.
"dst = (sampleNearest(src, outCoord()));" works fine. And anything like "float4 a= float4(b);" will give same error.

Thank you for the error report. I'll put it into our bug database. We're bottling things up for the current version. Gven the workaround, it is unlikely we'll be addressing this bug soon. Please accept my apologies for the annoyance this will cause.
In your second example, float4 a = float4(b), does it return an error if b is only a float4 or regardless of what b is? If b is a scalar float, for example, is the conversion performed correctly? If so, this could be an error that only crops up when using constructor/conversion syntax when the thing being converted is already the correct type.
Thanks,
Chuck.

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);

Winfile.cpp-759 error when exporting .flv files

Similar Messages

Maybe you are looking for