Your responses helped narrow down the problem which I appreicate. I would like thank everyone in the forum who replied. This has been a long journey (including an interesting encounter with someone who tried to trick me into turning over my serial number). Using a "Type 1" exception, you can activate your license on another computer or with a browser that supports TLS 1.2 (like Firefox or Chrome) by generating a response code and going to the following page: Offline Activation You can work around all of this by using the Adobe Provisioning Toolkit Enterprise Edition found on the Creative Suite Enterprise Deployment page. Windows Vista and 7 need the latest services packs AND all Windows Updates installed and maybe some registry hacks on top of that. You can patch up Windows XP if you don't mind your using POSReady updates. Basically, the connection with the activation server uses either TLS 1.1 or 1.2 which some older operating systems don't support. I'm pretty sure I found out the root cause of the failure. I spent some serious time looking through installer logs like PDapp.log and Oobelib.log, and using various tools like Process Explorer to see exactly what the installer was doing and at what step it failed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |