I initially anonymously authorized my computer to read my new book, which worked fine. But now I want to read mi book in other computer. What I did was to de-authorize my computer and items, and then try again to authorize with my adobe ID. The computer was authorized OK, but my book still requires an eVendor ID and my adobe ID doesn't work, it prompts the following message:
"The vendor account you entered is not associated with the item you are trying to open. Try again"
Do I need a special eVendor ID? How do I get it?
I already tried with the username and password of the site I purchased my book from, but then it says that the log in or password for the selected eBook vendor is incorrect.
Can you help me, please?
Unfortunately, you de-authorized your computer but NOT your items.
Once a book is accessed on one ID, it cannot be used on another ID.
I am afraid you may be stuck ... if you are lucky the vendors will give you a second chance.
This is a vicious trap that Adobe lays for unsuspecting customers.
When you register 'without ID', ADE creates an anonymous/implicit ID with limited powers (eg can't be used to share with other devices).
Whenever you first load a DRM book, that copy of the book is associated with whatever ID the computer is registered to at the time.
Any book you load while this anonymous ID is active gets associated with that ID, and can't be read on any other device.
When you properly register your computer with a real ID, that old anonymous ID is lost.
Now you don't have any devices that can read the book.
I think that even if you de-authorize again and revert to anynomous authorization, it will be a different anonymous ID, but worth a try.
Not helpful for you if reverting to anonymous doesn't help, but general comment that might help other readers .....
The only way I know round this is to use a DRM stripper such as epubee BEFORE you deauthorize the device.
I do NOT advocate using such code to get around the valid limitations placed on a DRM book.
However, where the problem arises only because of the ineptness of Adobe's ADEPT DRM infrastructure and its implementation,
such a measure is totally justifiable.