User has multiple license keys for Benchmark Factory (BMF) for each database product (Oracle, SQL Server, Sybase, and DB2).
When entering one of the new QuestKey style keys that BMF 6.x supports (for example BMF for Oracle), and then changes it to a different key (for example Sybase) it wont let the user go back to the previous BMF for Oracle key (or any QuestKey style key that had already previously been entered).
原因
This is due to a bug in the product. Looking at the ProductLicenses.xml, it appears to be appending the key to the file rather than replacing it.
Apparently when the user changes back to a key that was previously entered, it sees the key already in the ProductLicenses.xml and doesnt do anything. So it will always prefer the last key entered, but only if it wasnt previously entered before.
解决办法
The workaround is to delete alll the Benchmark Factory entries in the file C:\Documents and Settings\<login name>\Local Settings\Application Data\Quest Software\ProductLicenses.xml.
The change should be made with care, and always make a backup copy of ProductLicenses.xml before making any changes.
NOTE: On Windows 2008 the location of the above file may differ.
For example, you would delete any entries that look like the following:
This only affects the new QuestKey style keys (alpha-numeric). Old QSA style keys (all numeric) are not affected in this particular way.
However, it should be noted that there is a related issue in that BMF 6.x will always prefer a QuestKey style key over the older QSA style keys, even if the QuestKey is a trial key and the user tries to use a QSA style key.
Both of these situations will be addressed in an upcoming 6.1.1 patch.
