4,391 Posts served
10,712 Conversations started
- Academic

- Android

- Art, Music, & Animation

- Embedded Computing

- Events

- Game Development

- Graphics & Media

- Intel SW Partner Program

- Intel® AppUp Developer Program

- Manageability & Security

- Mobility

- Open Source

- Parallel Programming

- Performance and Optimization

- Power Efficiency

- Site News & Announcements

- Software Tools

- Association for Computing Machinery TechNews (ACM)
- Go Parallel! (Dr. Dobbs)
- HPCwire (Tabor Communications, Inc.)
- insideHPC (John West)
- Joe Duffy's Weblog (Microsoft)
- Microsoft Parallel Programming Development Center (Microsoft Germany)
- MultiCoreInfo.com
- scalability.org (Scalable Informatics)
- Software Dev Blog (Intel Germany)
- Soft Talk Blog (Intel United Kingdom)
- The Moth (Microsoft)
How to Upgrade Intel Compiler license for IDB feature in Intel compiler 11.0.XX version
By Wise Chen (Intel) (2 posts) on March 1, 2009 at 9:24 pm
Recently, I got 2 QuAD issues (Q529476, Q537439) in which our customers don’t know how to upgrade their old licenses to 11.0.XX licenses with IDB feature.
Issue status
In generally, without upgrade license, compiler attempts to launch eclipse or some features and it errors stating could not find a license when customer try running the idb command.
Actually, IDB command in 11.0.XX versions needs a new license if our customer used old Intel compiler version. So upgrading license is a MUST action for our customer.
Solution
There are 2 ways to resolve this issue:
1. let our customer upgrade the license by themselves
2. Help our customer to upgrade the license
The Intel Software Development Products Registration Center website is at https://registrationcenter.intel.com/regcenter/register.aspx, customers should provide their email address and old serial number SN and then click ‘Register Product’ button to upgrade their new license for 11.0.XX Intel Compiler products.
Categories: Uncategorized
Tags: License issue
For more complete information about compiler optimizations, see our Optimization Notice.

