SoftTree Technologies SoftTree Technologies
Technical Support Forums
RegisterSearchFAQMemberlistUsergroupsLog in
24x7 COM Component

 
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite View previous topic
View next topic
24x7 COM Component
Author Message
Jocio Morais



Joined: 17 Jul 2002
Posts: 10

Post 24x7 COM Component Reply with quote

Hi,

I try to use a 24x7 COM component for 24x7 (version 2.4.15) with IIS for testing some web jobs, but when i try to connect the follow erros apears.

OpenSession Error 50

How can i fix this problem to keep try this COM component ?

Best Regards

Fri Jul 19, 2002 10:51 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7948

Post Re: 24x7 COM Component Reply with quote

The complete error message should say "OpenSession Error 50 - Distributed service error." in some cases following by additional diagnostic information.

You can turn on the tracing flag in the OpenSession to get the trace of communication calls. Please let us know what you get in the trace.

: Hi,

: I try to use a 24x7 COM component for 24x7 (version 2.4.15) with IIS for
: testing some web jobs, but when i try to connect the follow erros apears.

: OpenSession Error 50

: How can i fix this problem to keep try this COM component ?

: Best Regards

Fri Jul 19, 2002 11:14 am View user's profile Send private message
Jocio Morais



Joined: 17 Jul 2002
Posts: 10

Post Re: 24x7 COM Component Reply with quote

Here is the trace log :

SMI AddRef SMI_TRACE(0101B760) refCount(2)
DPB AddRef DPB_Connection(0101B8E8) refCount(1)
DPB01 Connection(0101B8E8): ConnectToServer : application(10099), location(), driver(WinSock). ... (00000000)
SMI07 Connection(0101BAA8): Connect: computerName(), serviceName(10099), driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='10099'
SMI Property: __Location=''
SMI Property: __Options=''
SMI AddRef SMI_CONNECTION(0101BAA8) refCount(3)
SMI AddRef SMI_TRACE(0101B760) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI02 Connection(0101BAA8): ERROR OCCURRED: Distributed Communications Error: Connect call failed with error WSAEADDRNOTAVAIL, (220) (8004200D)
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(0101BAA8) refCount(2)
SMI Release SMI_TRACE(0101B760) refCount(2)
SMI07 Connection(0101BAA8): Connect: computerName(), serviceName(10099), driverName(WinSock). FAILED (8004200D)
DPB01 Connection(0101B8E8): ConnectToServer : application(10099), location(), driver(WinSock). FAILED (8004200D)
DPB Release DPB_Connection(0101B8E8) refCount(0)
SMI08 Connection(0101BAA8): Disconnect: ... (00000000)
SMI08 Connection(0101BAA8): Disconnect: SUCCEEDED (00000000)
SMI Release SMI_CONNECTION(0101BAA8) refCount(1)
SMI Release SMI_CONNECTION(0101BAA8) refCount(0)
SMI Release SMI_TRACE(0101B760) refCount(1)
SMI Release SMI_TRACE(0101B760) refCount(0)

Fri Jul 19, 2002 11:22 am View user's profile Send private message
Jocio Morais



Joined: 17 Jul 2002
Posts: 10

Post Re: 24x7 COM Component Reply with quote

New Trace Log, (with option in OpenSession, is true)

