Licenses

ChrisF · #1 09-28-2010, 07:18 AM

I've been running a fully-licensed VBPro v7.2a on our build machine for almost a year now. Last night my build script stopped saying "Evaluation license limited to 50 steps." What happened?

kinook · #2 09-28-2010, 08:01 AM

I don't know. Apparently the license info got removed. Try reinstalling and registering again.

ChrisF · #3 09-28-2010, 08:06 AM

I did just that. I have several *.bld scripts, with a main build script that's >50 lines. Do I need to install the license in ALL of them? When looking at scripts, I usually go to File->Recent Files instead of opening multiple VBPro windows.

kinook · #4 09-28-2010, 08:11 AM

No, the license applies to the Visual Build installation, not a particular .bld file. See the bottom of Introduction -> Installation in the offline help (F1) for other methods to register if the regular method isn't working or sticking.

ChrisF · #5 09-28-2010, 08:27 AM

Thanks!

ChrisF · #6 10-07-2010, 07:12 AM

It happened again, on a scheduled task, if that makes any difference. Odd thing is, I ran the same script manually, without changing the license registration, and it did run. What gives? I'll try the suggestion at the end of the suggested page this time.

kinook · #7 10-07-2010, 07:15 AM

Something must be occasionally preventing the licensing component from reading the license info.

ChrisF · #8 10-07-2010, 07:55 AM

What could that "something" be? Windows update, java update? I'm running Vista Business. This just started happening on the post date of this thread.

kinook · #9 10-07-2010, 07:59 AM

I don't know. It could be a side effect of a Windows Update or other software update, or interference from security or other background software. We've never seen the problem here. The alternate registration methods should provide a workaround.

ChrisF · #10 10-08-2010, 07:26 AM

Here are the three lines needed for the Help -> Register API

Product: Visual Build Pro v. 7
Name: MyCompany (3-computer license)
Key: 123456-654321-...-123456

Here are the instructions for the suggested alternative method.

Alternatively, create a text file named C:\Program Files\VisBuildPro7\System\VisBuildSvr.ini (in the VBP installation System folder) with contents like:

[License]
PortableKey=license name + count,license key

How should I map my 3-line license into to the *.ini file?

As an additional note, when I do a Help->Register on the problematic *.bld file, I do NOT see the license info in there, even after just adding it the day before. But I should correct? Again, even in this scenario, I can run he script manually. Interestingly, I have another machine with XP Pro and I do see the license info.

kinook · #11 10-08-2010, 07:36 AM

PortableKey=MyCompany (3-computer license),123456-654321-...-123456

Yes, once Visual Build has been registered, it will normally remain registered.

ChrisF · #12 10-08-2010, 02:03 PM

I did the *.ini trick; we'll see what happens tonight.