New Lightroom 5.4 export jpeg error?

I have just installed the Lightroom 5.4 upgrade (on my MacBook Pro) and attempted to export a JPEG. It complained of a "Access to undefined global: newGrainSeed   (1). Any help would be appreciated. Thanks.

Brilliant and thanks for reporting back.... I looked at it and went "what"??????

Similar Messages

  • Lightroom 4.1 exported JPEG files are not recognized by Apple Preview App

    I just started using Lightroom 4.1 Trial version (coming from Aperture). I exported JPEG versions of some images using an ICC profile. On my iMac running Lion 10.7.5 the pictures do not show a thumbnail, the file on the desktop just shows "JPEG". I could not open the file with the Preview App, but I am able to open it with DPP (Canon software)? Also the file shows that it has 0 x 0 dimentions when I click Get Info even though it is about 25 Megs in size?
    The message I get is
    "The file “Edit-739820120223Canon EOS 7D.jpg” could not be opened.
    It may be damaged or use a file format that Preview doesn’t recognize."
    Does anyone know why this is hapening?
    Is it a know issue between Adobe and Apple?
    Is there a fix for this?
    Thanks for help in advance.

    25MB is quite a large filesize for a JPG, and this might be either quite a lot of pixels saved at a very "high" quality (not very much compressed), or it may be an extremely large number of pixels saved with medium compression.
    While the technical spec of the JPG format imposes an absolute limit on maximum width and height pixel dimensions, some software employs a lower limit above which it considers the file to be invalid. Different programs, different limits, sometimes.
    I have encountered this (for example) with pano stitched images using the full resolution of a large number of component shots - where JPG output could not be made, or if made, could not even be viewed as a whole by my standard image viewer (though TIFF was still OK even at still larger sizes).
    If Lightroom has been set to a large printed size AND to a high ppi resolution, it is easy to get into very high numbers and very large output files. One should IMO at least question the utility and benefit of using very high ratios of upsampling from a standard digital photo - which may happen in some cases as a result of using the same output settings regardless, when spreading the same data across both small and large scales. If the file that was imported into LR really does provide an unusually high number of pixels expressing lots of detail, then that will better deserve such a capacious output file. Otherwise, each part of the file may merely show a very highly detailed representation, of a very blurry nothing-much-in-particular.
    If the JPG has exceeded the viewer's size limits, a reported width and height of 0 may represent an error message, in effect - not actual reality.
    regards, RP

  • Lightroom to Photoshop export. Error upon saving to jpeg "Could not complete your request because of a program error"

    Lightroom 2.4 to Photoshop CS2. My export parameters in Lightroom are Resize to fit W&H 850 pixels (for web), resolution 300 ppi. Export as TIF, sRGB, 8 bits. When I go to save as Jpeg, quality 10, I get the above error. I only get this error after I have used the adjustment brush in lightroom, and that is the problem. If I don't use the adjustment brush it saves fine. Now this is a recent issue. I have used the adjustment brush multiple times on a single issue in the past with no problem. Lightroom crashed about 2 weeks ago but I got everything up and running. I have reinstalled Lightroom and I have reinstalled Photoshop with no resolution. I have tested this may times and it's definatly the adjustment brush issue. If you have any ideas or experience like this I would appreciate some help.  Thanks

    You could try removing the Lightroom/ACR adjustment settings using File Info in Bridge or Photoshop. The screenshot included below shows the two items that you should remove.
    Note that camera-raw-settings will definitely appear in the list, but camera-raw-saved-settings will only be listed if you had a Snapshot in Lightroom (normally at least one is automatically created)

  • I want to install lightroom previously installed on a macbook on a new macbook. I get an error message when I try to use the same serial number. How can I install lightroom on my new mac?

    i want to install lightroom previously installed on a macbook on a new macbook. I get an error message when I try to use the same serial number. How can I install lightroom on my new mac?

    Oliver,
    Are you getting activation errors? As Ned stated , it is easier to troubleshoot if we have the specific type of error and error detail that you are getting.
    Here is some help on activation if this is the issue:
    https://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
    Pattie

  • Exporting Jpegs from Lightroom - DPI question

    When I export Jpegs from Lightroom, I set the dpi to 300 pixels per inch. I do not specify a max width or height. When I view these files in Adobe Bridge (CS2 or CS3) the file info says 300dpi. However, when I open the files in Photoshop and select image size, It says 72dpi and has the document size set to very large. I realize that I can enter 300 dpi and uncheck the resample box, I am just confused as to why this is happening.
    My concern is, that I upload my images directly to my lab after exporting from Lightroom. Will this cause problems?
    Thanks in advance!
    David

    the image resolution is a combination of the two parameters you mention: size and dpi. a very large size at 72 dpi is equivalent to a small size (like 3x5) at very high dpi. for printing you want at least 240 dpi at the largest size that allows you to keep that resolution. for screen presentations or your web site you want jut 72 dpi. 72 dpi and 2x3 inches will require a very small file size.
    I suggest you to export images at TIFF and not JPEG as that will allow you to preserve the image quality when doing editing in PS.
    In my case I export TIFF for PS (when I need PS editing) and 72 dpi JPEG for my web site (that way if somebody downloads my image illegally thy get a poor resolution copy). But since LR works very well for me 90% of the images re just kept in raw mode and I print from LR.

  • I had a free trial of Lightroom 5 and tried to purchase it, but page errors blocked me from being able to do this. I then got a free trial of Adobe CC.  At first I saw my old photos, then the whole thing went down, and now I have a new Lightroom 5 trial,

    I had a free trial of Lightroom 5 and tried to purchase it, but page errors blocked me from being able to do this. I then got a free trial of Adobe CC.  At first I saw my old photos, then the whole thing went down, and now I have a new Lightroom 5 trial, and none of my edited photos.  Can I retrieve all these photos from my first trial?

    Yes, you have to find the catalog file from the CC trial (use your operating system to search for it, the file name ends with .LRCAT), and then once you find it, open the LR5 trial and open the catalog you just found using File->Open Catalog

  • Have downloaded new Lightroom 5.4 from CC. When trying to launch am getting following error message and then Lightroom crashes: "an error occurred when attempting to change modules". Can't find a thread which relates to this error message.

    Have downloaded new Lightroom 5.4 from CC. When trying to launch am getting following error message and then Lightroom crashes: "an error occurred when attempting to change modules". Can't find a thread which relates to this error message.

    Hi 99jon,
    Many thanks for that. Had been going through this list yesterday and now again today:
    Ref  Solution 1: Lightroom is at its latest update
    Ref  Solution 2: It's interesting how I cannot find the Preferences file anywhere on my mac. (new mac pro, OS 10/9.2) . . .
    Ref  Solution 3: Lightroom doesn't allow me to do anything after the error message appears
    Ref  Solution 4: don't have any Nik Software plug-ins
    Ref  Solution 5: checked permissions and changed all to "Read & Write" - makes no difference
    Ref  Solution 6: I don't have a different user account on my mac.
    Not sure what else to do.

  • Very dull color of Lightroom exported JPEG

    My exported JPEG images from Lightroom turn out to be very dull in prints. My monitor is calibrated with EYE ONE (Color Management System). Used correct color space for the printing company (either sRGB or AdobeRGB) I followed instruction about Export process. But still color is not right. Is there anything I should do to get the same color quality as I see in the Lightroom? I think images in the lightroom show much brighter than they are after print (by printing company like Costco/Blurb/Shutterfly) Thank you very much for your help!

    You need to have your monitor fairly dim (80-130 lumens or so) to reproduce color. I thought eyeone actually calibrates brightness but I could be wrong. Most people have their monitors set far too bright. Next, you need to look at your pictures using a good fairly bright lamp with much higher color temperature than most desk lamps. If you are getting dull prints (as opposed to just dark) the likely culprit is the wrong colorspace or bad calibration. Some calibrators simply turn out to be broken. Do the pictures look dull too after export in another managed app such as Photoshop, preview, etc? Lastly, you have to realize that it is simply not possible to reproduce every color you can see on a good screen on paper. This can lead to lower saturation. This is the reason why soft proofing is important, which unfortunately is not yet possible in Lightroom.

  • Cannot install new Lightroom.  Keep getting error code 58

    Cannot install new lightroom CC.  Keep getting message of error code 58.

    It's usually a better bet with a 2330, but I think we'd better check for disk/file damage on your C drive.
    The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • Lightroom 5 cannot export files in original Raw format (LR 5.4, Mac, OS 10.9.4).

    A client has the following problem: When trying to export files in the original Raw format (.CR2), the operation failed and a dialog informs us that "Some export operations were not performed". We can export JPEGs just fine.
    After lots of testing, this is what we discovered:  The problem does not appear to be catalog-based; we run into the same problem using a test catalog.  The export operation works fine, however, with the same test catalog and images on two other machines, and it even works fine on the same machine with a new user admin account that we created. 
    So it appears to be something associated with the user account, , or with how LR is interacting with the user account, but I cannot figure out what it might be. We can copy the Raw files when using the Finder to do so. But not via Lightroom.  Any thoughts, ideas of suggestion would be greatly appreciated!  Thanks, Sean

    As part of your testing make sure you've tried exporting JPGs from the same folder as the CR2s you're exporting as original, and export JPGs from CR2s to the same folder as you're exporting your originals.  This would test LR's read and write permissions from and to the folders being used.
    From this document you can see that all the LR files other than the program, are under the /Users folder with different values possible for each user, so the difference could be that the users that work are using the original LR defaults, if you have just started using LR with them after you started having this problem, or at least that the user with the problem has some oddball settings that are interfering with Export as Original.
    Preference and other file locations in Lightroom 5
    You can test for the Preferences being off by either copying the preferences from a user that has the problem to a user that doesn't have the problem--probably through an external or common folder, or be deleting the preferences file from the user that has the problem and see if it resolves.  Moving the preferences file or renaming it may be better than deleting it if no change is seen, then you can restore the preferences back by moving or renaming the file back to the original location and name.

  • Bloated exported jpegs??

    I start by importing a 4 meg file (jpg). Apply a few Lightroom tweeks and export jpg (quality 100%) and file size triples to 12 megs. Why so big?
    I can lower quality to 80% and then it is pretty close to the original. But I prefer not to do this.
    I have also noticed a much bigger file size when exporting web galleries and have to drag the sliders down to about 60% quality to keep files small for web viewing.

    Lora, here is what I think is happening. The JPEGS you started with are expanded to uncompressed images within LR's rendering pipeline, simply because they have to be in order for LR (or any other imaging application) to work with them. At this point, they in memory and are MUCH larger than the JPEG files you started with since they are not compressed.
    After processing, when you tell LR to do an Export, the JPEGS you started with are expanded to uncompressed images within LR's rendering pipeline, simply because they have to be in order for LR (or any other imaging application) to work with them. At this point, they are MUCH larger than the JPEG files you started with.
    LR then proceeds to apply all of your edits to the files, and then it creates new JPEGs in whatever folder you told it to export to. The new JPEGs are compressed using the settings in the Export dialog, and if you choose a higher image quality than the original JPEGS, they can certainly be be larger than the original files.
    Note that I am NOT saying that the new JPEGs will actually be higher quality than the originals. JPEGs use lossy compression, so whatever compression was used to produce the original JPEGS threw content away that can never be recovered. But the LR doesn't care about that, and works on the contents of the file as it had pristine originals to work with, so it's very possible to tell it to produce JPEGs that are larger than you started with. It's just that there is not much point to actually doing so.
    Don's suggestion about Auto Export doesn't really apply here, since it refers to files that are within the Library. Exported files, such as we're talking about, will ALWAYS get the metadata written into the file, unless you have turned on the "minimize metadata" checkbox in the Export dialog. I'd have a hard time believing that this is the sole cause of the size increase, though; metadata shouldn't take up more than a few kilobytes even in a worst case scenario.
    Bottom line: set the Export JPEG quality to your needs, without regard to what the original JPEG sizes were.

  • Lightroom 4.1 export problem

    Lightroom 4.1 will not export a deleloped image.  I have the metadata to new file set to automatic and I get no error mesage.  All my new exported files are the same as the original.  I need a detailed discription of what boxes need to be checked or unchecked and where to find them.  Something as simple as saving changes so that I might use them in another app should not be so difficult- version 2.7 worked fine so what's up with 4.1? 

    Still no luck... I just purchased a licence for my demo version- I was hoping not to have to do  a 1.1Gb download and/or redo my my catalog- is this required?
    Date: Sun, 17 Jun 2012 00:37:57 -0600
    From: [email protected]
    To: [email protected]
    Subject: Lightroom 4.1 export problem
        Re: Lightroom 4.1 export problem
        created by ssprengel in Photoshop Lightroom - View the full discussion
    Are you saying that LR4 is exporting over the top of your exiting images, or that it is not exporting anything?   To test whether you can export anything, try exporting to a subfolder under your originals, instead of new names in the original images folder, which I think is what you’re saying you’re attempting: On the Export panel, all the way at the top, make sure to set Export To: to Hard Drive. Set the Export Location – Export To:  value to Same folder as original photo. Put a checkmark next to Export Location – Put in Subfolder Enter in “output” into the Export Location - Put in Subfolder: textbox. Uncheck the Add to this Catalog unless you really want to include the output of this experimental export in the catalog. Set Export Location - Existing Files to Ask what to do, so LR will indicate if it’s trying to overwrite the same files, again, which it should if the output subfolder is empty. Uncheck the File Naming – Rename To: so the files aren’t renamed. At the bottom change Post-Processing – After Export to Show in Explorer Click the Export button and see what happens.  It should do the export then open up Windows Explorer on the output folder you specified.    Before doing any of this, it might be wise to make a screenshot of your current Export settings, the Export To and File Naming sections at least, which you can both post here and use to reset things back from what I’ve specified, above.
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4498854#4498854
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4498854#4498854. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Photoshop Lightroom by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • EXPORT XFA error while writing XFA files

    Hello Experts,
    We are facing an error while exporting to PDF from BEx report.
    We are on EP7 SP14. BI on SP16.
    After the report is displayed and Export to PDF button is clicked, a new window opens which shows following:
    1. Error:
    Message: No message was provided.
    Stack trace: java.lang.NullPointerException
    at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
    at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
    at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
    at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
    at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
    at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
    at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
    at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
    at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
    at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java
    :33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Message: EXPORT XFA error while writing XFA files
    Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: EXPORT XFA error while writing XFA files
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:311)
    at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
    at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
    at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
    at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
    at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
    at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
    at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java
    :33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NullPointerException
    at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
    at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
    at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
    2. Message:
    No metadata is available for "DISABLE_NAVIGATION":
    <parameterList>
      <param name="BI_COMMAND_TYPE" value="OPEN_DIALOG_DISABLE_NAVIGATION"/>
      <param name="TARGET_DIALOG_REF" value="DISABLE_NAVIGATION"/>
    </parameterList>
    In this window, complete screen of report is displayed as an image instead of PDF.
    Please let me know if anybody faced similar issue earlier.
    It was working perfect earlier, but suddenly error started.
    regards
    Kedar Kulkarni

    No proper findings, but issue resolved.
    Problem i found that we got a domain change and service values were not refreshed until we apply new patch.
    So when we applied patch level 6 on BI WEBAPP& BI BASE S URL for ADS got refreshed and we faced the issue.
    After resetting the URL to new domain problem got resolved.
    Regards
    Kedar Kulkarni

  • Lightroom 5: All photos now "Error working with this photo"

    I went back to my lightroom catelog, where a lot of my photos are all on my NAS, and now all the photos are unable to be edited. "There was an error working with this photo."
    Everything was working for awhile, but now every single photo is erroring out.
    In the finder, i still see the photos perfectly fine. I even opened up the good 'ol Photo Mechanic 5 and opened a contact sheet, and these photos still worked. So it's not like they're corrupted or completely gone.
    I created another new lightroom catelog, and tried to import the photos again. But when I select the directory the photos are in, it's empty for about 10 minutes, then shows all the photos but with "Preview unavailable for this file."
    The big caveat are all these photos are on a networked NAS (Synology). I'm accessing it over WiFi which is probably the biggest problem.
    The folder was mounted as a NFS folder. It was disconnected once when I had a power outage (damn wind). I since re-mounted the folder and all that. I'm not entirely sure if that's what did it or if these errors started happening after that or not. But I've moved photos to my NAS folder in my catalog just today, and they are now erroring as well. So it's not like the older ones are erroring. Just all of them are.
    Mac OSX - Mavericks 10.9
    32GB Ram / 3.4GHz Intel Core i7
    Lightroom 5
    Files are all: DNG/ARW/NEF

    I'm sorry I can't be more helpful, but there are lots of messages in the forums about Lightroom problems specifically related to Synology NAS. 
    Have you spoken to Synology about this?

  • Invalid Export Options error

    Post Author: Kit
    CA Forum: .NET
    Why would an export to html, which has for many months  performed correctly, suddenly start producing the "Invalid export options" error?Our application is a Microsoft Dynamics GP third party add-on, developed in Dexterity ( The MS Dynamics GP native development tool) and using a home-grown .NET component to export reports to HTML.In our scenario we have a production environment where three reports are produced each evening, exported to HTML, and then published via FTP. Crystal 10 is installed on the server. This has worked well for a long time but lately one or more of the three  reports have failed each time, with a "Invalid export options" error.The failure is not consistent -  for example one time the first two reports were successful, but the third failed, but the next time the first two both failed, whereas the third was succesful.Ou first thought was that the error could be caused by a bad report setup within the Dexterity side of the application, however we have investigated this possibility and debugged the application and can find no likely cause there.Here's the error;CrystalDecisions.CrystalReports.Engine.InvalidArgumentException: Invalid export options.   at CrystalDecisions.CrystalReports.Engine.EngineExceptionUtils.DoThrowException(String message, EngineExceptionErrorID id)   at CrystalDecisions.CrystalReports.Engine.ExceptionThrower.ThrowEngineException(String messageID, EngineExceptionErrorID id)   at CrystalDecisions.CrystalReports.Engine.HTMLExporter.GetPage(Boolean bSeparatePages, Boolean bDHTML, Int32 startPage, Int32 endPage)   at CrystalDecisions.CrystalReports.Engine.HTMLExporter.Export()   at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)   at CrystalDecisions.CrystalReports.Engine.ReportDocument.Export(ExportOptions options)   at KIT.Crystal.RunReport()" KIT.Crystal.RunReport is from our component, and contains the following code                    rptDoc = SetupRptDoc();                    // Set the options for saving the exported file to disk                    destOpts = new DiskFileDestinationOptions();                    destOpts.DiskFileName = outputFilename;                    expOpts = new ExportOptions();                    expOpts.DestinationOptions = destOpts;                    // Set the exporting information                    expOpts.ExportDestinationType = ExportDestinationType.DiskFile;                    switch (exportFormat)                    {                        case ExportFormatEnum.CRS:                            expOpts.ExportFormatType = ExportFormatType.CrystalReport;                            break;                        case ExportFormatEnum.DOC:                            expOpts.ExportFormatType = ExportFormatType.WordForWindows;                            break;                        case ExportFormatEnum.HTML:                            htmlOpts = ExportOptions.CreateHTMLFormatOptions();                            htmlOpts.HTMLBaseFolderName = new FileInfo(_outputFilename).DirectoryName;                            htmlOpts.HTMLFileName = new FileInfo(_outputFilename).Name;                            htmlOpts.HTMLEnableSeparatedPages = false;                            htmlOpts.HTMLHasPageNavigator = false;                            expOpts.ExportFormatOptions = htmlOpts;                            expOpts.ExportFormatType = ExportFormatType.HTML40;                            break;                        case ExportFormatEnum.RTF:                            expOpts.ExportFormatType = ExportFormatType.RichText;                            break;                        case ExportFormatEnum.XLS:                            expOpts.ExportFormatType = ExportFormatType.Excel;                            break;                        case ExportFormatEnum.PDF:                        default:                            expOpts.ExportFormatType = ExportFormatType.PortableDocFormat;                            break;                    }                    //Export the report                    rptDoc.Export(expOpts);

    Post Author: Kit
    CA Forum: .NET
    Why would an export to html, which has for many months  performed correctly, suddenly start producing the "Invalid export options" error?Our application is a Microsoft Dynamics GP third party add-on, developed in Dexterity ( The MS Dynamics GP native development tool) and using a home-grown .NET component to export reports to HTML.In our scenario we have a production environment where three reports are produced each evening, exported to HTML, and then published via FTP. Crystal 10 is installed on the server. This has worked well for a long time but lately one or more of the three  reports have failed each time, with a "Invalid export options" error.The failure is not consistent -  for example one time the first two reports were successful, but the third failed, but the next time the first two both failed, whereas the third was succesful.Ou first thought was that the error could be caused by a bad report setup within the Dexterity side of the application, however we have investigated this possibility and debugged the application and can find no likely cause there.Here's the error;CrystalDecisions.CrystalReports.Engine.InvalidArgumentException: Invalid export options.   at CrystalDecisions.CrystalReports.Engine.EngineExceptionUtils.DoThrowException(String message, EngineExceptionErrorID id)   at CrystalDecisions.CrystalReports.Engine.ExceptionThrower.ThrowEngineException(String messageID, EngineExceptionErrorID id)   at CrystalDecisions.CrystalReports.Engine.HTMLExporter.GetPage(Boolean bSeparatePages, Boolean bDHTML, Int32 startPage, Int32 endPage)   at CrystalDecisions.CrystalReports.Engine.HTMLExporter.Export()   at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)   at CrystalDecisions.CrystalReports.Engine.ReportDocument.Export(ExportOptions options)   at KIT.Crystal.RunReport()" KIT.Crystal.RunReport is from our component, and contains the following code                    rptDoc = SetupRptDoc();                    // Set the options for saving the exported file to disk                    destOpts = new DiskFileDestinationOptions();                    destOpts.DiskFileName = outputFilename;                    expOpts = new ExportOptions();                    expOpts.DestinationOptions = destOpts;                    // Set the exporting information                    expOpts.ExportDestinationType = ExportDestinationType.DiskFile;                    switch (exportFormat)                    {                        case ExportFormatEnum.CRS:                            expOpts.ExportFormatType = ExportFormatType.CrystalReport;                            break;                        case ExportFormatEnum.DOC:                            expOpts.ExportFormatType = ExportFormatType.WordForWindows;                            break;                        case ExportFormatEnum.HTML:                            htmlOpts = ExportOptions.CreateHTMLFormatOptions();                            htmlOpts.HTMLBaseFolderName = new FileInfo(_outputFilename).DirectoryName;                            htmlOpts.HTMLFileName = new FileInfo(_outputFilename).Name;                            htmlOpts.HTMLEnableSeparatedPages = false;                            htmlOpts.HTMLHasPageNavigator = false;                            expOpts.ExportFormatOptions = htmlOpts;                            expOpts.ExportFormatType = ExportFormatType.HTML40;                            break;                        case ExportFormatEnum.RTF:                            expOpts.ExportFormatType = ExportFormatType.RichText;                            break;                        case ExportFormatEnum.XLS:                            expOpts.ExportFormatType = ExportFormatType.Excel;                            break;                        case ExportFormatEnum.PDF:                        default:                            expOpts.ExportFormatType = ExportFormatType.PortableDocFormat;                            break;                    }                    //Export the report                    rptDoc.Export(expOpts);

Maybe you are looking for