Skip navigation
Currently Being Moderated

Error opening files that contain 'CR'...

Jun 28, 2011 11:40 AM

Okay, so this is the weirdest thing.

 

I can't open any files that have 'CR' in either the file name, or the file path. It is only with 'CR' (yes, capital only). It does not matter whether it's at the beggining, middle, or end of the file name or file path. The file can be on the desktop, or be inside a folder that contains CR on it, it does not matter.

 

The error I receive when I try to open these files is "Before proceeding you must first launch Adobe Acrobat and accept the End User License Agreement." and I only get an 'OK' option. If I open Adobe Reader I never get prompted to accept the EULA. I checked my registry, the EULA is on (accepted). Please help, this is ridiculous!

 

Many of the files I download for work have the letters 'CR' on it... It's a pain to have to rename each and every one of them. Please HELP!!!!!!!!

 

By the way, I am running Adobe Reader X 10.1 and this happens to EVERYONE in my office... Does it happen to any of you?! Just try to rename a file to CR and see what happens. Thank you in advance for your help!

 
Replies
  • Currently Being Moderated
    Jun 28, 2011 1:44 PM   in reply to GiaKzter

    Same thing here.  Has anyone found a fix besides renaming the file?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 28, 2011 2:20 PM   in reply to GiaKzter

    crpdf.png

    So you can see it, THERE'S the file I named CR.pdf. It was Chase Calendar 6-2011.pdf.

    I right click and select Open with>Reader X and it opens just the same as it has since last week when I made it.

     

    crpdf2.png

     

    I'd think since this is happening all over your office, there is something specific on all those systems that is causing this.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 28, 2011 11:12 PM   in reply to GiaKzter

    Hi,

     

    I can confirm that we have users affected by this on the following system:

    Server 2003 x64 running XenApp 5.

    Adobe Acrobat 10.1.

     

    -Blake

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 6:02 AM   in reply to GiaKzter

    I can confirm this bug as well (Windows 7 - 32bit). I have just reported it directly to Adobe via their bug report form.

     

    This bug has turned up directly after the latest 10.1.0 version was rolled out. I can confirm that any other combination of CR (cr, cR and Cr) work well. Furthermore: if Adobe Reader is already running, then double-clicking on the file in Windows Explorer does function. You can also open a file with CR in the file name with the file open command from within Adobe Reader x.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 10:27 AM   in reply to GiaKzter

    sysinfo.PNG

     

    With Windows 7 Ultimate 32 bit (SP1), Reader X and a file named CR.pdf, I'm just not getting this error.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 11:17 AM   in reply to 370H55V

    @Expat

     

    And just to be absolutely certain.. you have the very latest Reader 10.1.0 update installed?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 11:21 AM   in reply to 370H55V

    I can also  open a file named CR.pdf.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 11:56 AM   in reply to Bernd Alheit

    I can confirm that this error does not occur at home with Win 7 64-bit and Vista 64-bit (German language setup).Furthermore it seems to have nothing to do if Acrobat Exchange is installed or not.

     

    --> Those who can confirm this error: are you in a corporate (domain) environment?

    --> Those who can not reproduce the error: are you in a workgroup environment?

     

    Thanks everybody

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 2:09 PM   in reply to DGF_CH

    readerx.PNG

     

    It's as up to date as up to date can get.

     

    And I am NOT in a corporate environment. Standalone home computer.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2011 8:14 PM   in reply to GiaKzter

    Our environment is Citrix Xendesktop 5 with Windows 7 32 bit enterprise installed and we can't open files with CR.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2011 4:57 AM   in reply to CMM1980

    Hello

     

    --> regedit
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown]
    change "bProtectedMode"=dword:00000000

    to
    "bProtectedMode"=dword:00000001

     

    thats fix the problem

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2011 6:25 AM   in reply to xiipa

    I can confirm this. It just does not solve my problem. The issue is, that due to a business apllication we are forced to start Adobe Reader in unprotected mode. This applicatzion displays PDF files via IE/html links, and when you start with Protected Mode enabled, the PDF is not displayed.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2011 6:41 AM   in reply to DGF_CH

    you can remove all the lockdown dwords
    bcommercialPDF

    bProtectedMode

    bPurchaseAcro

    ....

    ....

     

    it works allso

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2011 7:00 AM   in reply to xiipa

    So if Adobe Support is reading here - the unability to open files with a capital CR in the filename is caused by the bProtectedMode parameter provided in order to disable Protected Mode .

     

    Please make that possible again. Thank you.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 11, 2011 10:41 AM   in reply to GiaKzter

    I ran into the same problem. I wrote a post on my blog about how I fixed it. Hopefully it will help in your case as well.

     

    I will say I went back & tested the whole CR in the name thing. I can confirm that on Windows Server 2008 SP2 32bit & Adobe Reader X 10.1.0 if the filename has CR in it anywhere it will trigger the EULA error. The fix I mention in my blog post does however get around having to rename files.

     

    http://patrickhoban.wordpress.com/2011/07/09/124/

     

    Regards,

     

    Patrick

     
    |
    Mark as:
  • Mr_Moon
    2 posts
    Oct 20, 2011
    Currently Being Moderated
    Oct 20, 2011 5:36 AM   in reply to PatrickHoban1

    We fixed this issue by installing patch 10.1.1. You can download this patch from Adobe’s FTP site: ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.1.1/misc/ .

    The cause was that many of our auto-generated documents contained the “CR” in either the filename or pathname.

     

    Good luck fixing this issue!

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points