[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

3903.0. "FCS and some more error messages.." by WAYOUT::TALBOT (Trevor Talbot) Mon Feb 21 1994 09:50

Hi,


	Can somone please explain what the following 2 errors mean and what needs
to be done to prevent them? thanks.

1) %OAFC-E-SRVPVNOTSUPPORT, The local or remote server does not support this higher
   version protocol.
	Message: SrvConnectProcess; the network partner is running higher version
	         protocol

and

2) %MCC-E-FATAL_FW, fatal framework condition: !AS
    message: OafcGsmAttachJacket; Couldn't delete attached doc

These have stopped after re-starting FCS..but I expect them to return in the future
and would like to have an answer ready for the customer.

-Trev
T.RTitleUserPersonal
Name		DateLines
3903.1IOSG::STANDAGEMon Feb 21 1994 11:4245
    
    Hi Trev,
    
    I'll have a go...
    
    
>>1) %OAFC-E-SRVPVNOTSUPPORT, The local or remote server does not support
    >> this version protocol.
>>   Message: SrvConnectProcess; the network partner is running higher version
>>	         protocol
    
    This could come up a number of ways. I'd need to know:
    
    a) What version server is on their local system.
    b) Have they got distributed IOS systems, and what version are they ?
    c) Do they use TeamLinks, and if so what version ?
    
    
>>2) %MCC-E-FATAL_FW, fatal framework condition: !AS
>>    message: OafcGsmAttachJacket; Couldn't delete attached doc

    This is an error from the MCC threads package. An error occurred which
    resulted in a document attachment not being deleted, this can obviously
    occur from a number of scenarios. It is also not easy to fix, as the
    problem occurs with another product the FCS interoperates with. The
    only good news on this is that we have transitioned the FCS to use
    DECthreads instead of MCC threads, which is reportedly a much more
    robust threads package which is also supported. With any luck this
    server should be seen in a PFR.
    
    I have seen %MCC-E-FATAL_FW, reported hundreds of times one after the
    other in the log file, which is not good. If this is an isolated single
    message, then I don't think there are any side effects on the server in
    general, and it should continue to run ok.
    
    
    Sorry, not a complete answer, but I hope it helps,
    Kevin.
    
    
    
    Kevin.
3903.2WAYOUT::TALBOTTrevor TalbotTue Feb 22 1994 15:239
Hi kev,


	The customer just told me they have mupa on 1 machine and not on others,
this probably explains the nosupport error in 1). He was happy to close and apply
MUPA everywhere!!


Thanks.
3903.3phew!IOSG::STANDAGETue Feb 22 1994 16:0514
    
    Trev,
    
    Yes, having MUPA servers connecting to non MUPA servers will certainly
    cause this error to be logged. Actually, this is probably one of the
    only things that will work when those two servers talk to each other
    :-)
    
    Yup, all systems should be upgraded to MUPA - just how the release
    notes say  :-)
    
    Kevin.