[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

3989.0. "FCS Error Messages" by LARVAE::JORDAN (Chris Jordan, TSE - Technology Services, End-User Computing) Wed Mar 16 1994 11:20

The File Cabinet Server is giving these messages..... Is this important??
    (Once it starts going, the log file expands at a VERY fast rate!).
    
    Environment:
    ALL-IN-1 V3.0a (MUPA and TLC) on one machine.
    ALL-IN-1 V3.0-1 on the other (where these messages come from).
    The V3.0A is accessed by TeamLinks V2.0 users. One of these people 
    decided to also put the V3.0-1 system into his TeamLinks logon...... 
    Normally (2days) this gave no problems..... but on the third day this 
    is what we got:
    
    
11-MAR-1994 15:06:14.23  Server: PSOV12::"73="  
Error: %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

11-MAR-1994 15:35:05.56  Server: PSOV12::"73="  
Error: %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

T.RTitleUserPersonal
Name
DateLines
3989.1IOSG::STANDAGEWed Mar 16 1994 12:4421
    
    Chris,
    
    It would appear that the V3.0-1 server is brokering to the V3.0A
    server, or vise versa. Have they got the Distributed Sharing Option ?  
    
    I could envisage this happening if they have remote drawers added to
    their filecabinet. If this is the case, when you connect from TeamLinks
    the server makes an individual connection to all the drawers in your
    filecabinet before listing them for the first time. Therefore, you
    would see this message a number of times !
    
    The workaround ? - well to successfully operate in a distributed
    environment with MUPA, all your other systems must have MUPA, this is
    documented in the release notes.
    
    
    Kevin.