Error when exporting in Iphoto 6

I need to export my vacation photos so that my friends with windows based computers can view full size. When I try the suggested method of exporting for use in Finder I receive an error. The error states that the folder cannot be created. What is the cause of this?
Macbook   Mac OS X (10.4.7)  

stburks:
Welcome to the Apple Discussions. Open the Users window and click one on your user folder. Then bring up the Info window for it by typing Commnad-I. In the Onwership & permissions section of that window confirm that You can "Read & Write", the Owner is you and the Group can Read and Write. If all is well there do the same for the Desktop folder inside your user folder.
If all is well there I suggest you boot into your system install disk and in the first window after the language selection window go to the Utilities menu and launch Disk Utility. There select your hard drive icon and click on the Repair Disk button. If you get a message that repairs were made repeat the process until there are no repairs reported then boot back into your MacBook.
Do you have any 3rd party plugins for iPhoto installed?
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD,   Mac OS X (10.4.7)   22 LCD Display, 200G & 160G FW HDs, Canon S400, i850 & LIDE 50, Epson R200

Similar Messages

  • Error when exporting video

    Hi,
    Got this error when exporting video. Tried to export in different formats but same error pops up.
    Any solution to this problem would be greatly appreciated. I have PreProCS5
    Thanks
    Shiva

    Similar as the last post.. copy and paste.
    Found a simple solution;
    In Iphoto, select the movie; right click on the movie and select "copy; right click on your desktop or other folder in Finder and then select "paste Item";
    The movie will be copied to that location in its original format.
    Easy solution until Apple fixes the export movie issue.

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

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

  • 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

  • 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 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 ?

  • Unknown error when exporting 32-bit 5.1 wav audio

    I get the ever useful "Unknown error" when exporting the audio from Premiere Pro CS6 to a 32-bit, 5.1 channel uncompressed WAV file most of the time. I was able to get it to work just fine by pasting the audio to a new project, but that isn't working anymore. I get the same error when I change it to 24-bit audio. However, when I change to 16-bit sound it works fine.
    First, is there a real audible difference between 16- and 32-bit when it's all going through a WAV to AC3 converter? The AC3 files get dumped into Encore as the audio track so that I can get 5.1 sound on blu-rays instead of Encore re-encoding things.
    Second, what would cause it suddenly not work, and how can I get it working again?

    That error can happen for many reasons...one of the reasons that I occassionaly get it is because I try exporting a movie to an external drive that has been formated in the old FAT32 instead of the NTSF standard.  FAT32 only allows for file sizes up to 2 gigs.  And as soon as it reaches that...I would get that error.  I don't know if that is why you are getting that error...but it would be easy to check.  1) are you generating a file that is over 2 gigs?  2) is your drive that you are exporting to FAT 32 (just right click the drive in My Computer and select "properties" then just look for what it says next to "file system".

  • 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 ABAP Programs and the Project

    Hi All,
    I keep on getting the following errors when I'm exporting the entire Project or only ABAP Programs (see attached screenshots).
    - Screenshot 1 shows an error when exporting a Project.
    - Screenshot 2 shows an error when exporting ABAP Program(s).
    These errors occur in the DEV environment.
    Please help.
    Thank you all.
    Kind regards,
    Roli

    Hi Ramakrishna,
    I will send the log file for when exporting a project. However, the issue of exporting ABAP Programs is nor resolved.
    In CMC we had to configure the system to Generate ABAP = True.
    Thank you.
    Kind regards,
    Roli

  • JS error when exporting to HTML

    Hi,
    I'm getting JS error when exporting to HTML.
    When publishing to catalyst, all functions are OK, but when exporting there're lots of bugs and I get the error message.
    Pop-up attached.
    Please advise,
    Avi

    Hi, Sorry for the late response, are you still experiencing this issue. If yes, please let me know

Maybe you are looking for

  • Problem with iCloud and E-mail set-up

    I have been trying to set-up an iCloud e-mail account but keep getting the messages that it cannot set-up the account. Problems from the iCloud control provide the message that I should use the e-mail preferences to set-up the account, the e-mail pre

  • Problem related to Outbound Delivery creation via Background Job

    Hi , We are using the program RVV50R10C for creating OBD incase of STO . Z variant is created to take care of selection parameters which inlcudes Shipping Point , Delivery creation date , Calc Rule, Delivery priority and shipping conditions. The job

  • Laptops screen wont light and the system will not boot most of the time.

    my hp lptop g62 started not booting up and the monitor would not light  up sometimess even though it would power up. as time passed it had that problem more frequently. now it wont boot at all and the monitor wont light up at all  .  it will still po

  • DV9720US - Speakers won't mute with headphones plugged in.

    I am running XP instead of the Vista it came with. I have all the drivers but one work..(other devices> unknown device) with yellow !?  I can't use my headphones because speakers won't mute. Is this a hardware problem, or something electronic broken,

  • Problems sending texts.....

    Hi Everyone Bit of strange one, it's got me a bit confuddled, wondered if anyone could help please? I've got an iPhone 4s, and I've a problem sending texts/imessages... It sends fine when I'm replying to a thread of messages but if I start a 'new' te