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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

4014.0. "FCS gives DSL-E-INVSPEC ?" by KERNEL::LOAT (Stop throwing those bloody spears!) Tue Mar 22 1994 20:30

    
    VMS 5.5 ALL-IN-1 3.0
    
    When attempting to edit of refile a document from a shared drawer, the
    users see a message which says
    
    "A system error has occurred. Refer to extended status for system error
    code."
    
    Looking in the FCS log file, it has got the following error in it:
    
    "%DSL-E-INVSPEC, invalid component specification."
    
    All the FCS parameters have been checked, and look okay. CHANNELCNT
    should be a problem. SM MFC MS SAI shows that CHANNELCNT is set to 275
    but the number of channels is only 17. They can reproduce the problem
    with only one user logged on, so I don't think it's quota problem.
    
    I can't find any mention of this error message anywhere else, so anyone
    got any ideas what could cause this DSL error message?
    
    Steve.
    
T.RTitleUserPersonal
Name
DateLines
4014.1Some questions and thoughts.IOSG::STANDAGETue Mar 22 1994 20:5029
    
    Steve,
    
    The only time I have seen "%DSL-E-INVSPEC, invalid component
    specification" is when the server attempts to start up over TCP/IP and
    there is no UCX installed.
    
    OK, some questions :
    
    a) What version of IOS are you running (MUPA ?)
    b) Is the server running as DECnet only ?
    c) Are all users effected ?
    d) Does this problem occur in one shared drawer, or does it happen to
       all of them ?
    e) Does stopping/restarting the server make any difference ?
    
    If you have installed MUPA, check to ensure OA$DSL$SHR.EXE exists in
    SYS$COMMON:[SYSLIB}, and that you haven't got any old
    OAFC$SERVER_LINK.COMs hiding in the OA$BUILD search list. If you have
    the MUP and are still linking the server against DSL$SHR.EXE I could
    well expect this error to occur.
    
    Just a few thoughts, sorry I can't come back with a more specific
    answer right now...
    
    Kevin.
    
    
     
4014.2KERNEL::LOATStop throwing those bloody spears!Wed Mar 23 1994 20:2824
    
    Some answers.
    
    a) 3.0 (no patches)
    
    b) DECnet only.
    
    c) Not sure. There are only three shared drawers on the systenm and
    they belong to the ALL-IN-1 manager.
    
    d) All of the ones they've got (only three of them)
    
    e) No.
    
    The wierd thing is that they've got over 60 systems, and everything is
    okay, apart from on two of them. The only thing which is a bit wierd is
    that both of these nodes have a leading 0 (zero) in the nodename. Is
    this valid? Any problems known with this?
    
    This is an absolute show-stopper for them, so a quick reply is
    appreciated.
    
    Steve.
    
4014.30:: has a special meaningAIMTEC::WICKS_AAtlanta's Most (In)famous WelshmanTue Mar 29 1994 08:2114
    Steve,
    
    I think kev has dossed off on his hols again so I hope you weren't
    waiting for him. obviously I don't have a node that starts with a 0
    but that could be a key given that 0:: means this node under normal
    circumstances. Presumably they've just upgraded to v3.0? i don't
    have the FCS sources to hand as the machine they were on is in bits
    and pieces somewhere between its old home and its new resting place 
    but I wonder if they is possible some underlying assumption in the
    FCS code that assumes 0***:: means 0:: - have you logged an SPR yet?
    
    regards,
    
    Andrew.d.wicks
4014.4ICF fixes it!KERNEL::LOATStop throwing those bloody spears!Tue Apr 05 1994 14:0410
    
    Hi Andy.
    
    In all the recent rushing around with this problem, I forgot to update
    this note.
    
    I escalated this, and an ICF has been produced for the problem (ICF35).
    
    Steve.
    
4014.5And the STARS article is?? (:==:)AIMTEC::WICKS_AAtlanta's Most (In)famous WelshmanTue Apr 05 1994 19:528
    Steve,
    
    Yes I noticed (I get the CLD reports) I assume that you will be writing
    a STARS article to explain this to the great CSC public worldwide.
    
    Regards,
    
    Andrew.D.Wicks