Starting distributed service...
SMI AddRef SMI_TRACE(0101B7C0) refCount(2)
DPB AddRef DPB_Connection(0101B948) refCount(1)
DPB01 Connection(0101B948): ConnectToServer : application(10099), location(), dr
iver(WinSock). ... (00000000)
SMI07 Connection(0101BB08): Connect: computerName(), serviceName(10099), driverN
ame(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='10099'
SMI Property: __Location=''
SMI Property: __Options=''
SMI AddRef SMI_CONNECTION(0101BB08) refCount(3)
SMI AddRef SMI_TRACE(0101B7C0) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI02 Connection(0101BB08): ERROR OCCURRED: Distributed Communications Error: Co
nnect call failed with error WSAEADDRNOTAVAIL, (220) (8004200D)
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(0101BB08) refCount(2)
SMI Release SMI_TRACE(0101B7C0) refCount(2)
SMI07 Connection(0101BB08): Connect: computerName(), serviceName(10099), driverN
ame(WinSock). FAILED (8004200D)
DPB01 Connection(0101B948): ConnectToServer : application(10099), location(), dr
iver(WinSock). FAILED (8004200D)
DPB Release DPB_Connection(0101B948) refCount(0)
SMI08 Connection(0101BB08): Disconnect: ... (00000000)
SMI08 Connection(0101BB08): Disconnect: SUCCEEDED (00000000)
SMI Release SMI_CONNECTION(0101BB08) refCount(1)
SMI Release SMI_CONNECTION(0101BB08) refCount(0)
SMI Release SMI_TRACE(0101B7C0) refCount(1)
SMI Release SMI_TRACE(0101B7C0) refCount(0)
SMI10 Listener (0101BD28): Start Listening: computerName(), serviceName(10099),
driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='10099'
SMI Property: __Options='TimeOut=180'
SMI Property: TimeOut='180'
SMI AddRef SMI_TRACE(0101B7C0) refCount(2)
WSD11 AddRef: RefCount for listener object = 1
SMI10 Listener (0101BD28): Start Listening: computerName(), serviceName(10099),
driverName(WinSock). SUCCEEDED (00000000)
WSD11 AddRef: RefCount for listener object = 2
WSD11 AddRef: RefCount for listener object = 3
WSD11 AddRef: RefCount for listener object = 4
WSD11 AddRef: RefCount for listener object = 5
DPB30 Listener (0101B770): Start Listening : application(10099), location(), dr
iver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(2526), total(421888), alloc(298675)
, free(111627)
DPB56 Memory Proc Common : count(920), total(86016), alloc(51704), free(29196)
SMI AddRef SMI_LISTENER(0101BD28) refCount(2)
SMI AddRef SMI_TRACE(0101B7C0) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(0101B7C0) refCount(4)
SMI AddRef SMI_TRACE(0101B7C0) refCount(5)
SMI AddRef SMI_LISTENER(0101BD28) refCount(3)
SMI Release SMI_LISTENER(0101BD28) refCount(2)
SMI AddRef SMI_CONNECTION(0101BB08) refCount(3)
SMI Release SMI_CONNECTION(0101BB08) refCount(2)
SMI12 Listener (0101BD28): Open Connection: (0101BB08). numConnections(1), SUCC
EEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
WSD07 ReadHeader: Proto = 24576, Len = 210
SMI01 Connection(0101BB08): Create Message: (01013DB0), initial size 210 bytes
DPB AddRef DPB_SESSION_SERVICE(0101C768) refCount(2)
DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0). SUC
CEEDED (00000000)
DPB20 Connection(0101BB08): ClientConnect : Jociom_ic(LISITSTAS) userId([Unkno
wn]), connectString(), sessionId(FFFFFFFF). ... (00000000)
SMI AddRef SMI_LISTENER(0101BD28) refCount(3)
SMI16 Listener (0101BD28): Create Session: (0101E068). SUCCEEDED (00000000)
DPB41 : Use Session : sessionId(16900200). SUCCEEDED (0000
0000)
SMI Release SMI_LISTENER(0101BD28) refCount(2)
SMI AddRef SMI_CONNECTION(0101BB08) refCount(3)
DPB AddRef DPB_Connection(0101DD38) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(0101C768) refCount(3)
DPB20 Connection(0101BB08): ClientConnect : Jociom_ic(LISITSTAS) userId([Unkno
wn]), connectString(), sessionId(0101E068). SUCCEEDED (00000000)
SMI01 Connection(0101BB08): Create Message: (0101E188), initial size 0 bytes
DPB Release DPB_SESSION_SERVICE(0101C768) refCount(2)
SMI03 Connection(0101BB08): Send Reply Message: (0101E188) sequenceNumber(83) As
ynchronous. ... (00000000)
SMI06 Connection(0101BB08): Process request Message: (01013DB0) serviceId(0), se
quenceNumber(83). SUCCEEDED (00000000)
WSD08 Send: result = 0
SMI03 Connection(0101BB08): Send Reply Message: (0101E188) sequenceNumber(83) As
ynchronous. SUCCEEDED (00000000)
SMI08 Connection(0101BB08): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD06 ReadHeader: Received disconnect code = FF
WSD04 Release: RefCount for connection object = 2
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(0101BB08): Disconnect: SUCCEEDED (00000000)
SMI Release SMI_CONNECTION(0101BB08) refCount(2)
DPB Release DPB_SESSION_SERVICE(0101C768) refCount(1)
SMI Release SMI_TRACE(0101B7C0) refCount(4)
SMI Release SMI_CONNECTION(0101BB08) refCount(1)
DPB56 Memory Proc Common : count(1004), total(86016), alloc(57338), free(23419)

