Problem opening my canon EOS500D files

Please help.
I have a Canon EOS 500D camera.
When I try and open the .CR2 file in Photoshop CS4 I get the following message  “Could not complete your request because it is not the right kind of document”.
I have installed all of the possible adobe updates. The .cr2 files do open in the canon software.
It is as if the properties of the files are not correct but as I have said the file opens fine with the canon software.
Please help.

Your camera is newer than the latest version of Adobe Camera Raw which Photoshop uses to open raw files.
See http://forums.adobe.com/thread/424916?tstart=0 in the ACR forum.

Similar Messages

  • Error: "We're having a problem opening this location on file explorer. Add this website to your trusted sites list and try again"

    Hello,
    When i try to open document library from SharePoint Production portal then it throws the specified error. However, when i open document library from SharePoint Development portal then it opens it in file explorer quite easily.
    Production portal is on https whereas development portal is on http. Also, UAG has been configured on production portal.
    Any idea where it's getting stuck up? Surely, this is not a browser issue on Windows 7 as it's opening the development portal's document library on the same machine.
    I've also done following things:
    - Configured Desktop Experience on production environment
    - Installed the hotfix for Windows 7
    Regards,
    Sohaib
    Sohaib Khan

    Hello Sohaib.
    Here is the list of causes defined here.Hope it helps you
    The cause and the resolution methods are the following:
    Cause: There is a missing Root site collection...
    Resolution: Check and ensure,  that the “Managed Paths” are not changed in the web Application’s page, there is a (root) explicit for
    this web application and there is a working Root site collection.
    If for any reason this is not the case in your environment, you may try the following:
    - Apply (if not already) the following Hotfix to one of those clients:
    Error when you open a SharePoint Document Library in Windows Explorer or map a network drive to the library after you install Internet Explorer 10 in Windows 7 or Windows Server 2008 R2 
    http://support.microsoft.com/kb/2846960
    Then, try to delete the cache of the IE browser before reproducing the issue. Check the result..
    - Try to temporarily disable the Antivirus and test again.
    - Check if you have installed the Desktop Experience feature on the SPS13 server.
    - Check if you face this behavior with all users, Or only with some specific ones, Or with all different client OSes.. 
    Otherwise you will need to collect the logs to further analyze...
    http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/sps13-quot-open-with-explorer-quot-random-error-quot-we-re-having-a-problem-opening-this-location-in-file-explorer-add-this-web-site-to-your-trusted-sites-list-and-try-again-quot.aspx
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Sharepoint 2013 explorer view error - problem opening this location in file explorer (HTTPS + Win7 Enterprise 64 bit + IE9 32 bit + Office 2007 32 bit)

    Hi,
    We have a problem using Sharepoint 2013 explorer view. (Error - We're having a problem opening this location in file explorer. Add this web site to your trusted sites list and try again).
    I'm using Windows 7 Enterprise 64 bit, Office 2007 32 bit and IE9 32 bit. And the sharepoint site is a https site.
    Some people in my organization are able to browse and some users getting the above error. (with the same client machine configuration)
    If I clear my browser cache, closes the browser and open it then the explorer view is working. But after a minute if I try again I'm getting the above mentioned error. This 1 minute expiration happens is since the first time I have used explorer
    view, not since I opened the browser.
    I have tried the following on my machine:
    1. Modified the web client service to run automatically.
    2. Verified the sharepoint site is part of trusted sites (https://*.spsite.com/)
    3. Compatibility mode is turned on.
    4. Tried adding
    AuthForwardServerList in the webclient registry settings under parameters. (restarted the web client)
    5. Verified the BasicAuthLevel set to 1 (since we are using SSL). Tried setting the BasicAuthLevel to 2 as well. (restarted the web client)
    6. Tried installing software update for web folders (KB907306).
    Verified the below on the production server:
    1. The web application has the root site collection.
    2. It has WebDav Publishing disabled under IIS Web Server feature.
    Could some one please help me in resolving this issue?
    Thanks.

    Hi  Deepak,
    According to your post, my understanding is that you failed to use "Open with Explorer"  in a document library.
    For your issue, please verify the following:
    ActiveX controls must be enabled in IE.
    As you are using Windows 7 Server as the client computer, you must install the Desktop Experience feature from Server Manager.
    Make sure there is a working Root site collection.
    Install this hotfix for windows 7 work with sharepoint 2013 :hotfixv4.microsoft.com/.../463266_intl_x64_zip.exe
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • When i open my Canon RAW-files with preview or transfer them to another program using preview they change to color despite the fact that they where all shot in B/W... How to change this?

    When i open my Canon RAW-files with preview or transfer them to another program using preview they change to color despite the fact that they where all shot in B/W... How to change this?

    I shoot only RAW - no JPEG-files except those visualizing the files on my memorycard or computer. I think i have to refine my question;
    1. I know there is possible to make B/W HDR-images.
    2. I know the best HDR images are based on RAW-files.
    3. When i transfer the images in question to a HDR software they change, so when i view them in the software (either Preview or the HDR software) they are suddenly viewed (and processed) in color.
    4. This never happend on my PC so i know it has to do  with either Finder or Preview.
    5. Do i have to make all my B/W HDR-images on the PC or is it a way for me to change how Finder/Preview show/alter my images?

  • Problem opening 32bit HDR tif file

    Hi
    This is driving me mad. I've searched the forum and there are several similar posts, none of which solve this problem, so I'm posting a new thread.
    Essential stuff:
    CS5 v12.0.3 x32
    Windows Vista 2G RAM
    Memory usage in CS5 performance preferences set to 59% (I've tried everything from 10% to 90%)
    Windows Virtual Memory set to 4G
    Scratch disk has 20G free
    I've already tried deleting the preferences file
    The file it can't open is a 32bit HDR tif, 135Mb (hardly huge). I immediately get the error "Could not complete your request because there is not enough memory (RAM)" - yes, I've goggled this but the suggested solutions don't help. It routinely opens 32bit HDR tif files of about 35Mb, so I'm guessing the problem is something to do with the file size.
    If anyone can help I'd be eternally grateful
    Thanks
    Doug

    2 GB isn't really a lot of RAM to have in your system by today's standards, though one would think it would be enough that you should be able to open a single 135 MB file...
    What's the pixel count in that file?
    How was the file created?
    I just started a fresh copy of Photoshop CS5 32 bit and it seems to be taking about 200 MB in RAM, before opening any image.
    Just guessing at the image size, I created and saved a 141,193,460 byte 32 bit TIFF file.  Opening that file, peak memory usage by Photoshop (program and data) was a hair under 500 MB.
    Given that your OS should be using no more than about 500 MB to 1 GB of RAM, this should still leave space available for you to open this one file.
    Have you tried creating and saving another file of equal size, and opening that?  Doing so could help determine whether perhaps the file you're trying to open is somehow corrupted, or whether it's a basic RAM problem.
    -Noel

  • Problems opening up 2011 raw files in current Photoshop.

    I'm having problems opening up some of my older RAW files in Photoshop CS6 and CC. It extends to both dng and cr2 files. They display as a monotone image, with no original color present. I can copy the files to another computer with CS5 and open them up there and they're fine, and I can resave them and they're OK. But this could be a looming problem. What's going on?

    Ha! It's a camera profile thing, I have a profile for my IR converted 5D, and for some reason some of my files had that profile applied. If I opened it in a computer without that profile on it, it opened up fine. Thanks.

  • How do I open .CR2 Canon Raw Files in PS Elements 8 for iMac

    When I open a .CR2 Canon Raw File (Canon T3i camera) in PSE 8 for iMac, I get all greys - no color.  It is showing as color as a .CR2 on my desktop - when I bring it into PSE, it is grey.  I chose first 16 bit, then 8 bit.  Same result.  What am I doing wrong?  Thanks.  George

    Thank you Barbara for pointing this out. Since I'm new to forum stuff so missed the catch here. Got exactly same information as you posted. Got to know that ACR 6.2 doesn't support T3i files. It's ACR 6.4 which supports them but is incompatible with PSE8 ( http://kb2.adobe.com/cps/407/kb407111.html ).
    So the solution seems to be either upgrade to a newer version of Elements or download the free DNG Converter ( http://www.adobe.com/products/photoshop/extend.displayTab2.html ) and convert the raw files to DNG.
    Thanks again for correcting me here
    Regards
    andaleeb

  • Any problems opening Illust. 10 files with illus. CS3?

    I'm working on a logo in Illustrator 10 at home...my old g4 tower is running 10.3.9...
    I'll be using these files on a new laptop, a MBP with leopard...I'll be upgrading to CS3 for Illustrator...
    there won't be any major text files, just logo work...mostly type, an acronym...perhaps some mark design like circles, ovals, squares, etc...
    anything i need to know about now that won't work when I upgrade and transfer these files to a new computer?...I just want to make sure I don't keep my client waiting while i have a nervous breakdown trying to open and use my files :-)
    thanks for any advice...
    M

    Keep the G4 for backup in case things get out of hand. I'm like you are, still using v10 via OS10.3.9 and have concerns. Wade is correct about text, I believe Adobe rewrote the font engine in CS1 and there was some confusion on how to handle the transition. The problem with a triple upgrade like ours is: 1.) you're upgrading the CPU which affects peripherals and existing system applications like font management, 2.) you're upgrading from Panther to Leopard while totally bypassing Tiger, so there may be issues with missing updates ( although unlikely ) and some vendors not yet ready for Leopard, and 3.) Adobe is trying to keep pace with Leopard w/CS3, so there are probably issues that have not yet been discovered and some that have ( per Wade ). I've done some recent work with CS2 apps via Tiger ( OS10.4.1? ) and Apple's Mac Mini Intel based CPU and didn't perceive any real problems. But, again, those were just generic, education baed machines that didn't have print capabilities, font management, or outside peripherals ( probably the best way to run the system ).

  • Problems opening a certain CR2 files

    Hi,Can anyone help with this one, in May last year I shot some images on a Canon 450D in RAW, when I imported them into Aperture, they showed the unsupported message, Apple then updated aperture and now they only open as a thumb nail, I thought I might have mistakenly shot these in sRAW so tried opening in the Canon software but still no joy. In the metadata it shows a pixel size of 170 x 256 but a file size of 15.55mb which really doesn't make sense.
    Please help if you can.
    Regards
    Steve

    There are 2 issues here that combine to cause them not to open: the way the files were written, and how much memory Photoshop will allocate for decompressing a single image tile.
    Image Width: 14101 Image Length: 18206
      Resolution: 400, 400
      Bits/Sample: 8
      Compression Scheme: PackBits encoding
      Samples/Pixel: 3
      Rows/Strip: 18206
      Number of Strips: 1
    The images are written as one huge image tile/strip that decompresses to something around a Gig per tile.
    Decompressing that quickly is going to require allocating a buffer over a Gigabyte to hold the data.  Photoshop sets some limits on how large a tile buffer it will allocate so that you don't wait hours for the OS and Photoshop to free up the required space. Yes, we really had user documents that were spinning for an hour or more trying to allocate the buffer space to decompress them, even on a 64 bit system with quite a bit of RAM - hence the limits.  Your documents, written as a single huge tile, exceed the limits that Photoshop will allocate for a single tile.
    The TIFF spec recommends that documents be saved in smaller tiles (though one line per tile is excessive).  Even moving to a few hundred Meg per tile would allow Photoshop to decompress the image data successfully.  Either you should choose different TIFF output options when scanning, or communicate to the makers of the scanner that they should read the TIFF specification and talk to Adobe about improving their TIFF implementation (which would send them back to me).
    Also, the images are also written using PackBits (a run length encoding scheme) that is not a great compressor.  Using LZW or Flate would have decreased the size of the files considerably (half the size, or better).
    For the time being, you can use some of the libTiff command line tools to unpack and repack these files to work better with Photoshop and other applications.

  • Problem opening xcelcius 4.5 file

    Hello,
    I wrote an xcelcius file in version 4.5 and then I tried opening it in a different computer which also had 4.5 and I got the following error: 
    "Invalid Version found PK.  Crystal Expects version 1.1.0.2"
    How do I make it work?
    Thanks,
    Isaac

    I've only seen this happen on 2 occasions:
    1.) Opening an Xcelsius file in Xcelsius 2008, saving it in 2008, and then attempting to open it in 4.5
    2.) Accidentally opening a non-Xcelsius file in the application.
    This is a just a guess, but was the file opened and saved in Xcelsius 2008?  If so, attempting to open it in 4.5 again will show the error.

  • I had lightroom 4 and Photoshop CS4 I downloaded cc and trialled it and then uninstalled since then I cannot read/open my Canon cr2 files and

    I trialled cc Photoshop.
    I had Photoshop CS4
    and lightroom 4.4.
    I used LR4 and cc as well as CS4 during that time
    BUT
    when I uninstalled cc
    after initial work in LR4
    I try to open it in PS4
    it no longer recognise my Cr2 (Canon Mark 111 tif files)
    (which it had no problem with previously.
    When I try to go from LR$ to PSCS4
    it now tell me
    this version of Lightroom may require the Photoshop Camera Raw plug-in version 7.4 for full compatibility.
    Please update the Camera Raw plug in using the update tool in the Photoshop help menu.
    Ihave downloaded this off the net but it does not seem to solve the issue
    HELP!!!

    G'day Curt,
    I smacked myself on the forehead when I read your reply. How could I have forgotten to do that? However, after trying that, the problem persists and more files are corrupting. I now have around ten files of around 200 in a party folder I have that have corrupted. They all were perfect several days ago.
    I'm starting to get worried as I work for the local rag and have social pics this weekend to process. I can't afford to let this happen to them.
    Thanks for the suggestion....
    Onslow

  • Problems with some Canon Raw files

    I'm having a very frustrating problem and would be interested in seeing if anyone else has seen this.
    I have images shot in raw with a Canon 1D Mk II. Some of the files cannot be rendered in Aperture - they show a gray thumbnail and the red "unsupported file format" display in Viewer. If I open the Library package and navigate to these files, I can view them fine in every other browser/converter - ACR, Capture One, DPP, iView Media Pro, Bridge.
    Preview is also unable to view the image as I'd expect with the same error as Aperture.
    I do know about the Photo Mechanic problem, but I don't use that app. It's not a firmware issue since I have images taken on the same day - some display some don't. I've tried importing multiple ways, making sure there is no metadata assigned, everything I can think of but no luck.
    Even though most of my hair is already gray, I'd like to keep it if possible, but this has me ready to pull it out.
    Any ideas?
    Thanks much,
    Jon Canfield

    I shoot with a 1Ds and 5D and previously with a 1d and 20 . I have also seen this problem with 1D files and 1Ds files and I think it has to do with if the file had been opened in another raw converter and left with the raw adjustments in embeded. I say this because the files it gives me in grey are ones that I opened but didn't edit. I will try opening and saving in another software and then to bring back into Apeture, though the more I have to use PS CS, Bridge, DPP, or other package the less I think Aperture is going to provide a complete solution for me.

  • Problem opening Samsung NX1100 SRW files in CS6 and Lightroom 4

    I bought a Samsung NX1100 and want to shoot in Raw format. My CS6 Bridge and Photoshop will not open the SRW files though. I downloaded the lightroom 4 that came with the camera and that will not read the SRW files either. How do I access my SRW files?

    I'm having much the same problem, except I'm shooting with an EX2F. I've tried reinstalling CS6 (I have extended) and updating to the latest patches, but no go. Photoshop and Bridge can see the files, but cannot open them or draw thumbnails for them. I have also tried installing the latest version of Adobe DNG converter, I get the same result with this.
    I'm on a Macbook Pro, lastest OS with latest updates.
    I saw on another thread somewhere that changing the file extension from .SRW to .CRW is the fix. I tried this with a couple of files but again I am still unable to open the files.
    Apparently there's a raw converter for Samsung cameras but I haven't been able to find it. which is available on the Samsung website NX200 - DOWNLOADS | SUPPORT | SAMSUNG I don't know if it converts to JPG or another RAW format yet. Hopefully the link doesn't get wiped and it's useful to someone else.
    EDIT: Looks like it's a standalone RAW developer. It only outputs jpg or TIFF.

  • Problem opening a scanned .tif file in CS4

    Hi...Just got CS4 and am trying to use CS4 to open a picture that I scanned into the computer. I get this message "Could not complete your request because of a problem parsing the tiff file". The file is only 12,084 KB and 1702 x 2338. It will open in CS2 but not CS4. CS4 will however, open the scanned files that are smaller than 10,000 KB.
    Any help is greatly appreciated.

    Hi, is there a solution yet for this problem? I just upgraded to CS4 (from CS3) and now I have the same problem (Scanned tiff files, CS3 opens them perfect, CS4 gives error problem parsing the Tiff file.
    thanks!

  • Having problems opening an SSIS solution file

    I have to make some changes to an SSIS package that was last modified in 2009 by a person who has left the company.
    I am having problems finding a version of Visual Studio that will open the SLN file. I do not know how the package was originally maintained.
    Yesterday, I was able to right-click on the SLN file and select 'version selector', that opened the solution in VS 2005 without me having to select a program. I made some changes and saved, rebuilt and ran the package.
    Today when I try to open the SLN the same way, it displays the screen with the various VS version icons on it, but no VS 2005 listed!
    The bottom line, is I now cannot open the solution with any version of Visual Studio. If I can find another SLN file that will open, can I copy the modified dtsx file to that solution so all my work is not wasted? It took me 3 days work to modify this package.
    Can someone please help, my deadline for this task is TODAY.
    Here is the message I get if opening with VS 2005:
    Here is the message I get if opening with VS 2010:
    Here is the SLN file (It looks like it got modified because I'm pretty sure yesterday it said VS 2005 at the top):
    Microsoft Visual Studio Solution File, Format Version 11.00
    # Visual Studio 2010
    Project("{D183A3D8-5FD8-494B-B014-37F57B35E655}") = "HPAddress_ExportData", "HPAddress_ExportData.dtproj", "{7EB5909F-6836-4B23-A121-9F623FB1C932}"
    EndProject
    Global
     GlobalSection(SolutionConfigurationPlatforms) = preSolution
      Development|Default = Development|Default
     EndGlobalSection
     GlobalSection(ProjectConfigurationPlatforms) = postSolution
      {7EB5909F-6836-4B23-A121-9F623FB1C932}.Development|Default.ActiveCfg = Development
      {7EB5909F-6836-4B23-A121-9F623FB1C932}.Development|Default.Build.0 = Development
     EndGlobalSection
     GlobalSection(SolutionProperties) = preSolution
      HideSolutionNode = FALSE
     EndGlobalSection
    EndGlobal

    Hi AllTheGoodNamesWereTaken,
    Based on my test, if we open a solution file with lower version in a higher version Visual Studio (VS), it will use Visual Studio Conversion Wizard to update the solution to current version of VS. Then the solution file will also change to current version
    of VS. If we open a solution file with higher version in a lower version Visual Studio (VS), it causes an error that “The version number in the package is not valid. The version number cannot be greater than current version number”. And the solution file still
    use the original version of VS.
    So it seems that the original version of solution file is lower than or equal to VS 2010. Since the VS is backwards compatible, we should use a higher version of VS (VS2010 and later) to open the solution file. Notice that we need open the solution file,
    not the project file.
    Besides, we can also create a new SSIS project in a higher version of VS, then add the packages with “Add existing package” option from File System. Reference:
    https://www.blackbaud.com/files/support/guides/infinitydevguide/Subsystems/bbdw-developer-help/content/tkaddpackagefromexisting.htm
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

Maybe you are looking for