Quote:
Originally Posted by evdberg
Hi Eric,
The error comes after the selection window to choose the destination path and file. I also tried running the script itself, but that resulted in the same error. The message states the data is not base64. My guess is that the script can not find the key and is trying to use something else as key (hence the error message). How should that activation.dat file look like and where is the key located? Maybe I can then manually see what is the problem.
Thanks,
Erwin
|
Ervin,
Here is my own activation.dat file:
http://epstewart.home.comcast.net/activation.dat
There are
<privateLicenseKey></privateLicenseKey> tags in it. In between is the key itself, which I believe corresponds to the one that may be messed up in your case. However, be aware that this is
my key and will not work on anyone else's computer, since it is tied to the computer and user log-in of the Adobe Digital Editions user — me — that created it when he authorized ADE.
You can inspect
~/Library/Application Support/Adobe/Digital Editions/activation.dat on your Mac, in the
~/ hierarchy for your log-in account. Maybe you can see what the problem is.
I can't quite imagine why there is a complaint about "not being base-64," since I believe
any string of bits can be interpreted as being base-64! Perhaps the problem is one of the length of the string not being appropriate to a string of base-64 digits. I.e., base-64 digits require 6 bits per digit, so maybe your key's length in bits is not divisible by 6. (If you inspect the file in TextEdit, you should see a bunch of gobbledygook between the
<privateLicenseKey></privateLicenseKey> tags. Keep in mind that TextEdit is "seeing" 8-bit bytes, i.e., ASCII code.)
Anyway, have you tried just de-activating and re-activating your account in ADE? I would trash your
activation.dat file if it's still present after the de-activation, then re-activate, thus generating a new
activation.dat file to use with the script. Or, create a new user account on your Mac and activate ADE under that account, and then see if the script works under that account.
Good luck ...
Eric