Error when export application from navigator bar

hello, i had this error when export one application.
Error: ORA-06502: PL/SQL: numeric or value error (WWV-11230)
Unexpected error encountered: ORA-06502: PL/SQL: numeric or value error (WWV-15200)

Which version of portal you are using?
And what is the language installed ?

Similar Messages

Error when downloading application from Server

Hi,
I have installed MI Client 7.0 SPS 11 Patch 0 on Symbol Device ;OS Windows Mobile5.0
i have successfully completed first synchronization .
After that i assigned Mobile Component to the device and tried synchronizing.
"Error when downloading application from http://<servername>:50000/meContainerSync/servlet/com.sap.ip.mi.http.MobileComponentServlet?Application=xyz&Type=APPLICATION&Runtime=JSP"
Pl. suggest
Note: In NWA under 'Device Maintenance' -> Mobile component
The state of the aplication is "Deployment Activated"
rgds,
Kiran Joshua
Message was edited by:
Kiran Joshua

Hi ALL,
I resolved it on my own guys !!!
Actually while downloading server url consists of hostname bcoz the hostfile entry in windows/system32/drivers/etc/hosts was only hostname.
i entered FQDN name in the hostfile... It WORKED
Being Saturday and Sunday...i cud not get any help from forums...i was really worried and Guys we need to think on this :-?
rgds,
Kiran Joshua

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 quizzes from Captivate 2 to Flash 8!

Here is the error that I get when trying to Export quizzes
from Captivate 2 to Flash 8.
"An internal Adobe Captivate error (bad argument) occured. If
you have any questions please contact Adobe Technical Support."
I've noticed that this only happens if there are quizzes in
the project. I have tried everything that Adobe FAQ's and TechNotes
had to offer.
They said that the CP file could be corrupt. If that's the
case, Every file that I create with a quiz is corrupt. I have just
upgraded from Flash MX to Studio 8 and just bought the new version
of Captivate 2. These were both downloaded via try/buy.
If anyone is familliar with this problem, any suggestions
would be greatly appreciated.
Thank you!

Answering my own question.....Received this fix:
I think that I know what you did. When you had Captive 1 you
changed a dll file in order for it to work with Flash 8. They
forgot to mention that if you did this fix back in 1.0 that it
would corrupt the process in 2.0.
Go here:
C:\Documents and Settings\<UserID>\Local
Settings\Application Data\Macromedia\Flash
8\en\Configuration\Importers
Make sure this is the only file in there: RDMFISTUB8.DLL
That should solve your problem.

Error when exporting IDOC from one XI system to another

Hi all,
When I do an export for an IDOC from my one XI server to be able to import it into another I get the error below. The funny thing is that it works perfectly for my COND_A idoc but not at all for DEBMAS and MATMAS idoc.
Any ideas?
Error during export. Internal error during pvc call: SAP DBTech JDBC: Result set is positioned after last row.
Regards,
Liesel

Hey,
I guess you are using MAXDB,
please read note number 1055246
(Inconsistent XI content caused by bug in MAX DB)
Good luck!

Update error when installing application from Ovi

my phone is nokia e72 i instaling app for ovi but sho update errer
Moderator's notes: The post was edited. A more appropriate subject is provided.

Expect to see these screens, but should still be functional:
Happy to have helped forum in a small way with a Support Ratio = 37.0

SSRS XML Errors when exporting to .xlsx from Dynamics NAV Database

We use Dynamics NAV for our ERP and have many SSRS reports. We get xml Errors when exporting to Excel .xlsx. I've seen this happen since SQL 2008 R2 and have posted in many places trying to find an answer, but was hoping MS would solve the
issue. The numeric data types in the Dynamics NAV database are all decimal(38,20) and when the value is zero the Excel renderer throws the errors.
We now have over 400 reports and we export them to Excel 2003 format. I'm starting to feel like this is my new Y2K issue when Excel 2003 is set to sunset. I'm fearing that I'll have to do conversions on all numeric data types for all reports.
Both of these are Microsoft products so I'm wondering is this even on their radar.
We're running SQL Server 2012 SP2, and just rolled out CRM 2015 on SQL Server 2014. I get the errors in SSRS 2008R2, 2012, and 2014. Has anyone seen this before?
Timothy Kruse

Hi Skywalker73,
According to your description, when you export the report to Excel, the error “Excel was able to open the file by repairing or removing the unreadable content.” throws out when opening the Excel file.
Based on my research, it has reported the same issue when exporting to Excel. The issue could cause by numeric columns has a precision of 16 or higher. To fix the issue, we could change data type in the table to a support lower precision, or convert
the numbers in the stored procedure that populates the report. For more information, please refer to this article:
SSRS 2012 Bug – “Excel found unreadable content”. Besides, please refer to this
article to check if non-printing characters exist in the report.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

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.

