This article applies to:
E-Prime 3.0
E-Prime 2.0
This bug has been corrected in E-Prime 3.0.3.31.
Symptoms
E-Prime 2.0 produces grace period dialog when E-Prime 3.0 license key is attached.
Detail
In E-Prime 3.0.3.9, there is a known issue when attempting to open E-Prime 2.0 while both E-Prime 2.0 and E-Prime 3.0 License Keys are attached. This occurs because E-Prime 2.0 searches for a license key and finds the E-Prime 3.0 key first and determines it is not allowable. This only occurs when the "Key ID" property listed in http://localhost:1947/ is lower for E-Prime 3.0 than it is for E-Prime 2.0.
Users with an E-Prime 3.0 Upgrade License that was shipped with E-Prime 3.0.3.9 need to contact support to electronically update their license key.
Solution
This bug has been fixed in E-Prime 3.0.3.31. Upgrade to E-Prime 3.0.3.31 or later.
NOTE: There are no other differences (e.g., Runtime) between 3.0.3.9 and 3.0.3.31. Users do not need to have any concerns about updating.
Workaround
These workarounds are intended only for those users who are unable to update to the E-Prime version that contains the bug fix.
Detach the E-Prime 3.0 License Key while using E-Prime 2.0.
Comments
0 comments
Please sign in to leave a comment.