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

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

948.0. "Multi Line Window: Failed to connect to ENS" by 48862::WILLAY () Tue Aug 29 1995 09:00

Hy,

   I have a strange problem with Multi-Line Window and ENS. When CM start, I get
on my display workstation a multi-line window with the message:
   "Multi-Line Window has failed to connect to Event Notification Services."
   Then, on the node where CM is installed, the process Multi-Line  001 remains
in LEF state and a new one is created. I receive a new window with the same
message, and the new process ,Multi-Line  002, takes the same way, hang in LEF
state. And so on...

    When I start CM on interactive mode (Console event, with set display)
eveything works fine, Multi Line start normally...


    Logs files are empty, no security message... any clue is welcome.
    (OpenVMS 6.2, CM 1.6-110, transport for remote windows is Tcp/Ip)

Thanks a lot
Thierry Willay - GPS - Evry/France
T.RTitleUserPersonal
Name		DateLines
948.1CSC32::BUTTERWORTHGun Control is a steady hand.Tue Aug 29 1995 12:376
    This sounds like Geerts problem where the first 1 or two eventlists
    fail to start correctly. Do you get any other events in either the
    first or second multiline?
    
    REgs,
      Dan
948.2Only the same48862::WILLAYTue Aug 29 1995 13:107
 re:-1	

On the first, second, third, ... always the same message:
	Failed to connect...

 Regards,
 Thierry
948.3Nobody on the line ?48862::WILLAYMon Sep 04 1995 08:404
 No news, bad news or only nobody on the line ?

 Thierry
948.4ZENDIA::DBIGELOWInnovate, Integrate, EvaporateTue Sep 05 1995 11:0017
    Thierry,
    
        We have no news to report at the moment. As a workaround, I would
    suggest that you put the startup of the event list window into a
    command file and then spawn the command procedure. Within the command
    procedure, you can also specify the display. The spawn command would
    look something like:
    
        SPAWN/NOWAIT/INPUT=NL:/NOTIFY/OUTPUT=SYS$LOGIN:ELIST.LOG @command_proc

    or
    
        SPAWN/NOWAIT/INPUT=NL:/NOTIFY/OUTPUT=SYS$LOGIN:ELIST.LOG console event
    This problem is on the bug list.
    
    Dave
948.5CSC32::BUTTERWORTHGun Control is a steady hand.Wed Sep 06 1995 12:339
    I do not have a solution for you. We know there is a problem and it is
    a very difficult one to track down. There is some kind of timing issue
    here that is causing some data structure corruption within the code.
    The same block of memory is being used, deallocated and then reused.
    The only thing that prevents an ACCVIO is the fact that the block is
    still mapped. 
    
    Regs,
      Dan
948.6Thanks48862::WILLAYWed Sep 06 1995 13:506
Many thanks. 
You can't imagine how it's good to know that your problem is being
processed  ;-)

May the force be with you,
Thierry