Licenses
 

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?

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

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.

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.

Thanks!

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.

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

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.

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.

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.

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

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

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