Adobe Digital Editions Authorization

[anacreon]

I was extremely surprised recently when I couldn't read any PDF on the Sage - supposedly they weren't authorized by ADE - while there had been no change whatsoever to F/w and such. There was no problem with the kepubs (I don't read plain epubs).
I checked that the same PDFs had no problem on Elipsa, and decided to turn off the Sage.
I was happy that after turning it back on, all PDFs became readable again.
I wonder what type of problem would "de-authorize" reading PDFs but not kepubs, and would be solved by turning a device off then on.

EDIT: I strip DRMs on all books (PDFs or epubs or kindle files) as soon as bought, so ADE shouldn't have a say on them anyway. It is particularly necessary for PDFs since a higher proportion do not have TOCs than epubs'.

[davidfor]

Originally Posted by anacreon

I was extremely surprised recently when I couldn't read any PDF on the Sage - supposedly they weren't authorized by ADE - while there had been no change whatsoever to F/w and such. There was no problem with the kepubs (I don't read plain epubs).
I checked that the same PDFs had no problem on Elipsa, and decided to turn off the Sage.
I was happy that after turning it back on, all PDFs became readable again.
I wonder what type of problem would "de-authorize" reading PDFs but not kepubs, and would be solved by turning a device off then on.

EDIT: I strip DRMs on all books (PDFs or epubs or kindle files) as soon as bought, so ADE shouldn't have a say on them anyway. It is particularly necessary for PDFs since a higher proportion do not have TOCs than epubs'.

Firstly, the DRM mechanisms for ePub and PDF is completely different from and unrelated to the DRM mechanism for kepubs. For ePub and PDF, the Adobe RMSDK is used. And is used for ePubs and PDF with and without DRM. So a failure on one doesn't mean a failure for the other.

The DRM error is something that has been around a while. It isn't obvious what is happening. And rebooting the device usually solves it. That suggests it could be a problem with one of the processes used for reading. It could be that a process has hung, or has crashed and not restarted properly. Restarting the device clears those problems as everything gets started anew.

[anacreon]

Originally Posted by davidfor

Firstly, the DRM mechanisms for ePub and PDF is completely different from and unrelated to the DRM mechanism for kepubs. For ePub and PDF, the Adobe RMSDK is used. And is used for ePubs and PDF with and without DRM. So a failure on one doesn't mean a failure for the other.

The DRM error is something that has been around a while. It isn't obvious what is happening. And rebooting the device usually solves it. That suggests it could be a problem with one of the processes used for reading. It could be that a process has hung, or has crashed and not restarted properly. Restarting the device clears those problems as everything gets started anew.

That was informative. Thank you.

[catsknit]

Originally Posted by John F

Strip the DRM.

You can't do that until you've gotten through ADE's gauntlet. I have purchased books from Google Play and when I downloaded them and imported into Calibre with plug-ins up to date, it said not authorized. After consulting with help at Apprentice Harper's blog (last year), sending the logs etc. I finally had to make a new log-in for my laptop, add ADE and Calibre to it and only then would it finally work. Something in my laptop's registry on the main login is preventing it.

[Shopaholic]

Originally Posted by DNSB

It's likely too late for you but copy only the activation.xml file to backup your Adobe authorization. The device.xml is tied to the device including the device fingerprint.

I've done this for quite a few years and it can and does work.

The alternative is to contact Adobe customer service who are pretty decent about increasing authorizations.

I will be doing this for my Libra 2. The only remaining device that was authorized. Thank you so much. It’s too late for my Clara & Aura One but at least I’ll have it for the Libra 2. I’m still shaking my head at how useless Adobe “support” was. Apparently authorizations only refer to actual computers or mobile devices like phones & tablets but not ereaders. According to them anyways.

[PeterT]

As long as you have a working activation.xml file you can just copy it to the other devices.

Sent from my Pixel 4a using Tapatalk

[Shopaholic]

Originally Posted by PeterT

As long as you have a working activation.xml file you can just copy it to the other devices.

Sent from my Pixel 4a using Tapatalk

That doesn’t work. I tried it earlier. Yes it will show that the device is authorized with ADE on the device itself but when I try to send a book to the device via ADE it gives a message not authorized for this device or something like that.

[DNSB]

Originally Posted by Shopaholic

That doesn’t work. I tried it earlier. Yes it will show that the device is authorized with ADE on the device itself but when I try to send a book to the device via ADE it gives a message not authorized for this device or something like that.

Is the activation.xml generated with the same user id as the user ID ADE is using? I've been recycling my activation.xml file for quite a few years now. As long as the line in activation.xml matches the Adobe ID used with ADE, it works for me.

<username method="AdobeID">username@something.net</username>