I have a copy of 24x7 Scheduler with a valid site license where the
Serial # shows up as expected in the help window. I set up the
system to accept COM commands over TCP on port 1096. When I do an
OpenSession, I get a 'LastError' of "Evaluation period expired".
Does a site license not cover COM calls or is there another problem?

-- thanks

Site license covers all components. Where do you get "Evaluation period expired" message, on the client or on the server? Does the client have site license key? Do you actually pass that key value in OpenSession parameters?

: I have a copy of 24x7 Scheduler with a valid site license where the
: Serial # shows up as expected in the help window. I set up the
: system to accept COM commands over TCP on port 1096. When I do an
: OpenSession, I get a 'LastError' of "Evaluation period expired".
: Does a site license not cover COM calls or is there another problem?

: -- thanks

: Site license covers all components. Where do you get "Evaluation period
: expired" message, on the client or on the server? Does the client
: have site license key? Do you actually pass that key value in OpenSession
: parameters?

This is exactly what is being done - this code is running on the same
physical machine as the 24x7 instance. Note that I have obscured the actual key
in this sample but in the real case, the code passed is the same as the
one that shows on the help window.

/* Create 24x7 Object */
var Remote_24x7 = new ActiveXObject("w24x7ASP.jsRemote24x7");

/* Start new Session */
var RC = Remote_24x7.OpenSession("24x7Service","XXXXX-XXXXXXX-XXXXX","WinSock","LocalHost","1096","",-1);

if(RC != 1)
{

WScript.Echo(Remote_24x7.LastError);

WScript.Quit(1);
}

RC = Remote_24x7.GetJobList(0);

var JobsList = Remote_24x7.ipStringBuffer;

var JOBS_FILE = "24x7Jobs.txt";

/* New Object, New File */
var fso = new ActiveXObject("Scripting.FileSystemObject");
fso.CreateTextFile(JOBS_FILE,true);

//----- open the new file
var fo = fso.OpenTextFile(JOBS_FILE,8,true);

/* Write the list */
fo.Write(JobsList);
fo.Close();

This problem is a pretty serious reason not to continue using this product
if there is no further information about it or fix coming forward soon. The
code I showed earlier worked at one point so I know it can work. Do you have
any further information as to the cause of this issue?

You have a problem with the installation or use a non-site license key. Did you do the suggested checks in the registry? Did you verify the license key is actually a site license key?

: This problem is a pretty serious reason not to continue using this product
: if there is no further information about it or fix coming forward soon. The
: code I showed earlier worked at one point so I know it can work. Do you have
: any further information as to the cause of this issue?