[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

840.0. "Unknown error triggered from action routine" by KERNEL::HAWLEYI (It looks like a haggis with a head!) Fri Jun 23 1995 12:43

    
    Hi all,
    
    I have a customer that is attempting to set up an action routine.
    When it is triggered he receives an error in CONSOLE_NOTIFY_OUTPUT.LOG:
    
    CONSOLE$ENS_DAEMON: eventport_error Callback
        errno_val : 3520480
    	     msg1 : Failed to create local socket  CONSOLE_EVT_firewall____001
             msg2 : Unknown error code :  3520480
    
    Does anyone know what this unknown error equates to?
    
    Thanks in advance,
    
    Ian.
    
T.RTitleUserPersonal
Name
DateLines
840.1:-)KERNEL::HAWLEYIIt looks like a haggis with a head!Fri Jun 23 1995 12:445
    
    Oh, I forgot to mention that I got him to setup CONSOLE$DEBUG in order
    to get this, but I guess you probably realise that!
    
    Ian.
840.2OPG::PHILIPAnd through the square window...Fri Jun 23 1995 13:486
Ian,

  What version of PCM?

Cheers,
Phil
840.3dohKERNEL::HAWLEYIIt looks like a haggis with a head!Fri Jun 23 1995 15:275
    
    Sorry, 1.5 of PCM, 6.1 of OpenVMS.
    I'll forget my head next!
    
    Ian.
840.4OPG::PHILIPAnd through the square window...Fri Jun 23 1995 16:3712
Ian,

  I dont know what errno_val 3520480, its one of those error messages
  we werent able to either trap or fix in V1.5 so it could be caused
  by any number of things. You say the customer has V1.5, but have they
  installed the MUP? Alternatively, you could get V1.6 to them and see
  if their problem goes away (I suspect it will), the IPC mechanism we
  use (from which you got the error message) has been totally rewritten
  for V1.6 and so the problem should no longer occur.

Cheers,
Phil