[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::objectbroker

Title:ObjectBroker - BEA Systems' CORBA
Notice:See note 3 for kits; note 5 for training; note 1134 for releases
Moderator:TLE::PARODId
Created:Tue Jul 11 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1413
Total number of notes:6391

1357.0. "Implementation not found, OBB V2.7-11" by LEMAN::GHAVAMI (Farhad GHAVAMI @GEO) Tue Jan 28 1997 15:28

My collegue is giving the OBB training in Sweden at a customer side. He has some problems
using OBB V2.7-11 on WNT V4.0. The situation is as the following:

	A very simple client server application is used to show development
	steps using OBB. When both client and server are executing on the same
	machine (node), they execute normally and they can communicate.
	But when he tries to distribute them physically, server on one node and 
	client on another, the communication doesn't work and OBB agent cannot find
	the implementation on the server side.
	Strange, because Implementation Manager can see the implementation and evrything
	seems to be Ok.
	The client and server directories on respective node are defined as shared, as well
	as the directory where the context object are defined.
	The students have their specific accounts and a NT doamin has been defined correctly.

Could you please help ! FYI, this application worked without problem on UNIX using OBB V2.6.

When have also encountered another problem on NT and W95 concerning C++ binding. Is it correct
that debugger cannot be used with C++ binding ?

I will apreciate some prompt response from everywhere.


Thanks,
Farhad.
T.RTitleUserPersonal
Name
DateLines
1357.1reformatted .-1SEND::SLAVINTue Jan 28 1997 15:5031
reformatted .-1

My collegue is giving the OBB training in Sweden at a customer side.
He has some problems using OBB V2.7-11 on WNT V4.0. The situation is
as the following: 

	A very simple client server application is used to show
development steps using OBB. When both client and server are executing
on the same machine (node), they execute normally and they can
communicate. But when he tries to distribute them physically, server
on one node and client on another, the communication doesn't work and
OBB agent cannot find the implementation on the server side. Strange,
because Implementation Manager can see the implementation and
evrything seems to be Ok. The client and server directories on
respective node are defined as shared, as well as the directory where
the context object are defined. The students have their specific
accounts and a NT doamin has been defined correctly. 

Could you please help ! FYI, this application worked without problem
on UNIX using OBB V2.6. 

When have also encountered another problem on NT and W95 concerning
C++ binding. Is it correct that debugger cannot be used with C++
binding ? 

I will apreciate some prompt response from everywhere. 


Thanks, Farhad. 

1357.2SEND::SLAVINTue Jan 28 1997 15:554
You should see if notes 2414, 2411, 2355 or 2331 in the
ObjectBroker_development notes files are discussing the same problems
that you are having. 
1357.3REQUE::BOWERPeter Bower, ObjectBrokerWed Jan 29 1997 00:5010
    What error is returned from the call that fails. What is the output
    from the OBB_errortext member function of the SystemException
    class.
    
    Try defining the OBB_TRACE_FLAGS to be RINV and post the output
    from the client side.
    
    Also, check to make sure the OBB_DEFAULT_NODES is set to the correct
    server node.
    
1357.4Use VC++ V4.0SEND::VLATASWARNING: Do not swallow the battery doorWed Jan 29 1997 10:0013
    >> Is it correct that debugger cannot be used with C++
    >> binding ?
       
    What version of Visual C++ are you using?
    
    People have been having trouble with debugging on at least VC++ V4.2,
    and possibly VC++ V4.1. It appears that MS has changed/broke something
    with 4.2 compatability with V4.0 built libraries (OBB is built with
    V4.0).
    
    You should not have any problems building and debugging with VC++ V4.0.
    
    Tony     
1357.5No info yetLEMAN::GHAVAMIFarhad GHAVAMI @GEOThu Jan 30 1997 15:075
Sorry, I cannot find my collegue to have more info.

I will do it asap I can reach him.

Farhad.
1357.6OBB V2.7 & VC++ 4.2 compatibilitySTKAI1::LANKI_TTapio LankiMon Feb 10 1997 13:3220
    We are about to start a pilot with a customer using the
    following toolset:
    
    - NT 4.0 (Server)
    - OBB V2.7-??
    - VC++ 4.2
    
    Note .4 said:  
    >> People have been having trouble with debugging on at
    >> least VC++ V4.2, and possibly VC++ V4.1. It appears 
    >> that MS has changed/broke something with 4.2 compatability 
    >> with V4.0 built libraries (OBB is built with V4.0).
    
    When will OBB V2.7 have support for VC++ 4.2? The customer
    is very reluctant to moving to VC++ 4.0. The debugging
    facilities will certainly be a requirement.
    
    
    Tapio Lanki
    Digital Consulting, Stockholm
1357.7RECV::SLAVINMon Feb 10 1997 14:066
The Bryce release of ObjectBroker will consider new versions of 
operating systems and new versions of layered products such as 
compilers. At this time there is no commitment for Bryce to use a 
specific version of the VC++ compilers. Bryce is to be released 
around fall/winter 1997.
 
1357.8It seems that WINS(TCP/IP) causes problemsHOUBA::BOUCHETTue Feb 11 1997 12:2328
As Farhad mentionned previously, I have got really bad time 
during this OBB training. 

Regarding the Debug problem using C++ I have added a note 
in ObjectBroker Development notes conference 

Regarding the server selection problem, it seems that OBB
has some problem using WINS(TCP/IP). Looking in the log 
file generated using RINV flags, the agent does not 
communicate with the other agent and returns "No server 
selected".

The configuration was the following:

Local Node		Remote Node
----------		-----------
seppc43.is.sandvik.se 	seppc41.is.sandvik.se
			Agent Security Model: opened
			Proxy: *, *, *

When I defined the seppc41.is.sandvik.se in the local 
host file it worked. I have appended two log files:
(1) the one using WINS(TCP/IP) and (2) the one using 
the host file.

Cheers.

Frederic
1357.9Log file with WINS(TCP/IP)HOUBA::BOUCHETTue Feb 11 1997 12:25330
**** Skip Method Selection, OpInfo Created by STUB


**** Implementation Selection


**** Callout to method map resolve rtn.

*** Method map resolve rtn not present. Defaulting.

*** Load Network implementation MicrosoftTCP
	FamilyName<5> <TCPIP>
ImagePath<24> <%OBB_ROOT\lib\trnwsk.dll>
	LibraryName: C:\win32app\obroker\lib\trnwsk.dll
--- WM_CREATE message
--- WinSock implementation WinSock 2.0
---   Min Version: 1.1
---   Max Version: 2.2
---   Max Sockets: 32767
---   Max Datagram: 65467

**** Server Instance Selection

 Selection policy defaulting to advertisements, local_node, default_nodes.

 Context scope default to USER.

 Get Server Selection Node List:

 Possible server selection nodes: <2>
   000. OBB_LOCAL                        = seppc43
   001. OBB_DEFAULT_NODES                = seppc41.is.sandvik.se

 Looking for running server:

 Looking for servers on node seppc43.

*** Load Agent implementation OrbV12
	FamilyName<3> <OBB>
ImagePath<26> <%OBB_ROOT\lib\obbagncl.dll>
	LibraryName: C:\win32app\obroker\lib\obbagncl.dll
OBB__TrnWsckBindWellKnown
--- Connecting to seppc43
---   Port: 62
--- Attempting connect on socket: 100
--- Set asynch socket
---   Socket: 100
---   Message: WSA_READ
---   SocketSetAsynch - Successful

*** Load Authentication implementation Trusted
	FamilyName<3> <TRS>
ImagePath<26> <%OBB_ROOT\lib\obbsectr.dll>
	LibraryName: C:\win32app\obroker\lib\obbsectr.dll
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 564
***    Allocated Buffer : 1887
OBB__TrnWsckSar
--- SAR: Sending message on socket 100
--- Sending on socket 100
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 564
--- Number of bytes actually written 564
--- SAR: Waiting for message on socket 100
--- SAR: Receiving message on socket 100
--- Receiving on socket 100
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 464
--- ioctlsocket buffer available for recv() is 464
--- Recv returned 464
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
OBB__TrnWsckFreeHandle
--- Closing socket: 100
OBB__TrnWsckBind
--- Connecting to seppc43.is.sandvik.se
---   Port: 1046
--- Attempting connect on socket: 108
--- Set asynch socket
---   Socket: 108
---   Message: WSA_READ
---   SocketSetAsynch - Successful

 Server selected from Registry: 7a9561739fe4.02.a4.04.19.88.00.00.00 (seppc43).
*** Request Sent: Synchronous Invoke.
*** Method: 7368090a6e58.02.10.1f.a0.9b.00.00.00.
***    MethodServerClass: 508c0a7f9532.1d.40.33.45.06.70.2e.d9
***    Marshalled Buffer: 724
***    Allocated Buffer : 1925
OBB__TrnWsckSar
--- SAR: Sending message on socket 108
--- Sending on socket 108
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 724
--- Number of bytes actually written 724
--- SAR: Waiting for message on socket 108
--- SAR: Receiving message on socket 108
--- Receiving on socket 108
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 300
--- ioctlsocket buffer available for recv() is 300
--- Recv returned 300
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 

**** Skip Method Selection, OpInfo Created by STUB


**** Implementation Selection

Using default clause.

**** Server Instance Selection

 Selection policy defaulting to advertisements, local_node, default_nodes.

 Context scope default to USER.

 Get Server Selection Node List:

 Possible server selection nodes: <2>
   000. OBB_LOCAL                        = seppc43
   001. OBB_DEFAULT_NODES                = seppc41.is.sandvik.se

 Looking for running server:

 Looking for servers on node seppc43.
OBB__TrnWsckBindWellKnown
--- Connecting to seppc43
---   Port: 62
--- Attempting connect on socket: 144
--- Set asynch socket
---   Socket: 144
---   Message: WSA_READ
---   SocketSetAsynch - Successful
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 564
***    Allocated Buffer : 1887
OBB__TrnWsckSar
--- SAR: Sending message on socket 144
--- Sending on socket 144
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 564
--- Number of bytes actually written 564
--- SAR: Waiting for message on socket 144
--- SAR: Receiving message on socket 144
--- Receiving on socket 144
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 184
--- ioctlsocket buffer available for recv() is 184
--- Recv returned 184
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_INV_METHODFAIL (e), Method execution failed. 
OBB__TrnWsckFreeHandle
--- Closing socket: 144

 Looking for servers on node seppc41.is.sandvik.se.
OBB__TrnWsckBindWellKnown
--- Connecting to seppc41.is.sandvik.se
---   Port: 62

 No server selected.

**** Host Selection for Server Startup

 No startup attributes found, defaulting to selection attributes.

 Possible server startup nodes: <2>
   000. OBB_LOCAL                        = seppc43
   001. OBB_DEFAULT_NODES                = seppc41.is.sandvik.se

 Scanning server startup nodes:

 Node seppc43 matched; selected.
OBB__TrnWsckBindWellKnown
--- Connecting to seppc43
---   Port: 62
--- Attempting connect on socket: 148
--- Set asynch socket
---   Socket: 148
---   Message: WSA_READ
---   SocketSetAsynch - Successful
*** Request Sent: Synchronous Invoke.
*** Method: 65e448eeadd4.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 708
***    Allocated Buffer : 2020
OBB__TrnWsckSar
--- SAR: Sending message on socket 148
--- Sending on socket 148
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 708
--- Number of bytes actually written 708
--- SAR: Waiting for message on socket 148
--- SAR: Receiving message on socket 148
--- Receiving on socket 148
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 88
--- ioctlsocket buffer available for recv() is 88
--- Recv returned 88
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
*** Request Sent: Synchronous Invoke.
*** Method: 65e448efbf44.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 352
***    Allocated Buffer : 1514
OBB__TrnWsckSar
--- SAR: Sending message on socket 148
--- Sending on socket 148
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 352
--- Number of bytes actually written 352
--- SAR: Waiting for message on socket 148
--- SAR: Receiving message on socket 148
--- Receiving on socket 148
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 100
--- ioctlsocket buffer available for recv() is 100
--- Recv returned 100
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
*** Request Sent: Synchronous Invoke.
*** Method: 65e448efbf44.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 352
***    Allocated Buffer : 1514
OBB__TrnWsckSar
--- SAR: Sending message on socket 148
--- Sending on socket 148
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 352
--- Number of bytes actually written 352
--- SAR: Waiting for message on socket 148
--- SAR: Receiving message on socket 148
--- Receiving on socket 148
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 712
--- ioctlsocket buffer available for recv() is 712
--- Recv returned 712
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
OBB__TrnWsckFreeHandle
--- Closing socket: 148
OBB__TrnWsckBind
--- Connecting to seppc43.is.sandvik.se
---   Port: 1088
--- Attempting connect on socket: 64
--- Set asynch socket
---   Socket: 64
---   Message: WSA_READ
---   SocketSetAsynch - Successful
*** Request Sent: Synchronous Invoke.
*** Method: 7a88c2ed7658.02.a4.04.19.88.00.00.00.
***    MethodServerClass: 7a88c2ed7657.02.a4.04.19.88.00.00.00
***    Marshalled Buffer: 548
***    Allocated Buffer : 1787
OBB__TrnWsckSar
--- SAR: Sending message on socket 64
--- Sending on socket 64
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 548
--- Number of bytes actually written 548
--- SAR: Waiting for message on socket 64
--- SAR: Receiving message on socket 64
--- Receiving on socket 64
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 96
--- ioctlsocket buffer available for recv() is 96
--- Recv returned 96
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 

**** Skip Method Selection, OpInfo Created by STUB


**** Implementation Selection


**** Automatic Implementation and Server already Bound, Skipping Implementation Selection

*** Request Sent: Synchronous Invoke.
*** Method: 7a88c2ed7659.02.a4.04.19.88.00.00.00.
***    MethodServerClass: 7a88c2ed7657.02.a4.04.19.88.00.00.00
***    Marshalled Buffer: 512
***    Allocated Buffer : 1725
OBB__TrnWsckSar
--- SAR: Sending message on socket 64
--- Sending on socket 64
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 512
--- Number of bytes actually written 512
--- SAR: Waiting for message on socket 64
--- SAR: Receiving message on socket 64
--- Receiving on socket 64
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 68
--- ioctlsocket buffer available for recv() is 68
--- Recv returned 68
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
OBB__TrnWsckFreeHandle
--- Closing socket: 64
OBB__TrnWsckFreeHandle
--- Closing socket: 108
--- Transport rundown
--- WM_DESTROY message
---   Shutting down transport
---   Shutting down transport
1357.10Log file with local Hosts fileHOUBA::BOUCHETTue Feb 11 1997 12:26271
**** Skip Method Selection, OpInfo Created by STUB


**** Implementation Selection


**** Callout to method map resolve rtn.

*** Method map resolve rtn not present. Defaulting.

*** Load Network implementation MicrosoftTCP
	FamilyName<5> <TCPIP>
ImagePath<24> <%OBB_ROOT\lib\trnwsk.dll>
	LibraryName: C:\win32app\obroker\lib\trnwsk.dll
--- WM_CREATE message
--- WinSock implementation WinSock 2.0
---   Min Version: 1.1
---   Max Version: 2.2
---   Max Sockets: 32767
---   Max Datagram: 65467

**** Server Instance Selection

 Selection policy defaulting to advertisements, local_node, default_nodes.

 Context scope default to USER.

 Get Server Selection Node List:

 Possible server selection nodes: <2>
   000. OBB_LOCAL                        = seppc43
   001. OBB_DEFAULT_NODES                = seppc41.is.sandvik.se

 Looking for running server:

 Looking for servers on node seppc43.

*** Load Agent implementation OrbV12
	FamilyName<3> <OBB>
ImagePath<26> <%OBB_ROOT\lib\obbagncl.dll>
	LibraryName: C:\win32app\obroker\lib\obbagncl.dll
OBB__TrnWsckBindWellKnown
--- Connecting to seppc43
---   Port: 62
--- Attempting connect on socket: 104
--- Set asynch socket
---   Socket: 104
---   Message: WSA_READ
---   SocketSetAsynch - Successful

*** Load Authentication implementation Trusted
	FamilyName<3> <TRS>
ImagePath<26> <%OBB_ROOT\lib\obbsectr.dll>
	LibraryName: C:\win32app\obroker\lib\obbsectr.dll
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 564
***    Allocated Buffer : 1887
OBB__TrnWsckSar
--- SAR: Sending message on socket 104
--- Sending on socket 104
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 564
--- Number of bytes actually written 564
--- SAR: Waiting for message on socket 104
--- SAR: Receiving message on socket 104
--- Receiving on socket 104
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 464
--- ioctlsocket buffer available for recv() is 464
--- Recv returned 464
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
OBB__TrnWsckFreeHandle
--- Closing socket: 104
OBB__TrnWsckBind
--- Connecting to seppc43.is.sandvik.se
---   Port: 1046
--- Attempting connect on socket: 44
--- Set asynch socket
---   Socket: 44
---   Message: WSA_READ
---   SocketSetAsynch - Successful

 Server selected from Registry: 7a9561739fe4.02.a4.04.19.88.00.00.00 (seppc43).
*** Request Sent: Synchronous Invoke.
*** Method: 7368090a6e58.02.10.1f.a0.9b.00.00.00.
***    MethodServerClass: 508c0a7f9532.1d.40.33.45.06.70.2e.d9
***    Marshalled Buffer: 724
***    Allocated Buffer : 1925
OBB__TrnWsckSar
--- SAR: Sending message on socket 44
--- Sending on socket 44
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 724
--- Number of bytes actually written 724
--- SAR: Waiting for message on socket 44
--- SAR: Receiving message on socket 44
--- Receiving on socket 44
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 300
--- ioctlsocket buffer available for recv() is 300
--- Recv returned 300
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 

**** Skip Method Selection, OpInfo Created by STUB


**** Implementation Selection

Using default clause.

**** Server Instance Selection

 Selection policy defaulting to advertisements, local_node, default_nodes.

 Context scope default to USER.

 Get Server Selection Node List:

 Possible server selection nodes: <2>
   000. OBB_LOCAL                        = seppc43
   001. OBB_DEFAULT_NODES                = seppc41.is.sandvik.se

 Looking for running server:

 Looking for servers on node seppc43.
OBB__TrnWsckBindWellKnown
--- Connecting to seppc43
---   Port: 62
--- Attempting connect on socket: 144
--- Set asynch socket
---   Socket: 144
---   Message: WSA_READ
---   SocketSetAsynch - Successful
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 564
***    Allocated Buffer : 1887
OBB__TrnWsckSar
--- SAR: Sending message on socket 144
--- Sending on socket 144
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 564
--- Number of bytes actually written 564
--- SAR: Waiting for message on socket 144
--- SAR: Receiving message on socket 144
--- Receiving on socket 144
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 184
--- ioctlsocket buffer available for recv() is 184
--- Recv returned 184
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_INV_METHODFAIL (e), Method execution failed. 
OBB__TrnWsckFreeHandle
--- Closing socket: 144

 Looking for servers on node seppc41.is.sandvik.se.
OBB__TrnWsckBindWellKnown
--- Connecting to seppc41.is.sandvik.se
---   Port: 62
--- Attempting connect on socket: 124
--- Set asynch socket
---   Socket: 124
---   Message: WSA_READ
---   SocketSetAsynch - Successful
*** Request Sent: Synchronous Invoke.
*** Method: 65e448f20f7c.0c.7e.0b.00.00.00.00.00.
***    MethodServerClass: 65e448ecbd2c.0c.7e.0b.00.00.00.00.00
***    Marshalled Buffer: 576
***    Allocated Buffer : 1901
OBB__TrnWsckSar
--- SAR: Sending message on socket 124
--- Sending on socket 124
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 576
--- Number of bytes actually written 576
--- SAR: Waiting for message on socket 124
--- SAR: Receiving message on socket 124
--- Receiving on socket 124
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 440
--- ioctlsocket buffer available for recv() is 440
--- Recv returned 440
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
OBB__TrnWsckFreeHandle
--- Closing socket: 124
OBB__TrnWsckBind
--- Connecting to seppc41.is.sandvik.se
---   Port: 1043
--- Attempting connect on socket: 128
--- Set asynch socket
---   Socket: 128
---   Message: WSA_READ
---   SocketSetAsynch - Successful

 Server selected from Registry: 7a956891c889.02.a4.04.19.86.00.00.00 (seppc41.is.sandvik.se).
*** Request Sent: Synchronous Invoke.
*** Method: 7a88c2ed7658.02.a4.04.19.88.00.00.00.
***    MethodServerClass: 7a88c2ed7657.02.a4.04.19.88.00.00.00
***    Marshalled Buffer: 560
***    Allocated Buffer : 1801
OBB__TrnWsckSar
--- SAR: Sending message on socket 128
--- Sending on socket 128
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 560
--- Number of bytes actually written 560
--- SAR: Waiting for message on socket 128
--- SAR: Receiving message on socket 128
--- Receiving on socket 128
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 96
--- ioctlsocket buffer available for recv() is 96
--- Recv returned 96
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 

**** Skip Method Selection, OpInfo Created by STUB


**** Implementation Selection


**** Automatic Implementation and Server already Bound, Skipping Implementation Selection

*** Request Sent: Synchronous Invoke.
*** Method: 7a88c2ed7659.02.a4.04.19.88.00.00.00.
***    MethodServerClass: 7a88c2ed7657.02.a4.04.19.88.00.00.00
***    Marshalled Buffer: 524
***    Allocated Buffer : 1739
OBB__TrnWsckSar
--- SAR: Sending message on socket 128
--- Sending on socket 128
--- Socket send buffer size is 4096
--- Sending data on socket - send len is 524
--- Number of bytes actually written 524
--- SAR: Waiting for message on socket 128
--- SAR: Receiving message on socket 128
--- Receiving on socket 128
--- Receiving Header on socket - len is 20
--- Received data - retval is 20
--- Received the transport header
*** In SocketRecvBuf ***--- Receiving data - remaining is 68
--- ioctlsocket buffer available for recv() is 68
--- Recv returned 68
***    Transport Status: OBB_SUCCESS (s), Successful completion. 
***    Operation Status: OBB_SUCCESS (s), Successful completion. 
OBB__TrnWsckFreeHandle
--- Closing socket: 128
OBB__TrnWsckFreeHandle
--- Closing socket: 44
--- Transport rundown
--- WM_DESTROY message
---   Shutting down transport
---   Shutting down transport
1357.11REQUE::BOWERPeter Bower, ObjectBrokerSun Feb 23 1997 10:515
    OBB calls gethostbyname to get the host name address information.
    It appears to not be working on your system with WINS. Try running
    the OBB network tester between the two nodes and see if the network
    tester displays more information from the underlying transport
    error.