DPB Release DPB_SESSION_SERVICE(0101C768) refCount(0)
DPB Release DPB_Connection(0101DD38) refCount(0)
SMI Release SMI_CONNECTION(0101BB08) refCount(0)
SMI Release SMI_TRACE(0101B7C0) refCount(3)
SMI Release SMI_LISTENER(0101BD28) refCount(1)
SMI Release SMI_TRACE(0101B7C0) refCount(2)


Fri Jul 19, 2002 11:29 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7948

Post Re: 24x7 COM Component Reply with quote

You forgot to specify the server computer name for the ServerLocation parameter. If 24x7 runs on the same computer either specify real computer name or it's IP address or specify LocalHost. Don't leave the ServerLocation parameter empty.

: New Trace Log, (with option in OpenSession, is true)

: Starting distributed service...
: SMI AddRef SMI_TRACE(0101B7C0) refCount(2)
: DPB AddRef DPB_Connection(0101B948) refCount(1)
: DPB01 Connection(0101B948): ConnectToServer : application(10099), location(),
: dr
: iver(WinSock). ... (00000000)
: SMI07 Connection(0101BB08): Connect: computerName(), serviceName(10099),
: driverN
: ame(WinSock). ... (00000000)
: SMI Property: __DriverName='WinSock'
: SMI Property: __ApplicationName='10099'
: SMI Property: __Location=''
: SMI Property: __Options=''
: SMI AddRef SMI_CONNECTION(0101BB08) refCount(3)
: SMI AddRef SMI_TRACE(0101B7C0) refCount(3)
: WSD04 AddRef: RefCount for connection object = 1
: SMI02 Connection(0101BB08): ERROR OCCURRED: Distributed Communications Error:
: Co
: nnect call failed with error WSAEADDRNOTAVAIL, (220) (8004200D)
: WSD04 Release: RefCount for connection object = 1
: SMI Release SMI_CONNECTION(0101BB08) refCount(2)
: SMI Release SMI_TRACE(0101B7C0) refCount(2)
: SMI07 Connection(0101BB08): Connect: computerName(), serviceName(10099),
: driverN
: ame(WinSock). FAILED (8004200D)
: DPB01 Connection(0101B948): ConnectToServer : application(10099), location(),
: dr
: iver(WinSock). FAILED (8004200D)
: DPB Release DPB_Connection(0101B948) refCount(0)
: SMI08 Connection(0101BB08): Disconnect: ... (00000000)
: SMI08 Connection(0101BB08): Disconnect: SUCCEEDED (00000000)
: SMI Release SMI_CONNECTION(0101BB08) refCount(1)
: SMI Release SMI_CONNECTION(0101BB08) refCount(0)
: SMI Release SMI_TRACE(0101B7C0) refCount(1)
: SMI Release SMI_TRACE(0101B7C0) refCount(0)
: SMI10 Listener (0101BD28): Start Listening: computerName(),
: serviceName(10099),
: driverName(WinSock). ... (00000000)
: SMI Property: __DriverName='WinSock'
: SMI Property: __ApplicationName='10099'
: SMI Property: __Options='TimeOut=180'
: SMI Property: TimeOut='180'
: SMI AddRef SMI_TRACE(0101B7C0) refCount(2)
: WSD11 AddRef: RefCount for listener object = 1
: SMI10 Listener (0101BD28): Start Listening: computerName(),
: serviceName(10099),
: driverName(WinSock). SUCCEEDED (00000000)
: WSD11 AddRef: RefCount for listener object = 2
: WSD11 AddRef: RefCount for listener object = 3
: WSD11 AddRef: RefCount for listener object = 4
: WSD11 AddRef: RefCount for listener object = 5
: DPB30 Listener (0101B770): Start Listening : application(10099), location(),
: dr
: iver(WinSock). FAILED (80004005)
: DPB55 Memory Session : (00000000) count(2526), total(421888), alloc(298675)
: , free(111627)
: DPB56 Memory Proc Common : count(920), total(86016), alloc(51704),
: free(29196)
: SMI AddRef SMI_LISTENER(0101BD28) refCount(2)
: SMI AddRef SMI_TRACE(0101B7C0) refCount(3)
: WSD04 AddRef: RefCount for connection object = 1
: SMI AddRef SMI_TRACE(0101B7C0) refCount(4)
: SMI AddRef SMI_TRACE(0101B7C0) refCount(5)
: SMI AddRef SMI_LISTENER(0101BD28) refCount(3)
: SMI Release SMI_LISTENER(0101BD28) refCount(2)
: SMI AddRef SMI_CONNECTION(0101BB08) refCount(3)
: SMI Release SMI_CONNECTION(0101BB08) refCount(2)
: SMI12 Listener (0101BD28): Open Connection: (0101BB08). numConnections(1),
: SUCC
: EEDED (00000000)
: WSD04 AddRef: RefCount for connection object = 2
: WSD07 ReadHeader: Proto = 24576, Len = 210
: SMI01 Connection(0101BB08): Create Message: (01013DB0), initial size 210
: bytes
: DPB AddRef DPB_SESSION_SERVICE(0101C768) refCount(2)
: DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0).
: SUC
: CEEDED (00000000)
: DPB20 Connection(0101BB08): ClientConnect : Jociom_ic(LISITSTAS)
: userId([Unkno
: wn]), connectString(), sessionId(FFFFFFFF). ... (00000000)
: SMI AddRef SMI_LISTENER(0101BD28) refCount(3)
: SMI16 Listener (0101BD28): Create Session: (0101E068). SUCCEEDED (00000000)
: DPB41 : Use Session : sessionId(16900200). SUCCEEDED (0000
: 0000)
: SMI Release SMI_LISTENER(0101BD28) refCount(2)
: SMI AddRef SMI_CONNECTION(0101BB08) refCount(3)
: DPB AddRef DPB_Connection(0101DD38) refCount(1)
: DPB AddRef DPB_SESSION_SERVICE(0101C768) refCount(3)
: DPB20 Connection(0101BB08): ClientConnect : Jociom_ic(LISITSTAS)
: userId([Unkno
: wn]), connectString(), sessionId(0101E068). SUCCEEDED (00000000)
: SMI01 Connection(0101BB08): Create Message: (0101E188), initial size 0 bytes
: DPB Release DPB_SESSION_SERVICE(0101C768) refCount(2)
: SMI03 Connection(0101BB08): Send Reply Message: (0101E188) sequenceNumber(83)
: As
: ynchronous. ... (00000000)
: SMI06 Connection(0101BB08): Process request Message: (01013DB0) serviceId(0),
: se
: quenceNumber(83). SUCCEEDED (00000000)
: WSD08 Send: result = 0
: SMI03 Connection(0101BB08): Send Reply Message: (0101E188) sequenceNumber(83)
: As
: ynchronous. SUCCEEDED (00000000)
: SMI08 Connection(0101BB08): Disconnect: ... (00000000)
: WSD09 SendDisconnect: result = 0
: WSD06 ReadHeader: Received disconnect code = FF
: WSD04 Release: RefCount for connection object = 2
: WSD04 Release: RefCount for connection object = 2
: SMI08 Connection(0101BB08): Disconnect: SUCCEEDED (00000000)
: SMI Release SMI_CONNECTION(0101BB08) refCount(2)
: DPB Release DPB_SESSION_SERVICE(0101C768) refCount(1)
: SMI Release SMI_TRACE(0101B7C0) refCount(4)
: SMI Release SMI_CONNECTION(0101BB08) refCount(1)
: DPB56 Memory Proc Common : count(1004), total(86016), alloc(57338),
: free(23419)