Crashes when running applications from network share - "Windows cannot access the file for one of the following reasons"

Hi,
starting a couple of weeks ago, we get the following error(s) when running applications from a network share. We don't know what causes this, we are not aware of any major changes in our network infrastructure or client/Server configuration. We did upgrade
a lot of machines to Windows 8, but the issue also occurs on older Win7 computers.
We figured out a workaround though: The applications run fine when launching from a FQDN share (like
\\share.domain.Company.com) and only cause problems when running from
\\share directly. They have worked fine for years without FQDN though.
Any ideas?
Error Details (the Kind of error differs greatly):
# 1 #
Log Name: Application
Source: Application Error
Date: ...
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: vmDEV
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program XYZ
because of this error.
Program: XYZ
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional data
Error value: C000020C [ also seen with code C00000C4]
#2 (German error Messages from now on, we only use German OSes, the above english one is translated based on similar error Messages I found on the web) #
Name der fehlerhaften Anwendung: XYZ.exe, Version: 2015.0.496.5054, Zeitstempel: 0x54ea67c3
Name des fehlerhaften Moduls: clr.dll, Version: 4.0.30319.34014, Zeitstempel: 0x52e0b784
Ausnahmecode: 0xc0000006
Fehleroffset: 0x00026549
ID des fehlerhaften Prozesses: 0x13ac
Startzeit der fehlerhaften Anwendung: 0x01d055a854d36445
Pfad der fehlerhaften Anwendung: \\share\application.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Berichtskennung: 949ea933-c19b-11e4-bf04-78542e186754
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Anwendung: XYZ.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000006, Ausnahmeadresse 720B6549
Stapel:
# 3 #
Anwendung: WpfApp.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
Stapel:
   bei SP.Forms.AutoCompleteSelectionBase.OnEnter(System.EventArgs)
   bei System.Windows.Forms.Control.NotifyEnter()
   bei System.Windows.Forms.ContainerControl.UpdateFocusedControl()
# 4 #
Anwendung: WpfApp.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
Stapel:
   bei System.IO.UnmanagedMemoryStream.ReadByte()
   bei System.IO.BinaryReader.ReadByte()
   bei System.IO.BinaryReader.Read7BitEncodedInt()
   bei System.Resources.ResourceReader._LoadObjectV2(Int32, System.Resources.ResourceTypeCode ByRef)
   bei System.Resources.ResourceReader.LoadObjectV2(Int32, System.Resources.ResourceTypeCode ByRef)
   bei System.Resources.ResourceReader.LoadObject(Int32, System.Resources.ResourceTypeCode ByRef)
   bei System.Resources.RuntimeResourceSet.GetObject(System.String, Boolean, Boolean)
   bei System.Resources.RuntimeResourceSet.GetObject(System.String, Boolean)
   bei System.Resources.ResourceManager.GetObject(System.String, System.Globalization.CultureInfo, Boolean)
   bei System.Resources.ResourceManager.GetStream(System.String, System.Globalization.CultureInfo)
# 5 #
Anwendung: WpfApp.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.Runtime.InteropServices.SEHException
Stapel:
   bei System.Reflection.RuntimeParameterInfo.get_Name()
   bei System.Diagnostics.StackTrace.ToString(TraceFormat)
   bei System.Environment.GetStackTrace(System.Exception, Boolean)
   bei System.Exception.GetStackTrace(Boolean)
   bei System.Exception.ToString(Boolean, Boolean)
   bei System.Exception.ToString(Boolean, Boolean)
   bei System.Exception.ToString(Boolean, Boolean)
   bei System.Exception.ToString()
# 6 #
Name der fehlerhaften Anwendung: XYZ.exe, Version: 2015.0.496.5054, Zeitstempel: 0x54ea834f
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.3.9600.17278, Zeitstempel: 0x53eeb460
Ausnahmecode: 0xe0434352
Fehleroffset: 0x00012f71
ID des fehlerhaften Prozesses: 0xa68
Startzeit der fehlerhaften Anwendung: 0x01d0559cb7ec4ed6
Pfad der fehlerhaften Anwendung: \\share\XYZ.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Berichtskennung: 010514d0-c190-11e4-bf04-78542e186754
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
# 7 #
Name der fehlerhaften Anwendung: XYZ.exe, Version: 2015.0.496.5054, Zeitstempel: 0x54ea7a6e
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.17630, Zeitstempel: 0x54b0d74f
Ausnahmecode: 0xc0000006
Fehleroffset: 0x0006db27
ID des fehlerhaften Prozesses: 0x18dc
Startzeit der fehlerhaften Anwendung: 0x01d0559cb08529c3
Pfad der fehlerhaften Anwendung: \\share\xyz.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: ef389186-c18f-11e4-bf04-78542e186754
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Hi,
>>The applications run fine when launching from a FQDN share
It sounds like a DNS suffix issue. When this issue occurs, please try to ping share on the client, then check if the corresponding IP address is correct. If the IP address is wrong, please adjust your settings of DNS to make sure that the client can resolve
the share correctly.
If it's very hard to change the settings of the DNS for some reason, as a work around, we can add the entry into the clients' hosts file.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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 a pdf in SAP

