Where are Toad for Oracle 9.7 through10.x license keys stored?
How are these license keys tracked?
How does Toad for Oracle licenses authorize Toad for Data Analysts and up to Toad Data Point 3.2?
Licensing for Toad Data Point (formerly Toad for Data Analysts) and Toad for Oracle (versions 9.7 through 10.x)
When launched, Toad Data Point will search for (in the following order):
1.
A. Windows XP:
C:\Documents and Settings\All Users\Application Data\Quest Software\Toad Data Point 3.2\license.key
B. Windows 7:
C:\Users\<user>\AppData\Roaming\Quest Software\Toad Data Point 3.2\license.key
2. A. Windows XP:
C:\Documents and Settings\<personal folder>\Local Settings\Application Data\Quest Software\ProductLicenses.xml
B. Windows 7:
C:\Users\<user>\AppData\Local\Quest Software\Toad Data Point 3.2
Note: In newer versions of Toad Data Point, the ProductLicenses.xml is stored in other locations as well. These locations may need to be checked as well.
a) Windows XP:
a. C:\Documents and Settings\<personal folder>\Application Data\{08439167-4CA5-48E9-A810-A3A7C0B80B06}
b) Windows 7:
a. C:\Users\<user>\AppData\{08439167-4CA5-48E9-A810-A3A7C0B80B06}
-or-
c) Windows XP:
a. C:\Documents and Settings\<personal folder>\Local Settings\Application Data\{08439167-4CA5-48E9-A810-A3A7C0B80B06}
d) Windows 7:
C:\Users\<user>\ Application Data\ Local \{08439167-4CA5-48E9-A810-A3A7C0B80B06}
-or-
e) Windows XP:
C:\Documents and Settings\<personal folder>\Application Data\Quest Software\Toad for Oracle\<version>\QSAuth11.key
f) Windows 7:
C:\Users\<user>\AppData\Roaming\Quest Software\Toad for Oracle\<version>\QSAuth11.key
Note: This is the old format Toad for Oracle key (21 digits). If you do not have Toad for Oracle installed, this file may not exist.
If no file is found or no applicable key is found, Toad Data Point will prompt you for a key, and create its own license.key file (in location 1). This is a .txt file with two lines. The first line is the license key; the second line is the Site Message. Be aware of upper and lower case characters and extra spaces.
Currently Toad Data Point will accept Toad for Oracle Suite license keys.
If it picks up a Toad for Oracle key (in the ProductLicenses.xml file or in the QSAuth11.key file), it will be applied automatically to Toad Data Point. It will create a license.key file with the Toad for Oracle key data it for future access (in location 1).
In Toad for Oracle's case, Toad Data Point keys will not work in Toad for Oracle. Toad for Oracle will not check for
Windows XP:
C:\Documents and Settings\All Users\Application Data\Quest Software\Toad Data Point
3.2\license.key
Windows 7:
C:\Users\<user>\AppData\Roaming\Quest Software\Toad Data Point 3.2\license.key .
However, it will check for the ProductLicenses.xml and if it is not found, it will check for any QSAuth11.key.
Starting with Toad for Oracle 10.5, Toad for Oracle will check directories for other Toad for Oracle installs on the machine (i.e. c:\Program Files\Quest Software\Toad for Oracle) and go as far back as Toad for Oracle 9.1. If a QSAuth11.key is found, it will create a copy in the local 10.x directory (in location 3).
Currently the ProductLicenses.xml will take precedence if a QSAuth11.key also found. From ProductLicenses.xml file, if multiple Toad keys are entered, it will apply the strongest key. For example, if there is a Base edition key and an Xpert edition key registered in that file, Toad for Oracle will implement the Xpert key because it enables more features. If you wish to implement a weaker key after registering a stronger key; you will need to remove the entry of the stronger key from the ProductLicenses.xml file.
Toad 11 stores the key differently than the previous versions.For security reasons, the information where the key is stored for Toad 11 is not available.