: DPB Release DPB_SESSION_SERVICE(0101C768) refCount(0)
: DPB Release DPB_Connection(0101DD38) refCount(0)
: SMI Release SMI_CONNECTION(0101BB08) refCount(0)
: SMI Release SMI_TRACE(0101B7C0) refCount(3)
: SMI Release SMI_LISTENER(0101BD28) refCount(1)
: SMI Release SMI_TRACE(0101B7C0) refCount(2)

Fri Jul 19, 2002 11:34 am View user's profile Send private message
Jocio Morais



Joined: 17 Jul 2002
Posts: 10

Post Re: 24x7 COM Component Reply with quote

: You forgot to specify the server computer name for the ServerLocation
: parameter. If 24x7 runs on the same computer either specify real computer
: name or it's IP address or specify LocalHost. Don't leave the
: ServerLocation parameter empty.

Hi,

I specify the server computer name in ServerLocation parameter, and the problem dont fix. The same erros still happened, and now open a notepad document (licence.txt) in the same time when de erros is appears.

Have any ideia ?

Fri Jul 19, 2002 12:13 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7948

Post Re: 24x7 COM Component Reply with quote

Popping up notepad window with the license.txt occurs only if a license violation is detected. Running 24x7 COM or 24x7 Java interface requires a separate license and license key. Using the same key leads to the connection being denied.

