I have problem with getting a correct result from "isc_service_query" when I 
pass "3A" (Get license and licensed_users), in fact I get an "Unexpected 
Output buffer value" error when IBX tries to read the license information 
from the result. From the debugging I have done it seems like I dont get the 
correct result from Interbase.

Looking at the result I see that I get a correct value on 
"isc_info_svc_get_licensed_users", but the rest of the buffer is filled with 
zeros where I expect to see 0x33 and information about licenses.

I am using Delphi 2009 and the IBX Admin component TIBServerProperties to 
reproduce this (Example code below)

procedure TForm1.Button1Click(Sender: TObject);
var i : integer;
begin
 ListBox1.Clear;
 IBServerProperties1.ServerName := '';
 IBServerProperties1.LoginPrompt := false;
 IBServerProperties1.Params.Add('user_name=SYSDBA');
 IBServerProperties1.Params.Add('password=masterkey');
 IBServerProperties1.Active := true;
 IBServerProperties1.Options := [License];
 if IBServerProperties1.Active then begin
  IBServerProperties1.FetchLicenseInfo;
  try
   for i := 0 to High(IBServerProperties1.LicenseInfo.Key) do begin
    ListBox1.Items.Add(IBServerProperties1.LicenseInfo.Key[i]);
   end;
  finally
   IBServerProperties1.Active := false;
  end;
 end;
end;

Looking at the code for IBX "TIBServerProperties.FetchLicenseInfo" in the 
unit IBServices.pas you will see the following:

  ServiceQueryParams := Char(isc_info_svc_get_license) +
                        Char(isc_info_svc_get_licensed_users);
  InternalServiceQuery;

It makes a request for license and number of licensed users.
This gives "request_spb_length=2" and "request_spb='3A' (0x33,0x41)" in the 
call to isc_service_query, but isc_service_query only return a result for 
0x41 (isc_info_svc_get_licensed_users).

Can "isc_service_query" only take one query in IB2009? If so, IBX needs to 
be fixed to split the query into two separate calls?

Kind regards
Magnus Flysjö

Magnus Flysjö wrote:
> 
> Can "isc_service_query" only take one query in IB2009? If so, IBX needs to 
> be fixed to split the query into two separate calls?

since IB 7.5 (I think) the licensing API doesn't work.  Once IB switched to 
sanctuary for lits licensing the server API was never updated to return the 
information that while it knows is now in a different spot.

> 
> Kind regards
> Magnus Flysjö


-- 
Jeff Overcash (TeamB)
       (Please do not email me directly unless  asked. Thank You)
And so I patrol in the valley of the shadow of the tricolor
I must fear evil. For I am but mortal and mortals can only die.
Asking questions, pleading answers from the nameless
faceless watchers that stalk the carpeted  corridors of Whitehall.
              (Fish)

> since IB 7.5 (I think) the licensing API doesn't work.  Once IB switched 
> to
> sanctuary for lits licensing the server API was never updated to return 
> the
> information that while it knows is now in a different spot.

That explains it all then.. To bad the APIGuide isnt updated, it would have 
saved me a lot of time today.
Are there any other ways to distinguish if the user has a trial, full or 
completly lack a valid license?

Also, the source code for TIBServerProperties.FetchLicenseInfo (IBX 
component) should be changed to handle this.
At the moment it only breaks the loop for an "isc_info_flag_end" (127) 
status code.
It should also break on "isc_info_end" (1) to handle this issue correctly, 
since thats what IB sends.

/Magnus

Magnus Flysjö wrote:
>> since IB 7.5 (I think) the licensing API doesn't work.  Once IB switched 
>> to
>> sanctuary for lits licensing the server API was never updated to return 
>> the
>> information that while it knows is now in a different spot.
> 
> That explains it all then.. To bad the APIGuide isnt updated, it would have 
> saved me a lot of time today.
> Are there any other ways to distinguish if the user has a trial, full or 
> completly lack a valid license?
> 
> Also, the source code for TIBServerProperties.FetchLicenseInfo (IBX 
> component) should be changed to handle this.
> At the moment it only breaks the loop for an "isc_info_flag_end" (127) 
> status code.
> It should also break on "isc_info_end" (1) to handle this issue correctly, 
> since thats what IB sends.
> 
> /Magnus

To find out about what license are installed run License Manager. This 
is the best way to go since for InterBase 2007 and later. Note that 
InterBase Manager can show installed user licenses as well.

> To find out about what license are installed run License Manager. This
> is the best way to go since for InterBase 2007 and later. Note that
> InterBase Manager can show installed user licenses as well.

Yes, but I was more into doing something from inside our own application.

The idea is to gather information about the application environment and put 
it into a report that the end user can generate from our application and 
then send to one of our support engineers if something is wrong.

We don’t really want to include and ship the license manager with our 
installer and then also have to instruct the end user on how to manually use 
it.

/Magnus Flysjö

I can see how this is desirable. However, the only thing I can see you 
can get in your application is the Server version. The API to extract 
license information is not public and is not part of the InterBase server.

Note that there is a command line version of license manager. So, it 
should be possible to execute a batch file to extract license 
information. The command line version is not installed on Windows 
because we see no need for it there. It's a java application, so could 
be configured to run on windows. You'd have to get the .jar file from 
the install of another platform. If this is of interest to you let me 
know and try to give you some guidance.

Magnus Flysjö wrote:

> 
> Yes, but I was more into doing something from inside our own application.
> 
> The idea is to gather information about the application environment and put 
> it into a report that the end user can generate from our application and 
> then send to one of our support engineers if something is wrong.

quinn wildman wrote:
> I can see how this is desirable. However, the only thing I can see you 
> can get in your application is the Server version. The API to extract 
> license information is not public and is not part of the InterBase server.

What you don't seem to be getting is that the IB server already knows how to 
extract that for the users otherwise how can it refuse connections based on user 
counts?  I knows the licensing information, they just never updated the service 
API to return this information to clients.  Making the service API read only is 
still important, even if they disable the write portion of the API.

> 
> Note that there is a command line version of license manager. So, it 
> should be possible to execute a batch file to extract license 
> information. The command line version is not installed on Windows 
> because we see no need for it there. It's a java application, so could 
> be configured to run on windows. You'd have to get the .jar file from 
> the install of another platform. If this is of interest to you let me 
> know and try to give you some guidance.

And is worthless from remote locations like a client.  People have complained 
about not being able to read the information for several years now.  No one is 
complaining about not being able to remotely add licenses, only retrieving the 
license information.  All the service API has to do is return the information IT 
ALREADY KNOWS.

-- 
Jeff Overcash (TeamB)
       (Please do not email me directly unless  asked. Thank You)
And so I patrol in the valley of the shadow of the tricolor
I must fear evil. For I am but mortal and mortals can only die.
Asking questions, pleading answers from the nameless
faceless watchers that stalk the carpeted  corridors of Whitehall.
              (Fish)

I'm in complete agreement that this would be a useful feature that the 
server already knows about. It is all a mater of priorities.

Jeff Overcash wrote:
>...All the service API has to do is return the information IT
> ALREADY KNOWS.
>