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

Conference tuxedo::dce-products

Title:DCE Product Information
Notice:Kit Info - See 2.*-4.*
Moderator:TUXEDO::MAZZAFERRO
Created:Fri Jun 26 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:10003

2210.0. "DCE with swiftalliance" by DAIVC::DEDI_B () Tue Apr 08 1997 01:34

    Hi,
    
    I have a customer who are using Swiftalliance (banking application).
    The problem seems a little bit funny, if the machine is started up on
    08.00 am, the problem will happen on about 16.00 pm.
    
    The main configuration are :
    - Alphaserver 400 4/233
    - Memory 128 MB
    - X.25 adapter (PBXDI-AB)
    - RACAL MILGO RMD 3222 (modem 9600 bps V2.4)
    - DCE layered product (dce130)
    
    The problem is the machine will hang (screen blank) but if the machine 
    is shutdown and restarted up the condition will be ok.
    The appeared message are :
    
    call_csys_find_server1_dce_rpc()
    cnfg_find_server3_dce()
    warning : swiftalliance instance will not be accessible from window
    clients
    serious : bs_watch:0:1040 (osf1/cbs_cnfg_rpc.c:cnfg_get_cnfg:809)
    operating system error for system call
    csys_find_server3_dce_rpc(...)
    (rpc_x_comm_failure)
    serioud : bs_watch:0:100 (osf1/cbs_isys_rpc.c:isys_monitor:1021)
    unexpected return code:isys_monitor
    (the server with full-pname /bs_isys: WHYSUR has either crashed or not
    been started correctly)
    
    Hopefully somebody could gives some clue.
    
    Regards,
    
    Dedi
    
    
    
        
T.RTitleUserPersonal
Name
DateLines
2210.1probably not DCETUXEDO::ZEEThere you go.Tue Apr 08 1997 12:439
>    (rpc_x_comm_failure)

I assume this should be rpc_s_comm_failure, which means that RPC could
not communicate with the remote server with full-pname /bs_isys: WHYSUR.
This indicates a network connectivity problem, and at the time this
error occurs, you should see if you can ping or telnet to that remote
system (if you are using TCP or UDP).

--Roger