A little of the wall, but I notice konfabulator (widget.yahoo.com) offers the ability to use com objects.. the createObject call for w24x7ASP.jsRemote24x7 works properly, but my call to OpenSession seems to fail, and the docuentation is a little fuzzy.

The username is a local admin for the box in question?
The password is my serial number in xxxxx-xxxxxxx-xxxxx format ?

All the properties of the com object seem to be in place, I just think my opensession call is a little malformed.

Don't use license key as a paswrod. This idea came from version 2 and isn ot supported anymore.

Which error do you get when calling OpenSession? Do you have a separate license for the COM client?

: A little of the wall, but I notice konfabulator (widget.yahoo.com) offers the
: ability to use com objects.. the createObject call for
: w24x7ASP.jsRemote24x7 works properly, but my call to OpenSession seems to
: fail, and the docuentation is a little fuzzy.

: The username is a local admin for the box in question?
: The password is my serial number in xxxxx-xxxxxxx-xxxxx format ?

: All the properties of the com object seem to be in place, I just think my
: opensession call is a little malformed.

: Don't use license key as a paswrod. This idea came from version 2 and isn ot
: supported anymore.

: Which error do you get when calling OpenSession? Do you have a separate
: license for the COM client?

Using the konfab js engine is a little unusual and requires me to say :

var obj = COM.createObject("w24x7ASP.jsRemote24x7");

doing a 'dump' of this into in the konfab debugger shows the object is created properly (i see all the properties as listed in the 24x7 com documentation)

When i try openSession, I get a Error Calling OpenSession() from the try / catch block. This is coming from the konfab engine.

Curiously, when i create a test vbs file with the exact same OpenSession line (using the serial # as the pwd) i get a proper connect.. and this is using the latest 24x7 version. The documentation for this latest version also tells me to use the serial #, is there a different version of the docs ?

Please post fragment of your code where you do the OpenSession call. You can replace any senstive data with xxx or other symbols.

: Using the konfab js engine is a little unusual and requires me to say : var
: obj = COM.createObject("w24x7ASP.jsRemote24x7");

: doing a 'dump' of this into in the konfab debugger shows the object is
: created properly (i see all the properties as listed in the 24x7 com
: documentation)

: When i try openSession, I get a Error Calling OpenSession() from the try /
: catch block. This is coming from the konfab engine.

: Curiously, when i create a test vbs file with the exact same OpenSession line
: (using the serial # as the pwd) i get a proper connect.. and this is using
: the latest 24x7 version. The documentation for this latest version also
: tells me to use the serial #, is there a different version of the docs ?

: Please post fragment of your code where you do the OpenSession call. You can
: replace any senstive data with xxx or other symbols.

var obj = COM.createObject("w24x7ASP.jsRemote24x7");

try{

obj.OpenSession( "xxxx", "yyyyy", "WinSock","zz.zz.zz.zz", "10095", "", 0);

}

catch(e)

{

log(e);

}

This is thw widget code, which should be fully javascript compliant. "log" is a widget function, and the COM.createObject call is widget code, but in viewing the 'obj' object, all the read only properties are there.. so, it is correctly calling the proper object
This outputs : Error calling OpenSession()

yyyy is currently my user password, but it has also worked in my vbs test code when I used the serial number. I have yet to have stand alone javascript code working in a .js file

yes, 10095 is the port i am using

According to the docs the last parameter should be true/false boolean value and you are passing a number.

: var obj = COM.createObject("w24x7ASP.jsRemote24x7");

: try{

: obj.OpenSession( "xxxx", "yyyyy",
: "WinSock","zz.zz.zz.zz", "10095",
: "", 0);

: }

: catch(e)

: {

: log(e);

: }

: This is thw widget code, which should be fully javascript compliant.
: "log" is a widget function, and the COM.createObject call is
: widget code, but in viewing the 'obj' object, all the read only properties
: are there.. so, it is correctly calling the proper object
: This outputs : Error calling OpenSession()

: yyyy is currently my user password, but it has also worked in my vbs test
: code when I used the serial number. I have yet to have stand alone
: javascript code working in a .js file

: yes, 10095 is the port i am using

: According to the docs the last parameter should be true/false boolean value
: and you are passing a number.

That was the result of testing .. setting it to true / false gives the same result.

Try the following script:

1. Save this as test.js

// create COM object
var obj = WScript.CreateObject("w24x7ASP.jsRemote24x7");
// open session
obj.OpenSession( "john_doe", "password", "WinSock", "LocalHost", "10095", "", true);
// ... do something here ...
// close session and destroy COM object
delete obj

2. From DOS prompt run 'start test.js' on the computer where you have 24x7. Run it from the 24x7 installation directory.

3. If it fails, check 24x7 is set to run in the server mode and the port is 10095. If not, correct your 24x7 settings.

4. If it still fails reinstall 24x7 to ensure you have all files from the same version and there are no old hangouts from old versions.

5. Let us know what you get there.

: That was the result of testing .. setting it to true / false gives the same
: result.

hmm,, this works. I wonder why the js engine for the widget is stopping me from doing an opensession. let me take it to them.

: Try the following script: 1. Save this as test.js

: // create COM object
: var obj = WScript.CreateObject("w24x7ASP.jsRemote24x7");
: // open session
: obj.OpenSession( "john_doe", "password",
: "WinSock", "LocalHost", "10095",
: "", true);
: // ... do something here ...
: // close session and destroy COM object
: delete obj

: 2. From DOS prompt run 'start test.js' on the computer where you have 24x7.
: Run it from the 24x7 installation directory.

: 3. If it fails, check 24x7 is set to run in the server mode and the port is
: 10095. If not, correct your 24x7 settings.

: 4. If it still fails reinstall 24x7 to ensure you have all files from the
: same version and there are no old hangouts from old versions.

: 5. Let us know what you get there.