Running it on a web server requires a site license.

: Hi,

: I specify the server computer name in ServerLocation parameter, and the
: problem dont fix. The same erros still happened, and now open a notepad
: document (licence.txt) in the same time when de erros is appears.

: Have any ideia ?

Fri Jul 19, 2002 12:18 pm View user's profile Send private message
Jocio Morais



Joined: 17 Jul 2002
Posts: 10

Post Re: 24x7 COM Component Reply with quote

How can i find price list of this COM product, i try to see in site but i dont find any information about. Is it possible to test a trial version of this product ?????

Fri Jul 19, 2002 12:24 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7948

Post Re: 24x7 COM Component Reply with quote

The price differs for different versions. Site license price for version 3 is $3900. Single installation license price for version 3 is $270. It is $3600 and $240 for version 2 respectively.

To play with a trial version use your registry editor to create "HKEY_LOCAL_MACHINE\SOFTWARE\SoftTree Technologies, Inc.\24x7 Scheduler\3.0\RC" key. Under that key create new string value "Serial" and enter 00000-00000 for the value.

If you use version 2 replace 3.0 with 2.0 in the key name.

: How can i find price list of this COM product, i try to see in site but i
: dont find any information about. Is it possible to test a trial version of
: this product ?????

Fri Jul 19, 2002 12:35 pm View user's profile Send private message
Display posts from previous:    
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite All times are GMT - 4 Hours
Page 1 of 1

 
Jump to: 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

 

Powered by phpBB © 2001, 2005 phpBB Group
Design by Freestyle XL / Flowers Online.