Cannot run idb version 11

[J__S__Park]

Hello

I installed the intel fortran compiler 11.069 with intel debugger (Non-commercial License)

Ifort works fine but idb has a problem.

I use intel 64 version linux. (Debian Lenny)

When i run idb or idbc, it says following error message.

Intel Debugger for applications running on Intel 64, Version 11.0, Build [1.1510.2.66]

Error: A license for DbgL is not available (-5,357).

Make sure that a license file is being used that contains a license
for the requested feature. If your license requires a license server,
make sure that the server is using the right license file (usually,
this would be the same license file that is being used by this
application), and make sure that you have not changed the license
file since starting the server.

License file(s) used were (in this order):
1. Trusted Storage
2. /opt/intel/Compiler/11.0/069/licenses
3. /opt/intel/licenses/l_NDN5NJS6.lic
4. /home/jinseok/intel/licenses
5. /Users/Shared/Library/Application Support/Intel/Licenses
6. /opt/intel/Compiler/11.0/069/bin/intel64/*.lic

Please visit http://support.intel.com/support/performancetools/support.htm if you require technical assistance.

could not checkout FLEXlm license

Is there a solution for this problem ?

[etowie]

Hi,

I am also having an identical problem with the Intel debugger version 11 (packaged with 11.069), but I am running on Ubuntu 8.04 with a non-commercial license.

My license file is still valid and is located in the /opt/intel/licenses/ folder which is on the search path for the intel debugger.

[Kevin_D_Intel]

The IDB version 11.0 now has licensing enabled. The non-commercial license does not contain the required DgbL componentwhich leads to the error noted.

I do not have a resolution at this time, so please stand by for further instruction.

[Steven_L_Intel1]

Log in to the Intel Registration Center, find your serial number and click on it and then select the option to email the license file. When you receive the new license, replace the existing one with this one.

Let me know if this helps.

[J__S__Park]

Quoting - Steve Lionel (Intel)

Log in to the Intel Registration Center, find your serial number and click on it and then select the option to email the license file. When you receive the new license, replace the existing one with this one.

Let me know if this helps.

Even though I receive the license file again, it is not working also. Moreover, I can't see 'DbgL' in my license file.

[Steven_L_Intel1]

Kevin posted at the same time I did, and he has more information. Wait for his follow-up. We apologize for the inconvenience.

[Kevin_D_Intel]

The resolution of this issue requires Linux only customers obtain an updated Intel license (.lic) file containing the required DbgL component. How to accomplish that depends on your license type.

For non-commercial customers with an Intel Registration Center account, please follow the steps outlined below for Commercial customers. For all other non-commercial customers, please register for a new non-commercial license here.

For commercial and academic customers, please follow these steps:

1. Log into the Intel Registration Center here.

2. On the main landing page, click on the version # appearing in the Downloads (Build #) column for the Intel Fortran Compiler. Currently this will either be 10.1 (021) or 11.0 (069) depending on your specific Fortran product subscription.

3. On the next view, look for table near the bottom of the new page showing the Serial Number information for your subscription. Click on the Upgrade available link appearing in the Serial Number column to have a new license generated and emailed to you

Please contact Intel Premier Support here if you experience problems obtaining an updated license.

We apologize for the inconvenience.

This issue is also discussed in the Knowledge Base article located (here).

[Kevin_D_Intel]

To aeroparkgmail.com,

Please register for another NCOM license and disregard the license you received following your registering earlier this morning.

Kevin

[etowie]

Obtaining a new license seems to have fixed the problem, thanks!!

Ewan