She sends me the error when exporting a pdf from the SAP system, this is the message:
X Object reference not set to an instance of an object.
I hope I can support.
Annex image

See your other thread.

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.

Access denied error when starting DIAdem from LabVIEW

We are using the DIAdem Connectivity Toolkit in our application. Our application starts a DIAdem session to handle querying and datasheet creation. On a recent installation at a customer, our application was not able to communicate with DIAdem, i.e. we get an Access Denied error when our application tries to start up DIAdem.
The location of the error is in the DIAdem Open Connection.vi. I believe it is when the Automation Open is run.
Is there some system setting that could be blocking communication between the two, i.e. ActiveX setting, etc? If so, where could we control these settings from?

Hello Derrick,
While cBauer is away from the office, I will be working with this case on his behalf. I will try to answer your questions as best I can to determine what might be causing this failure.
1. The error which we encounter is an "Access Denied" error (as stated above). I am currently investigating the error code, and will update this post accordingly when I have it.
2. Our application is a built (.exe) application using LabVIEW 8.5 and DIAdem 10.2
3. We do not install the toolkit directly on the customers machine as this is a built application. We install the FULL LabVIEW 8.5 Runtime engine, as well as a licensed copy of the DIAdem 10.2 Basic edition.
4. The error occurs in run-time environment at a customer site. We have been unable to duplicate the error in development.
5. We're using the "DIAdem Open Connection.vi" from the DIAdem.dll library to initialize the connection (this is the VI which appears to be producing the error via the "Automation Open" node), and we're using the "DIAdem Close Reference.vi" from the same library to close the reference.
6. I will instrument a simple application which performs these tasks and post the results when we have tried this operation.
7. I am unsure whether the repair operation has been attempted. I will verify this behavior and again post the results to this forum.
Thank you for your help. Please let me know if you require additional information. Hopefully we can discover a solution to our problem.
Ken

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?

CS5: Bug when exporting directly from PPro with hardware MPE?

For the record, I'm using:
A GTX-480 (unsupported)
The hardware MPE-enabling hack (unsupported)
The latest version of the nVidia drivers (257.whatever)
I discovered an issue, of sorts, when exporting directly from Premiere CS5, versus using the "Queue" option to send to AME. I was exporting from an NTSC DV Standard sequence to a 320x240 H.264, in which I had enable cropping and trimmed a bit off the sides and top and bottom of the source; the Output tab was summarily set to "Scale to Fit". With hardware MPE enabled in the Project Settings, the export would be the proper final dimensions (320x240), but any area that was cropped off was instead padded with black. The actual video content was then squeezed and malformed into the area not occupied by the black bars.
I found that, if I disabled hardware MPE or sent the export through AME by use of the Queue button (instead of Export), then the export was performed properly--the video was cropped correctly and then the video stretched to the borders of the exported video, maintaining the desired aspect ratio.
As I mentioned at the outset, I'm breaking a couple rules and perhaps tempting fate with others, but before I go about rolling back my drivers and the like, has anyone noticed a similar issue?
ADDENDUM: By the way, the export doesn't need to come from a sequence. If I load up a source clip into the Source Monitor, and export from there using the process outlined above, I get the same issue. This would seem to indicate, to me, that this is due to some incompatibility with my card, its driver and hardware MPE...

Did he demo renders or exports?
About 11 minutes in, he [Dave] demos accelerated H.264 renders.
Harm Millaard wrote:
AFAIK MPE only works with renders, not with encoding.
Well, he did both, actually--but the quote above is a typo on my part. I meant to say "exports" or "encodes." The last couple minutes of the aforementioned demo video are dedicated to exporting a sequence directly from Premiere, and having the benefit of hardware MPE. That's where I'm getting the issue I've outlined above; with hardware MPE enabled, and using the "Export" versus AME "Queue" button/function, I get the strange black outline. With software MPE or through AME, all is well.

Error when export application from navigator bar

Similar Messages

Maybe you are looking for