License Troubleshooting Guide

Transcription

1 License Troubleshooting Guide General Information License Versions There are two license systems in use: 1. SentinelLM v7 This uses Site Codes with format 0x04-0x SentinelRMS v8 This uses Site Codes with format 4-* It is required to support Windows Vista / Server The transition information is as follows (by package version): Product LM RMS H SH M16C 5.43r r00 M32C 5.41r01 TBA R32C 1.01r00 TBA Stand-alone licenses I don't understand where all the information needed for registration can be found. There are two locations to check: 1. The labels on the back of the media case. o P/No: The Product number, e.g. S32HEWMCSH8-1-6 o S/No: The Serial number, e.g o PVC: The Product Verfication Code, e.g ABC o Ver: The toolchain's version number, e.g Do not give the HEW version number! 2. During installation a Site Code is shown. This can also be obtained using the HEW 4.05 License Management ECX, or using the Sentinel echoid utility. I didn't see a Site Code during installation. Ensure you select the European region in the installer - selecting the Japan/Asia region omits all the license support utilities. Even if you have downloaded the evaluation version from the website and are in Japan/Asia, select the European region so you can purchase the tool later. I can't find an Add Key shortcut on the Start menu. From mid 2009, the installers no longer use the Add Key utility. It has been replaced by the HEW 4.05 License Management ECX.

2 I can't find the Help > Technical Support > License Management menu in HEW. This was distributed with HEW A version is available for HEW 4.02 onwards on the Renesas website: Mgr.zip I added the key, but the compiler still reports an expired trial when building. Check you added the key to the compiler version used in the HEW project (this can be viewed by right-clicking the current project in HEW's workspace view and selecting Properties from the context menu). Check you added the key in the correct format (as well as text embedded in the , the license is supplied in an attached text file). This is a single line of random characters, a # character and then some comments to help you identify the license. For keys starting "*B 123 " the space must be retained. Note the Add Key utility does not verify the key, so the License Management ECX is the preferred method for adding SentinelRMS keys. I have installed the license key, but HEW's About dialog-box still reports 'Evaluation Version'. Ignore this information as it does not refer to the compiler's license or support status. I have installed the license key, but HEW still reports 'Unsupported Freeware Copy'. Ignore this information as it does not refer to the compiler's license or support status. It only refers to a deprecated Flash extension. After using AutoUpdate, my license doesn't work. Note there is an Add Key shortcut for every version - the license key needs to be reapplied to the new version. (Only applies to older licenses - the licenses starting *B are in a shared location.) After using AutoUpdate, my license doesn't work and the Site Code has changed. Use the table at the start of this guide to check if the Sentinel version changed with the new compiler version. You may need to apply for a new license key using the license transfer form. Dongle licenses How can I buy a dongle? This depends on your distributor, some only supply dongles with a compiler, others allow dongles to be purchased separately. They also set the pricing.

3 I already have a dongle, can I use it for more than one compiler? Yes, when you purchase the second compiler, quote the serial number of the new compiler and give the dongle Site Code (0x80-0x11111) when registering. I have an old IAR toolchain with a Sentinel parallel port dongle. The Renesas USB dongle is ignored. The Sentinel parallel and USB dongles are not mutually compatible. It is possible to register the Renesas toolchain to the IAR parallel port dongle. Please contact support for more information. I have a dongle based license key, but the HEW License Management ECX says it is invalid. Check that the dongle is inserted when trying to add the license key. There is a bug in the ECX that prevents SentinelLM style keys being added - you can add the key using either the Sentinel wlmadmin utility (supplied with some compiler packages) or manually by editing the license file: C:\Documents and Settings\All Users\Documents\Renesas\Licenses\lservrc How do I transfer a dongle license? The original dongle must be returned to RTE before a new license key can be issued. Network licenses I have received the key, how do I add it? The server CD includes an Add button on the auto-play front-end. Alternatively, you can use the Sentinel wlmadmin utility (in the SentinelLM\Admin.W32 folder) to add the key interactively. Ensure you select "Add Feature > > To Server and its File" so that the license is still available if you need to restart the server. The license key should not be added to the workstations - it only enables the server and will have no positive effect on the workstations. How do I configure the workstations to use the server? A bug in the SentinelRMS system means this is more complex than intended. With the provided tools, when the final seat is used, all seats block for 30 minutes. The workaround is to configure the toolchain's build environment: 1. Close the workspace. 2. Select Tools > Administration 3. In the Tools Administration dialog box, expand the Toolchains folder and select the failing toolchain (e.g. SuperH RISC engine Standard Toolchain v ). 4. Click the Properties... button. 5. In the Properties dialog box, select the Environment tab. 6. Click the Add... button. 7. Enter these details: Variable: LSFORCEHOST Value: <server hostname/ipaddress, e.g. myserver>

