I lent another book as protected pdf. ADE says «There were errors found in this book». But I can open it in Adobe Reader.
I didn't think Adobe Reader is capable of opening any DRM .pdf.
This is probably a password protected pdf, which is different from DRM pdf. I am not surprised if ADE can't open a password protected pdf.
Where will I find the uuid on iOS or Android? I open the books in Bluefire.
Whoops, I was thinking OSX which would have been the same as Windows.
I see a comment in http://www.bluefirereader.com/using-library-books.html saying
You can check the Adobe ID that Bluefire Reader is authorized with from the Info Screen of the Library View. It should say 'Adobe eBooks are Enabled' and show you the ID.
but I don't know if that returns the uuid as well as the external email ID.
(I don't currently have access to the ios device I often use that has Bluefire on)
~~~
Next suggestion is to try ADE v1.7.2. See (1) below.
There is some connection between the registration of the different versions,
you should go through the ctrl-shift-D/reauthorize rigmarole once on to ADE1.7.2
I don't think this really is one of the bugs in ADE2, but maybe the different version will stire things up enough anyway ...???.
Also, I have put in details of the authorization system at (2) below in case it helps.
(1) ~~~~~~~~~
There are lots of bugs in ADE2.0 (and 2.0.1). Try replacing ADE2.0 with the older but more reliable v1.7.2.
(You can have them both installed at once if you like.)
Version 1.7.2, it is a little difficult to find, available on Adobe site for Windows and for Mac.
http://helpx.adobe.com/digital-editions/kb/cant-install-digital-editio ns.html
The forum software is sometimes corrupting the link above. There shouldn't be a blank in 'editio ns.html'. The following redirects to the same page: http://tinyurl.com/diged172
Some people have found ADE trying to upgrade automatically.
It appears (not 100% sure) that if you install ADE2.0 as a new install (not as an upgrade) that your 1.7.2 will continue to run.
Probably best to say no if 2.0.x installation asks if you want to migrate your library.
(2) ~~~~~~~
Horribly long description of the Adobe account/uuid/email ID arrangement follows.
Usually you don't need to know, but as your situation has somehow got very complicated maybe you do.
~
Every Adobe account is permamently associated with an internal uuid, and at any point in time associated with an external email ID.
Devices are always fundamentally registered with the account/uuid; even though the email ID is used to perform the registration.
Sometimes devices show the registration as the email ID currently associated with the account/uuid, sometimes the email ID that was associated at the time of registration.
An email ID can only be associated with one account/uuid at a time: however, it is possible for the same email ID to be associated with different accounts at different times.
You can then get the situation ...
- create account/uuid1 associated with emailID1
- device1 authorized using emailID1 with account/uuid1
- emailID2 associated with account/uuid1, thus emailID1 no longer associated with any account/uuid (using Adobe web page)
- create account/uuid2 associated with emailID1
- device2 registered using emailID1 with account/uuid2
- you are now in the state ...
- query registration of device 1: it tells you emailID1
- query registration of device 2: it also tells you emailID1
- even though device 1 and device 2 are authorized with different account/uuid.