FLEXnet Licensing Error -25,147 in CCS v.5.1.1.00031

Hi Erik,

if the same setup works for CCSv4 .. I suspect you have a v4 license which will not work with v5.  Can you double check this?  If you have an active subscription you can upgrade to a v5 license on you own

Please keep us informed.

Best Regards,
Lisa

Lisa,

Thanks for your prompt response!  I did get access to the Registered Software page on TI.com and verified that we did get a license for v.5.  There was nothing to upgrade. What else could be causing this error?

Thanks,
Erik 

Hi Erik,

would you be able to send the license file for verification?  Can you provide details on your setup?

Best Regards,
Lisa

Lisa,

I think I just found a clue here.  In LMTOOLS when I look under Config Services, all of the information is correct.  The updated license file is present under the Path line, and lmgrd.exe path is correctly specified.  HOWEVER--when I perform a Status Enquiry under Server Status, it looks like it's still looking at the v.4 license for some reason.  (I've tried stopping the license server and re-reading the license, which says it completed successfully.)  Below is the text I get from the Status Enquiry window:

----------------------------------------------------------------------------
License server status: 27001@Q*********
License file(s) on Q********: demo\demo.lic:licenses\tidspssw\TMDSCCS-ALLUNVF100-v4.0.lic:

Q******: license server UP (MASTER) v11.10

Vendor daemon status (on Q********):

Any ideas?

Thanks,

Erik

Hi Erik,

yeah, I am wondering if it is pulling the v4 license.  What if you move that license file away so only the v5 is even there to find.  Did you also try removing the v4 license from the flexnet system? 

Best Regards,
Lisa

Lisa,

I tried doing that, but Flexnet still sees the demo license and the v.4 license.  I thought the v.4 license was removed from Flexnet, but apparently not.  Can you advise me on how to get it to stop looking at that old license?  I have the path to the license file correct, but I'm not sure what else I need to do.

Thanks!

Erik

Hi Erik,

a few further comments

- if both licenses are in flexnet, one will randomly be selected so v5 could wrongly select the v4 license.

- I am confused as you mention a demo license?  Are you on an evaluation license?  If so, CCS will not look for a different license until the trial expires.

- have you tried making a copy of the v4 license file somewhere and simply removing it

Best Regards,
Lisa

Hi Lisa,

I did remove all of the older licenses that flexnet might be pointing to, but even after a license server restart and license file re-read, it still sees that demo license (which I don't see anywhere, so I'm not sure where it's finding that!)

I think at this point it might be worth trying to just re-host the license.  I have a server I just brought online that doesn't have anything else that uses flexnet, and it's a brand new installation of Windows Server 2008 R2.  Hopefully we'll have fewer issues getting it up as a result.  Can you please let me know what needs to happen to re-host the license?

Thanks!

Erik

Hi Erik,

I think the best would be to wait out the trial license and continue at that point.  CCS will not look for another license until the trial expires so you can not really test unless you do a fresh pc/setup.  The license MAC should be that of your server, and is user pc independent.

Best REgards,

LIsa

Lisa,

We are not in a position to wait out the trial license.  The trial license doesn't give us access to CCS v.5, which is the only product we use.  We need to re-host this license.  There is a license server with a clean install of Server 2008 R2 that we can use.  Please tell me what needs to happen in order to get this done.

Thanks,

Erik

Hi Erik,

even if you rehost CCS will first use the trial unless you create a fresh CCS setup.  I am very confused as the trial license is a full featured license so I don't know what you mean by it not allowing you access ...???

If you wish to give things a try you can rehost once yourself here:

www.ti.com/myregisteredsoftware

Please keep us informed.

Best Regards,

Lisa

Lisa,

Thanks for the information.  Out of curiosity, if we were ever to need to rehost a second time, what is the process for that?  I would like to have that information documented in case I need it someday.

What I meant by CCS v.5 not being able to access the demo license is this: because the demo license is for v.4, the CCS v.5 installation I have running won't use it.  It gives me the error that I posted at the beginning of this thread.  So the demo version of CCS v.5 is not full-featured because it won't even recognize that there is a demo license it should be using.  This is causing problems for us because the MSP430 feature set is limited as a result.

I can certainly perform a clean installation of the client software, if that's what's required to skip the period of using a trial license.  Is that what you meant by create a fresh CCS setup?  So I would just perform a clean install of CCS v.5 and specify immediately the license server location, and that would preclude the use of a trial license?

Thanks as always!

Erik

Hi Erik,

yes a clean installation that has not yet been setup or any license type selected could be used to verify your license server.  It is simply once a trial license is selected/setup CCS will use that without further thought until it expires.

For any furhter rehosting you need to contact the specific license team and get their approval.  They will look up the license history and help you.

ccs_subscriptions@list.ti.com

Best Regards,
Lisa

Lisa,

Success!  I was able to rehost the license, perform a fresh installation of the license management tools, and get CCS v.5 to check out licenses.  I did have to spend a fair amount of time trying to figure out what the vendor daemon (tidspssw) was doing when it communicated with the license server.  It apparently does not use port 27000, so at first I tried telling it to use that specific port by modifying the license file.  No dice.  Then I just opened up every port on my license server higher than 27000 and that worked, but limiting it to ports 27000-27010 did not.  So that vendor daemon uses some oddball port, and I didn't have time to waste finding out what that was.

I ended up just creating firewall exceptions for all of the licensing tools, including lmgrd, tidspssw, lmutil, and lmadmin.  It seems like lmadmin was the kicker.  Once I created that firewall exception, the product began to license correctly.  (I'm making these notes at this point purely so that someone who is Google searching this issue has a chance at resolving his/her issue!)

Here's another thing for newbies to note: I struck out trying to get help from TI phone support.  I tried several different phone numbers, some of which are listed on web pages but no longer are in service.  It was a week before I finally decided to give the forum a shot, and I am so glad I did.  You have been extremely helpful, and your responses were always very prompt (within a few hours of my posts.)  Thank you SO much for all of the assistance you provided me!

Erik

Hi Erik,

great, very happy to hear you are up and running!   Thanks for the update and feedback.  We always try our best here :  )   I appologize as this might have been a bit of a frustrating situation but unfortunately license issues can be tricky due to the number of error codes, third party software etc.

Anyhow ... all the best,

Lisa