4 8. Click OK. The Environment Variables list will now include a line: LSFORCEHOST=myserver 9. Click OK to close the Properties dialog box. 10. Click OK to close the Tools Administration dialog box. 11. Reload workspace. The project should now build with the correct license. Note with this method, each version of the toolchain has its own list of environment variables and will need updating as above. Alternatively, you can set LSFORCEHOST in the system environment variables, but this may have side-effects on other licensed products. After running AutoUpdate on the workstation it reports an incompatible server version. Check the table for the transition from SentinelLM to SentinelRMS. The server must be SentinelRMS to support SentinelRMS (and LM) clients. How do I upgrade the Sentinel server service? Version can be downloaded from the Renesas website: _update.zip This walkthrough demonstrates the license server service changes on a clean Windows Server 2000: 1. Installed SentinelLM service v7.2.0 Checked Control Panel > Admin Tools > Services A service 'SentinelLM' is running. 2. Added license for SH toolchain using wlmadmin v7.2 Checked the license was stored in "C:\Program Files\Rainbow Technologies\SentinelLM Server\English\lservrc" 3. Used SH v9.0.2 (a v7 client) OK. 4. Installed SentinelRMS service v8.1.1 Checked Control Panel > Admin Tools > Services A service 'Sentinel RMS License Manager' is running. The 'SentinelLM' service is no longer listed. In wlmadmin, after restarting, the server does not list the license. The SH v9.0.2 compiler fails as it no longer gets a license. 5. In wlmadmin, used "Add Feature > From a File > To Server and its File" and navigated to the old license file (see step 2 for path). This added the original license to the new server. Now the licenses are stored in the file "C:\Program Files\Common Files\Safenet Sentinel\Sentinel RMS License Manager\WinNT\lservrc". 6. Used SH v9.0.2 OK. Used SH v9.2.0 (a v8 client) OK. After upgrading the server, all the licenses have vanished. The transition from SentinelLM to RMS does not transfer the licenses. They have to be manually transferred. See step 5 above.

5 How do I transfer a network license? We recommend updating to or later to support the toolchains released since early 2008 (refer to previous FAQ: "How do I upgrade the Sentinel server service?") Assuming version 8.x, there are four main steps: 1. Install the server service on the new server Fill in a license transfer form s/european_pdfs/license_transfer_form.pdf 2. Use wechoid (in SentinelLM\Admin.W32) to select two site codes: 2.1. Disk ID to give 4-* Host name + MAC address to give 18-* Use wlmadmin.exe (in SentinelLM\Admin.W32) to revoke the license on the original server 3.1. Refer to the System Administration help (on Cd in SentinelLM\index.html > About License Revocation) for how to do this. This will create a revocation ticket. 4. Request the new license by sending us the transfer form + revocation ticket (in plain text as we need to decode it). Do I need a new license key if I change workstations? No - the network server will support any workstation. I want to lock the licenses to only some workstations. A custom key can be used to limit your licenses to particular subnets. Contact support for more information.