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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3517.0. "Error attempting to create notify" by SEDSWS::MALLOY () Thu Aug 06 1992 19:17

	Error message when starting up Iconic Map
	------------------------------------------

  
" Error attempting to create notify  request for domain BAE "

"An error has occurred while determining  the contenst of the domain "
 
  (Domain BAE is the top domain)

 I  can not find this error message in the  DECmcc messages manual


Assume that notification service  is complaining about one or many entities in
 the domains as I have only one alarms rule now.

	The question is 
		which of 17 OSI is it
		 or 
		which circuit is it ???????


Switch notification disable/enable also causes this message.

	Notification is in fact disable as the only alarm rules when fired is 
  not changing the  colour of the node icon.
    

	It would be nice if the notify state (file menu) indicate that the
notification service failed to start.  	 

    Also would it possible to sink all messages to logfile in mcc_commom:
    
     say   	errors_for_session_'start_date'.err
    
    As in the real world customer report problems normally 30 minutes or
    later after the problem has occurred.
    This way a logfile would be available.
                           
    		Gary Malloy
    
	This relates to Note entry  3507


		Gary Malloy
T.RTitleUserPersonal
Name		DateLines
3517.1log file for notification fmSEDSWS::MALLOYFri Aug 07 1992 19:0882
    
    
 Here is a extract from  the log  of Notification service active
	 
   (logical mcc_notification_fm_log ffff)

    Hopefully this may help.

Notification FM; ** GETEVENT return values ** 

Notification FM; Return CVR: 
%MCC-S-SPECIALIZED_EXC, success with management module-specific exception reply
Notification FM; Out Entity: 
        entity [0] wild = NOT_WILD class = 8 id = 1 type = 5
        instance = �....X...�Os......BaeNet..
        %XAA000400055800111AFA4F7394000A0001064261654E65740000
        entity [1] wild = NOT_WILD class = 88 id = 1 type = 5
        instance = �....X...�Os......mcc..KI12NA..
        %XAA000400055800111AFA4F7394000F0001036D636301064B4931324E410000
Notification FM; Time Stamp: 

Dump of MCC time descriptor:
mcc_w_maxstrlen = 16
mcc_b_dtype     = DSC_K_DTYPE_T
mcc_b_class     = DSC_K_CLASS_D
mcc_w_curlen    = 16
mcc_b_flags     = 0
mcc_b_ver       = 1
mcc_l_id        = 0
mcc_a_link      = 0
mcc_l_dt        = MCC_K_DT_BIN_ABS_TIM
mcc_a_pointer   = 
    bin_utc      =  7-AUG-1992 17:57:55.68
    time          = 01CB7465C50FB1DC
    inacc         = FFFFFFFFFFFFFFFF
    tdf_minutes   = 60
Notification FM; Out_p     : 

[  207 ] ( 
    [  209 ]     aa 00 04 00 05 58 00 11 1a fa 4f 73 94 00 0f 00 01 02 63 72 
    01 07 62 61 65 67 61 74 65 00 00 
    )
Notification FM; State Rtn : MCC_K_HANDLE_FIRST 
Notification FM; ** NOTIFY return values ** 
Notification FM; Return CVR -- call_params: 
%MCC-S-SPECIALIZED_EXC, success with management module-specific exception reply
Notification FM; Out Entity -- call_params: 
        entity [0] wild = NOT_WILD class = 8 id = 1 type = 5
        instance = �....X...�Os......BaeNet..
        %XAA000400055800111AFA4F7394000A0001064261654E65740000
Notification FM; Time Stamp -- call_params: 

Dump of MCC time descriptor:
mcc_w_maxstrlen = 16
mcc_b_dtype     = DSC_K_DTYPE_T
mcc_b_class     = DSC_K_CLASS_D
mcc_w_curlen    = 16
mcc_b_flags     = 0
mcc_b_ver       = 1
mcc_l_id        = 0
mcc_a_link      = 0
mcc_l_dt        = MCC_K_DT_BIN_ABS_TIM
mcc_a_pointer   = 
    bin_utc      =  7-AUG-1992 17:57:56.18
    time          = 01CB7465C55BFD1C
    inacc         = FFFFFFFFFFFFFFFF
    tdf_minutes   = 60
Notification FM; Out_p      -- call_params: 

[  12 ] ( 
    )
Notification FM; State Rtn  -- call_params: MCC_K_HANDLE_FIRST 



			Gary Malloy

			dtn 7844 3308

I do have the whole log file if need.
3517.2deregistered entities in the domainTOOK::S_KOHoot mon!Wed Aug 12 1992 10:3517
    
    
    There are two exceptions in the log file.  The first exception
    is being reported by the Domain FM indicating that it detected a
    dergistered domain member.  This can occur when someone deregisters
    an entity, but does not have privileges to update domains that it
    may appear in.
    
    Notification considers this an error, and returns the 2nd exception you
    see in the log file indicating an error occurred while determining the
    contents of the domain.
    
    The domain needs to have the deregistered entities deleted from it
    before notification can proceed.  
    
    It sounds like you have namespace problems perhaps with access setup,
    or configuration.
3517.3Dns causing the problemSEDSWS::MALLOYThu Aug 13 1992 08:5013
    This problem was caused by a problem with DNS V1.1.
    
    The clearinghouse were holding different information.
    
    When DECmcc was setting up the domains, it was having problems reading
    from DNS .( Conflicting data attributes).
    
    Switched to Local DNS (MIR) all ok now.
    
    Customer is now rebuilding DNS.
    
    
    		Gary Malloy