Imported Catalogue, Corrupted Images

I imported a catalogue into my main LR catalogue.  20% of the image files were corrupted (vertical or horizontal lines in the images.)  I deleted the bad files and replaced them successfully, but when I switched to the Develop Module, the lines reappeared.  To overcome this, I edited the images in photoshop, and that seemed to work, however, when I exported the pictures from Lightroom, they were once again damaged with vertical and horizontal lines.  Any ideas?

I haven't checked the condition of the RAW files, only how they appear in LR, and how they look when exported as JPGs.  But yes, in Photoshop, the photos look fine. In the LR library they look fine.  As soon as any they move into Develop Module or any manipulation is done in the Library mode, they become corrupted.  One more thing.  Originally, the photos were on an external hard drive and the Catalogue was on my MacBook Pro.  The problem occurred when I imported the Catalogue into my main Catalogue on my office tower G5.

Similar Messages

  • Frustration - Iphoto corrupting image files during import (?)

    To begin with, I'm a recent convert from Windows to the Mac. I'm running a mac mini at home, and a Macbook with Boot Camp at work (in addition to my desktop pc). All of my software is up to date...
    I take alot of pictures with my digital camera (canon powershot). Saturday I took about 300 pictures, took the SD card out of the camera, put it into my Sandisk card reader, imported the pictures into iphoto and everything worked great. I chose to not delete the pictures after the import as I wanted to bring the card into work and upload the pictures on my pc.
    The next day (Sunday) I took another 70 or so pictures. I was able to view all of the pictures on my camera that I had taken over the past two days.
    I go to do an import , taking the exact same procedures that I took on Saturday (and that I always do). The first thing it does is identifies that there are duplicate pictures. I choose the option of "don't import duplicates" and apply this to all of the other duplicate pictures.
    At the end of the import, I got an error message saying that some of the files were corrupt. Now, there were pictures from Saturday that were still on there (and readable/viewable). However, every picture that I took on Sunday was "unreadable" and did not show up in iphoto. I put the card back into the camera, and now I can't view the pictures (they show as "corrupted data".
    I then pulled the SD card details up in Finder, and the "corrupt" files still show sizes of 2.4mb to 2.8mb, consistant with the good pictures. It shows the file's "Kind" as JPG Image... I double clicked on them and Preview comes up saying something to the extent that the file is corrupt,
    I've taken the Sandisk card reader, plugged it into my Macbook (using iphoto in osx) and was able to view one or two of the pictures from Sunday.
    Once I got to work this morning, I plugged the sd card into my Windows machine and it too says the files are corrupt. It shows them being on the card, it shows the file sizes, but I can't open the pictures in anything...
    If this was a one time deal, I'd be thinking it may be something I've done to cause the problem. However, this is the third instance I've "lost" all of my photos because of them becoming corrupt during an import into iphoto. There definately appears to be a pattern.
    I have somewhere around 8,000 pictures inside iphoto that I've taken and had no problems with. I mention this to illustrate that I'm not doing anything differently than I've done before. I have another 14,000 on my old Dell that I need to move over, but I'm questioning if I should do that now.
    Does anyone have any ideas on what the problem might be? Is anyone else experiencing (present or past tense) this problem? Where I'm new to the mac, I understand that I might be doing something wrong. However, I've imported photos to the software (what seems like) hundreds of times, the same way each time. This makes me want to rule out user error...
    One other question, I'm saving the "corrupt files" with the hope that there's a software program which will "fix" the files. Do you happen to know of such a piece of software? I'm hoping that I can get them fixed at some point.
    Where I'm taking pictures of my kids, its extremely frustrating to find out that the pictures (memories) I was hoping to make prints of are now "gone". Its almost like rolling the dice when doing a photo import any more. Most all of the time it takes, but every now and then the pics are lost...
    I'm hoping to identify the problem (either user error, procedure or software issue) and fix it as I really like the mac.
    Any help/suggestions you might have for me would greatly be appreciated!
    Mac Mini   Mac OS X (10.4.10)   Also running Macbook 10.4.10

    The Chainsaw
    Welcome to the Apple Discussions.
    First: the corrupt files: download Graphic Coverter, a shareware which is often successful where other software isn't. But first, if the Mac will let you, copy the files off the card to the Mac.
    I'm in this board a while now, and I can't recall an issue of iPhoto corrupting images on import. After all, it's just a simple file copy, at heart. I would be more inclined to suspect the card. DO you have more than one? Does the problem also occur with the other cards?
    Try use Image Capture to download the pics to the Mac first, then import them, see does that help. Image Capture is in your Applications folder.
    Regards
    TD

  • Lightroom 4.4 crashed on Windows 7 Laptop, lost catalog info, won't import half my images.

    Lightroom 4.4 crashed on Windows 7 Laptop today, lost catalog info, won't import half my images.
    Not only is LR messed up, it deleted my day's shooting. Can't believe that.
    Now it won't import (i.e. re-import) half my files.
    Imported half, but had errors importing rest.
    Corrupt catalog?
    When I try to import the folders, it recognizes that they are in the catalog (I have "don't import duplicates" turned on).
    After running through all the folders, it says, "Nothing to Import."
    Any help?
    Best,
    Peter

    Thanks dj_paige.
    I installed a plugin, coincidence makes me thinks this might have cause a LR4.4 crash.
    After rebooting my windows 7 laptop, LR had lost record of half my directories on the external drive, as seen in Library Module.
    In Windows Explorer, the folders and images are still there.
    I tried recovering the lost folder references in LR by doing an import on the external hard drive again.
    It took about a half hour to run.
    There was a report screen at the end of the process that said that LR was unable to import something like 1500 images.
    I did not save the report screen. Maybe it is part of a log file somewhere to give you what it exactly said?
    I do not profess to understand how catalogues work under the covers.
    I only use one catalog at this point.
    My guess is at this point I should de-commission the catalog (whatever it takes to do that - delete it, etc.) and just do a new, fresh import on my images.
    I don't feel I lose anthing this way - I can't see where I would lose anything important. About 5-10% of the RAW images were processed and exported to jpg, just for web use for casual viewing. The jpg's are all still on the external hard drive.
    Any suggestions are appreciated.
    Cheers,
    Peter

  • Any new fixes for corrupt images in Lightroom 4.4?

    I have seen many threads on this and tried a lot of the tings people say to try. But I do get corrupt images in Lightroom. I currently have an AMD FX-8150, 32GB ram, 2 SSD Raid0 + USB3.0 drives as backup.
    Drive and Memory:
    Note, I only keep up to the last 3 shoots on my SSD, the rest are stored on my USB3 drives. Any time I import files to the USB drive I get no corruption. Now that would imply that I have bad drives, I have run diskcheck and contacted Muskin and they had me run some disk checks, speed tests, +other things and identified that the drives are running fine with no issues and this has to be a software issue.
    I have run memtest86+ with no errors, also ran memtest86+ with my memory in another machine with no errors.
    To rule out the card reader:
    When I just copy files from my CF Card to a folder using explorer all images import fine and you can even open every image in photoshop with no issues. As soon as you add those files already copied to the HD to lightroom, they start to corrupt. I just recently used the windows explorer method and added ~400 images to lightroom, all images imported fine, when I later accessed lightroom(Today), about 10% of those images are not corrupt.
    Does anyone have any suggestions? Could it be because I use Raid0? Or even SSD drives?
    This is quite annoying and I would like to get things fixed.

    jproductions111 wrote:
    Usually when Lr renames the photos as you saw kianjillwedding-19, Lr changed the name from IMG_1968. Thats may have something to do with the corruption.
    I don't see how. Renaming shouldn't change anything on disk except, well, the name - and of course update a bunch of things in the catalog.
    jproductions111 wrote:
    I will get back to you if the problem continues but everything still seems to be fine in Lr5, even after letting Lr rename all the photos with my current(today's) import of 700 images.
    OK - thanks.
    jproductions111 wrote:
    I know you don't believe its software
    ~impossible it's Lr4 software. Theoretically possible, but highly unlikely. As I said, Lr4 should never be rewriting those files, and therefore essentially can not corrupt them. I mean, its possible that it got it's brains scrambled, and went ahead and rewrote them, for god-knows why or just for the he|| of it - because some bits seemed to be set wrong..., thus invalidating the assumption that it's not rewriting them. It's just that this scenario is the least likely. I mean, Jeff Schewe has given me spankings more than once before, for even bringing it up, since it's so unlikely...
    jproductions111 wrote:
    maybe Lr 4 was causing some sort of bug to make the hardware malfunction
    Although theoretically possible, I'd still venture to guess that's not what happened.
    jproductions111 wrote:
    this is not happening to my in Lr5.
    Didn't you also change your disk drive situation around just before you started using Lr5?
    jproductions111 wrote:
    But I am keeping my fingers crossed.
    Me too - please keep us posted...
    R

  • Hdiutil: verify failed - corrupt image

    problem: sparseimage is not mountable and verify ends with a "hdiutil: verify failed - corrupt image".
    cause: tiger crashed and the image was mounted. the only way to boot was power down the machine. after the reboot the image was not mountable anymore.
    thats the verbose output:
    hdiutil verify -verbose conti.sparseimage
    hdiutil: verify: processing "conti.sparseimage"
    DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
    DIBackingStoreInstantiatorProbe: interface 1, score -1000, CRAMBackingStore
    DIBackingStoreInstantiatorProbe: interface 2, score 100, CCarbonBackingStore
    DIBackingStoreInstantiatorProbe: interface 3, score -1000, CDevBackingStore
    DIBackingStoreInstantiatorProbe: interface 4, score -1000, CCURLBackingStore
    DIBackingStoreInstantiatorProbe: interface 5, score -1000, CVectoredBackingStore
    DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
    DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
    DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
    DIFileEncodingInstantiatorProbe: nothing to select.
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CUDIFEncoding
    DIFileEncodingInstantiatorProbe: nothing to select.
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
    DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
    DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
    DIFileEncodingInstantiatorProbe: nothing to select.
    DIDiskImageInstantiatorProbe: interface 0, score 0, CDARTDiskImage
    DIDiskImageInstantiatorProbe: interface 1, score 0, CDiskCopy42DiskImage
    DIDiskImageInstantiatorProbe: interface 2, score -1000, CNDIFDiskImage
    DIDiskImageInstantiatorProbe: interface 3, score -1000, CUDIFDiskImage
    DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
    DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
    DIDiskImageInstantiatorProbe: interface 7, score 1000, CSparseDiskImage
    DIDiskImageInstantiatorProbe: interface 8, score -1000, CCFPlugInDiskImage
    DIDiskImageInstantiatorProbe: interface 9, score -100, CWrappedDiskImage
    DIDiskImageInstantiatorProbe: selecting CSparseDiskImage
    DIDiskImageNewWithBackingStore: CSparseDiskImage
    DIDiskImageNewWithBackingStore: instantiator returned 103
    hdiutil: verify: unable to recognize "conti.sparseimage" as a disk image. (corrupt image)
    hdiutil: verify: result: 103
    hdiutil: verify failed - corrupt image
    the problem is not that i dont have a backup of tha date within this 7GIG imagefile. the problem is now that i dont trust this format anymore. i do have a couple of AES-secured sparesimages FOR backup-reason (including one on my iPod) and if something happens to them i might be in serious trouble.
    so now my question: is it possible to rescue this AES-secured spareseimage or is this kind of methos unsafe for important data?
    thanks
    klaus

    Regular tools like Disk Utility and DiskWarrior
    didn't solve anything. I was wondering if it is
    possible to rescue some files by manually decrypting
    the image with some low-level tool.
    Did you have any succes? Given all reports on the
    web, it seems a bit hopeless, but I like to give it a
    chance.
    no success at all, sorry.
    i dumped the images now and also went back to some backups.
    but i definitly don't use filevault anymore
    cu

  • Corrupted image files in Lightroom?

    I opened up Lightroom this morning and noticed that some of my files from a recent shoot look like this:
    Are they corrupted?
    If so, how does that happen? I've never seen this before and I have thousands of images in LR.

    Thanks. I read through a few of the other threads. I found one comment that might be applicable to my situation:
    Good - most often this tell-tale/signature-looking corruption is due to hardware - transfer hardware if corrupt upon first rendering (true raw rendering, not initial preview display), hard disk if corrupt after first rendering. And sometimes ram.
    I think this may have had something to do with how I got these files onto my computer. I shot the pictures while visiting family. I had my Macbook Pro with me, which is not my main image editing machine. I imported the files into LR4 on the MPB from the 5D3 using the USB cable.
    When I returned home, I moved the files from their location on the MBP to a USB flash drive, and then imported them from the flash drive to LR4 on my Mac Pro (which is my main image editing machine).
    The corrupted images are only from this group. So I'm hoping that it was the transfer to and from the flash drive that caused this, especially since I've never experienced it before and don't see it in any of my other images.
    Fingers crossed!

  • Aperture corrupting images during editing

    Hello,
    Starting a few days ago, aperture started corrupting images during editing.  This was normally at the time of my fist cut, going through doing simple straighten and croping.  Sometimes it would happen when doing a small lighten or darken of the exposure.  I purchased a new MacBook Pro about a month ago but this only started happening this week.  No OS or Aperture upgrades this week.  I did have a crash earlier this week and after the crash my Spotlight re-indexed my computer.  I updated QuickSilver this week and Awaken.  I tried quiting both QS and Awaken but problem still happens.  The real scary thing is I usally have to go back and re-import the raw CR2 image to fix the problem, doing an update from master or resetting all adjustments does not fix the problem.  Below is an example of an image with the problem.  This is a Version Export of a corrupted image, as you can see the cor  Can I get any help?

    Ernie Stamper:
    The Aperture Libraries are on the local drive.  I do have an external Firewire drive I can use to test your theory but since I recently replaced the whole laptop at the Apple store so I am thinking it is not hardware related but one of three things: an Aperture bug, my configuration, or memory (see more on memory below).
    leonieDF:
    I don't think it is related to a hardware issue unless it is memory. I took the laptop into the mac store because I was having a hardware issue not discussed in this thread.  The laptop was completely replaced except for the memory since I purchased 8GB of memory after the computer was purchased.  I put the 8GB memory back into the new laptop.  If this is a memory problem it is not showing up in diagnostics.  I am planning on doing two things this weekend.  First thing is putting back in the original apply memory and testing.  If I still get the issue I am going to do a complete uninstall of Aperture and re-install maybe something in my settings/libaries are corrupted.  I am reaching for straws at this point.  I might also try a complete reformat and only install Aperture and test to see if something else installed might be causing this, but I can't think of what it would be.

  • Corrupted image(s)

    Hello,
    Hello, Since upgrading to 1.4.1 I have noticed that on rare occasion a corrupted image. So to test, I recently manually down loaded a photo shoot to my hard drive and inspected the images (Canon 5D cr2 RAW) with Canon DPP (in the mode equivalent to LR develop). All the images were fine. They were then imported in LR. All the images were viewed in the library module and all looked fine. Then the images were examined in the develop module which when I noticed a corrupted image. The corruption takes the form of where a portion of the image contains rectangle with one color channel missing. That is about the best I can describe it.
    As further testing, I examined the corrupted image with DPP again. DPP now reports the image is corrupted which it did not before. I believe this is NOT file system corruption as is appears that windows is not reporting a file system problem to the applications.

    I thought they would have fixed this. This is an ongoing issue from the early days of LR2 (maybe before). In my case, I had imported several hundred images without knowing that the D80 had a bad SD card. About 40% of the images were corrupted.. but they looked fine on the back of the camera because the imbedded JPEG (I shoot RAW) was fine. Lightroom on the other hand crashed every single time I tried to load the catalog and it hit one of these images. I ended spending hours going in and manually deleting the offending images. I would load the catalog and note the file name of the image that caused it to crash. I would then go to the folder and delete it and try again. I also make a bit copy of the SD card so if something went really wrong, I could work on a new set of files.
    Also, I dont know if you have a friend with a Mac, but a tool called "Filejuicer" can pull the embedded JPEGs out of the RAW file even when it's corrupted. I was able to recover almost 100% of the bad files this way. I did give up alot of adjustment in post but at least I had something to work with.

  • Lightroom 4.4 Catalogue corruption - Information please

    Hi,
    Having upgraded to LR4 on Wednesday, I suffered a catalogue corruption today. LR4 couldn't recover the catalogue and I had to revert to a backup I made on Wednesday after uploading 1678 new photos into LR4. Fortunately, I have the XMP write box ticked so I just had to correct a few metadata discrepancies (is there any way to do this other than file by file?) and upload a few files I had exported. So I am now up and running again after about 90 mins chasing around.
    Now I am trying to find why it happened! I run LR4.4 on a windows 7 Home PC. The photos were on a local drive (G:). I have a system of cloning my discs to an external hard drive using Folderclone which runs automatically at certain times of the day. I have been using folderclone for ages and on this system for almost exactly a year since I reinstalled Windows 7. Folderclone was running - cloning the G drive - at the time the problem occurred. Both it and LR4 highlighted disc problems. Under LR3 I have run both at the same time but had to cease photo-editing as it was so slow (but obviously safe!).
    I have just returned from a long holiday and have applied 13 updates since 10 April, 5 of them on 12 April. See below.
    It looks to me like the two programs have tried to access the same information and something has become corrupted as a result. Obviously this shouldn't happen and I would expect Windows to prevent it. However it didn't. The obvious questions are about:
    Windows itself and the recent updates
    LR4.4 as there have been instances of catalogue corruption being reported.
    Has anyone else experienced similar problems? I would be grateful for any information in case there is something I can do to prevent it happening (other than set LR4 to back up every 5 mins which I have done). I will be posting this on a Windows forum as well.
    Thanks.

    KeithR16,
    My hunch would be that the problem of a corrupted catalog is due to the fact that you use "Folderclone". My suggestion is that you exclude the drive where the Lr catalog is located and your photos from "Folderclone".
    My guess is that when "Folderclone" runs in the background it interferes with the reading and writing of the catalog by Lr. Lr constantly reads and writes to/from the catalog. When you work in the Develop Module each step you do is instantly written into the catalog and immediately this last step and all previous steps are read back by Lr. If "Folderclone" tries to clone the catalog while Lr is reading or writing it, this might result in faulty or incomplete catalog data written. Something similar could happen with a image file into which Lr is just writing the xmp (although in case of a Raw-file the xmp is a side-car file - but still, the two are connected).
    My hunch that "Folderclone" creates the problem is based on the fact that I noticed several times that people who report problems with their catalog often also say that they run "Time Machine" on their Macs. Further there have been recent reports on problems where "Dropbox" prevents the export of images by Lr ( Dropbox fixed this problem),. The reason was that dropbox syncing "grabbed" the file before it could be written completely by Lr.
    So it seems Lr is very sensitive if other programs interfere while Lr is writing (or reading).
    Please understand that this is a 'hunch" as I don't have any personal experience with "Folderclone".

  • Attempting to upgrade to Firefox 3.6 (using an ancient Mac OS 10.3), but received an error message (corrupt image file) when downloading - any way to correct this with my current OS?

    I'm currently trying to update a few programs on my good old (VERY old) Mac Powerbook, but I ran into an error when downloading Firefox version 3.6...I'm currently running Mac OS X 10.3.9, which isn't compatible with the most recent versions of Firefox (or anything, for that matter), but it should still allow an upgrade of version 3.6; however, once the file finished downloading, an error message popped up indicating there's a corrupt image file. Is there any way to work around/correct this problem, or am I stuck with my old version of Firefox until I bite the bullet and upgrade my OS??? Any help is greatly appreciated!!

    Firefox 3.6 requires at least OS X 10.4, the last version of Firefox that runs on OS X 10.3.9 is Firefox 2.0.0.20 available from https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/

  • How do I import a jpeg image into my mail signature so that it wont separate when it gets to the receiving email

    How do I import a jpg image into my mail signature box so that it wont separate into an attachment when it gets to the receiving mail box.  We have a company logo and when I send it to someone it does not show up under our address but rather as an attachment.  How do I keep this from happening?

    Hello
    be sure to send your email into HTML format end be sure your corespondant read mail as HTML format
    as you can not be sure of your coresspondant email setting , you can not be sure as your mail is read
    Pierre

  • SCRIPT TO IMPORT MULTIPLE PLACED IMAGES..AND OUTPUT MULTIPLE IMAGES TO SINGLE PDF.

    Anyone got a script to import multiple placed images into CS4? or is this possible in CS5?
    and can we output multiple layers into a single PDF in illustrator?  Or multiple layers into single JPEGS from illustrator with one command instead of individually saving out each page... would be a huge time saver for me.
    Currently I output each completed layer individually and then right click those outputted jpegs in their output folder and choose "combine supported files into acrobat..." to make a single acrobat file..
    I`d also like to be able to CTRL click multiple layers and go save as... only those layers get saved out...
    And so adding something in the Save for PDF output dialogue box to save layers to multiple pages would be a helpful time saver..

    In CS 4 and CS 5 you can drag and drop fro m the finder or the Bridge, and I guess any other similar type viewer, multiple number of image files to a document. You can configure the bridge in such a way as to allow you to see the Bridge and your document at the same time for this very purpose.
    If you just drag and drop the files are linked if you drag while holding the shift key then the files will be embedded.
    ID and PS CS 5 have a minibridge which works the sam way but is an actually panel and will stay in the front.
    I separate the images but they import one on top of another.

  • Checking for corrupt image or element

    Hi
    Hoping someone may be able to help, I have a 256 page book which I created in InDesign CS3, the book is made up of several documents.
    I need to export to a PDF, each time I try it fails as there is a corrupt image. Is there anyway I check the documents for corrupt elements before I create the PDF?
    Any help appreciated.

    You need to "Divide and Conquer." It's not unusual to have a failure exporting to PDF with low disk space, but that might not be your problem. In either case the first step is the same. Divide the document in half during the export process and see if each half will export separately.
    If you can export both halves, you may need to live with that and simply recombine them in Acrobat. I don't recall any definitive answers for what to do fix this. Deleting temporary files may help.
    If you still get a failure, divide that section in half and try again (see below). If both sections fail, it could be either a bad font or more than one bad image.
    Make a copy of the document and change all the fonts to something simple and reliable, like Times New Roman, and see if that works. If it does, make a new copy of the original and eliminate fonts one by one, starting with cheap or freebie fonts from the web, and test after each replacement.
    If only one section failed it's more likely an image, and you should be able to isolate the page by continuing to divide the section that fails. Once you know which page, make a copy, and remove images one by one, starting with .eps if there are any.
    If you find a bad image, try resaving it and replacing with a native .ai or .psd.
    Peter

  • Problem in importing an own image

    I am new to Mapbuilder. I need to use my own images as themes in my project. when I try to import a bmp or "gif" file by choosing Tools--> Import Image Option using MapBuilder, i am getting the error message "GeoRaster spatial extent update was not successful" in Dialogbox. In the Console the following
    error message is getting displayed.
    Wizard Selection Change - Page:1
    You chose to open this file: D:\12.bmp
    Wizard Selection Change - Page:2
    Wizard Selection Change - Page:3
    Wizard Finish called
    ImportImageThread running thread: Thread-6
    Importing File...
    Georeferencing...
    Updating Spatial Extent...
    Exception: ORA-13430: There is the attribute of NULL in GeoRaster object
    ORA-06512: "MDSYS.MD" and line 1723
    ORA-06512: "MDSYS.MDERR" and line 8
    ORA-06512: "MDSYS.SDO_GEOR" and line 893
    ORA-06512: Line 4
    It is very urgent. Please help me....
    - prabhakaran

    Thanks for the reply. The parameters of the bmp file are
    407 wide * 411 high
    Size: 491 KB
    Top Left Coordinate
    X: -180.0
    y: 90.0
    Resolution
    X: 0.033
    Y: 0.033
    I have also tried to import .tif image. For that i have got the error "Import of File was not successful"
    The parameters used for the .tif image are
    10800*5400
    166 MB
    Top Left Coordinate
    X: -180.0
    y: 90.0
    Resolution
    X: 0.03333333333333
    Y: 0.03333333333333
    In what basis resolution should be mentioned? how to calculate it?
    For "Import of File was not successful" Error, We have followed the Information given in the following URL.
    Import image in Map Builder
    But the same error is coming, while importing the .tif image. Please help me....

  • Corrupted Images in Pages, now unable to open file

    Pages 2.0.1 has lost the ability to open any pages documents with images on my computer. Some image files are corrupted, but other documents with no corrupted images still will not open and crash Pages if I try. Also, the Dock changed unexpectedly after the first crash, removing my Final Cut Pro icon and restoring the iLife icons. Any suggestions?

    Hello Sahu,
    I too had a very similiar experience with one of my clients. There is nothing to do with missing authorizations.
    Ask him/her to set the resolution of their display to 1024 by 768 pixels. This is because some high display resolutions are not supported by SAP Front end. Believe me, I was amazed to discover that something like this exits.
    Have a nice weekend...............
    Shashi kanth

Maybe you are looking for