Although it has been a long time since the original query, I thought I would add my 2 cents on this issue. I had the same problem -- created a PDF with
Acrobat 9, enabled for commenting, sent out to coworkers, who then reported the dreaded "rights are no longer available" message. After many, many troubleshooting permutations, I finally found the problem to be related to the timestamp on the file, as noted above by Zofia_Remiszewska.
I am on the US east coast, and the document was sent to coworkers on the US west coast, 3 hours earlier. When they opened the document, it appeared to be "from the future" (lol) and therefore suspect. This was born out by the fact that the next day, the file behaved as expected for them. I also verified this on a test system, where I was able to switch the time setting. By the way, this happened with both Reader 8 and 9.
So, I guess the workaround is either to change your computer's time before sending a file with rights extensions to someone in an earlier time zone, or create it and hold it until they have caught up with the time in the file's timestamp.
That has to be about the weirdest bug I have encountered to date...
Hi, I am Acrobat QE, and I try to reproduce the problem that you have reported. Since I don't have your test file so our developer askes me to do the following steps to reproduce the problem but we can't reproduce the problem. So can you please send me the test file at (email@example.com). Thanks.
Steps to reproduce the problem:
Set your time zone to London, and your clock to 3AM (pick a day, say 4/18) Reader-Enable or sign a file Set your time zone to San Francisco, and your clock to 9PM on 4/17. That's 1 hour later. See if the file is enabled or the signature is valid.
Please send me emial if you have the steps to reproduce the problem too.
I was unable to reproduce the issue.
I’ve used AcroPro9.3.1 to ReaderExtend a PDF on machine that uses GMT+9:30 and immediately opened it on a different machine that uses GMT+5:30 using Adobe Reader 8.1.7 and it was just working fine.
Could you please specify the exact versions of Acrobat and Reader that you have used and upload the problematic test files (without ReaderExtended and with ReaderExtended) ?
Are you seeing this issue with any PDF file or with a specific PDF?
Actually, I have provided this information to Steven Yen in response to his post just before yours. He informs me he was able to reproduce the problem with the PDF file I provided, and has forwarded the issue to development.
For the record, here are the repro steps I gave to Steven:
"This document contained certain rights to enable special features in Adobe Reader. The document has been changed since it was created and these rights are no longer valid. Please contact the author for the original version of this document."
It is further observed that after the remote system time advances to a time later than the timestamp, the document opens as expected with commenting enabled. This behavior was experienced on two other computers, both located in California, on Pacific time.
The PDF was created on Windows XP SP3. This behavior occurred with any/all PDFs created in the above manner. If you would like me to provide sample files, please let me know the best way to get them to you.
I have discussed with our developer that we have found your computer should match the “real time”, and it is an error to open a file at a time earlier than when the document was signed. If the signing time was for UB, then the UB will be invalid if we believe the current time is earlier than the signing time. We do allow for small clock errors, but 5 hours is too much.
Hi N Santosh Kumar
Look like this is a user error that his computer should match the "real time", and it is an error to open a file at a time earlier than when the document was signed. If the signing time was for UB, then the UB will be invalid if we believe the current time is earlier than the signing time. We do allow for small clock errors, but 5 hours is too much.
I'm also getting this error with a certain pdf that I was provided. However it only appears on some computers and not others. I haven't been able to determine why some and not others. It's not reader version because I've had it happen with reader version 7, then upgraded to 8.22 and it still happens. I've uninstalled and reinstalled a bunch of times. I also tried installing acrobat 8 standard and opened the file and entered info into the forms successfully with acrobat 8 standard. But when I open the file with reader 8 on the same computer, I get the error.
However on some other computers I can open the pdf with reader 8.13 through 8.22 and I don't get the error and I can enter text into the forms just fine.
I'm unable to edit the pdf with acrobat because it is locked by password security.
Any help? Any info you'd like me to provide? Thanks!
Somethings to note:
All of the computers here have their time synced to a server so they should all be the same timezone.
Some of them are running XP SP2 and and some SP3
Please check the computers that have the problem to make sure their times are current time. We used to have the problem that computer's time is 5 hours early than current time even they are in the same timezone.
Acrobat 8 Standard always can fill in data no matter the uB rights are broken or not. The UB broken messages only show up in Reader and won't show up in Acrobat products.
Please send me the test files so I can do more further investigation.
Europe, Middle East and Africa