[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

2286.0. "Can't register node4 Mcc error = %SYSTEM-F-SHUT, not accepting connects" by SCOBIE::JCAROW (OK...We'll try it...) Thu Feb 06 1992 13:02

    We are upgrading our MCC to a model 3100-76 and reinstalled all
    software.  We are reregistering ou nodes and ran into this problem...
    
    MVDSP1 >  manage/enterprise
    DECmcc (V1.1.0)
    
    MCC> register node4 mcvtla .dna_node.mcvtla synonym mcvtla
    %MCC-W-ARGSYNTAX, syntax error in argument .
    MCC> register node4 .dna_node.mcvtla synonym mcvtla
    
    Node4 DSP_NS:.dna_node.mcvtla
    AT  6-FEB-1992 12:23:06
    
    The requested operation cannot be completed
                MCC Unhandled Service Reply = Error occurred while
    accessing the
                                              entity.
                                  MCC Error = %SYSTEM-F-SHUT, remote node
    no longer
                                              accepting connects
    MCC> register node4 .dna_node.mvdev2 synonym mvdev2
    
    Node4 DSP_NS:.dna_node.mvdev2
    AT  6-FEB-1992 12:25:23
    
    The requested operation cannot be completed
                MCC Unhandled Service Reply = Access control information
    invalid at
                                              Node
    MCC>
    	We can set host, etc. to this node...what object are we using here?
    Is the problem in ther MCC? or something about the node we are trying
    to register?
    
    FYI we are VMS V5.4 and MCC version 1.1.0
    
    
    any suggestions?
    
    Thanks in advance,
    
    John Carow
T.RTitleUserPersonal
Name		DateLines
2286.1Check NML protections/proxies, etcTOOK::MCPHERSONScientific progress goes 'Boink!'Thu Feb 06 1992 13:0811
Almost looks like 2 different problems.  Is this a cluster?

I belilve the 'not accepting connects' means someone has done an "NCP SET EXEC
STATE SHUT" on the remote node...

The 'access control' problem appears to be some sort of protection issue with
the NML object.  (this is the object the AM is speaking to.)  You will need to
resolve that at the remote end, either via changing protections, adding proxy
or passing Username/passord with the directive.

	/doug
2286.2you have a typo in the commandTOOK::CALLANDERMCC = My Constant CompanionThu Feb 20 1992 19:469
    first problem was simply a typo, you have a space between
    the first string of the dna name and the .
    
    register node4 name .name.name.name syno name
                       ^
    
    I didn't look close enough at the second half to 
    see what that was.