Can somebody tell me about the license in SILK.
I get a error message sometimes when I invoke SILK.It says,
"No License for 'Silk Test_GUI6.5'!"
ErrorMessage:All licenses are in use
This is a SilkMeter Message
while checking my client' says its the GUI license and not Client license.
What does this mean?
It (the license server) thinks you are trying to start more instances of the GUI than you have licenses for. It keeps track of the GUI and agent instances separately. If you are running into this when you should still have free licenses, run services.msc on the machine with the license server and restart the silkmeter manager. Myself, I've seen plenty of problems with the license server keeping track of agent licenses, but haven't had the same problem with the 'GUI part'.
Thanks Bala and Chris.
Chris,this clearly explains that x number of users have opened the silktest GUI already and the x+1 th user cannot be permitted.
Does this also mean that we can have the scripts at one server and give just the Agent(client) license to run these scripts.Then we wouldn't need more GUI license.
Is this the way it operates?
Is it possible to have the scripts in one machine and just with the Agent license can we run the scripts from another machine.If yes,can u please explain how to acheive it?
Theoretically, I think SilkTest was designed to do what you are suggesting (have one GUI drive several simultaneous agents). However, I don't believe that there is any easy way to explain how to accomplish this. Myself, I would focus I designing your tests so that you can swap from one agent to another at a time when the first agent would have been idle anyways. Otherwise, you may as well simply do your tests serially since the 'GUI' can't work faster simply because you are driving more agents. With my tests, I have a significant lag when my vmware images are booting and rebooting so I've thought about doing what you are asking about. When the reboot/boot is in process, I could connect to another agent (provided that machine was totally ready to go) and do some testing. Then, I could disconnect and go back to the other one. I haven't actually tried implementing this because the way I gather my results in the db is pretty much a series of lists which I now can assume all 'go together'. If I used two agents, I'd have to develop something better. Without the booting/rebooting time loss, this wouldn't make sense to me to even think about. Hope this helps...