| Product(s): | AssetWise APM Foundation | ||
| Version(s): | Release 7.x | ||
| Environment: | N\A | ||
| Area: | Licensing | ||
| Subarea: | N\A |
Problem
In APM, the Bentley Activation Key resides in 2 areas:
- The local registry files on the machine running an APM server or thick client
- The APM database being accessed
On startup, APM Server code will verify that the registry and database keys match, if not, it will provide the union of access available according to the keys that are found. If there is no key in the database, the startup will write in the one from the registry.
If you need to change the Activation Key you are operating under, both the registry and the database will need to be updated.
Solution
- Shutdown all APM Services and ThickClients
- Clear the database activation key using the script below.
SQL Server
update oq.CUSTOMERINFORMATIO set ACTIVATNKEY=null, vers=vers+1;
Oracle
update oq.CUSTOMERINFORMATIO set ACTIVATNKEY=null, vers=vers+1;
commit;
3. On Machines hosting Server and/or Thick client instances
Run the Product Activation Wizard from within the APM Configuration utility for your APM server installation.
This will:
- Set Permissions for accessing folders and registry as required for Bentley Licensing application to run properly
- Provide a series prompts to register your new Activation Key
Run Licencetool.exe (from ...\bin) to reactivate products if they were not activated
If APM foundation does not re-activate properly
go to License Checkout tab
check out CONNECTIONS passport and check them back in
check out CONNECTIONS passport and check them back in
Repeat for any other products that do not respond to the use Activate button
5. Restart all Servers.
| Original Author: | Giselle Notte |