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

Conference iosg::mapi_driver_for_all-in-1_office_server

Title:MAPI Driver for ALL-IN-1 and Office Server
Notice:See Note 6.19 for V1 SSB Kit Pointer
Moderator:IOSG::PYE
Created:Fri Nov 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:125
Total number of notes:506

123.0. "Logon failed. Communication error." by WOODY::FABBRI () Tue May 13 1997 16:35

	Hi, 

A customer has installed Mapi Driver for ALL-IN-1 and it was working fine for 2
days.
Then he has changed his VMS password and his NT (Version 4.0) password.
Since this, each time he starts Exchange he is no more able to open his ALL-IN-1
Message Store Drawer.

He gets the error message "ALL-IN-1 logon failed, communication error".

There is a lot of informations in the RDASL.LOG , and specially 2 lines:

 LogonFCS returns
 Logon returns 80040

Could somebody says me if 80040 is an error message and where I can find the
interpretation.

I can send the RDASLK.LOG file if needed.

Thanks

Michel
T.RTitleUserPersonal
Name		DateLines
123.1Logon returnsWOODY::FABBRITue May 13 1997 16:509
	Sorry, in the .0 I have made a mistake.

The correct lines in RDASL.log file are:

LogonFCS returns 80040113 MAPI_E_USER_CANCEL
Logon returns 80040113 MAPI_E_USER_CANCEL


Michel
123.2IOSG::MAURICEBack in the eggWed May 14 1997 09:2124
    Hi,
    
    Communication error usually indicates a problem with the Server. So can
    you check:
    
    1. The File Cabinet Server is running OK on the node the user
       specified.
    
    2. If the user is on a Cluster get the user to try on all the nodes
       that the File Cabinet Server is running on. 
    
    3. Can the user logon from another PC?
    
    4. If the user has TeamLinks installed, can the user connect using 
       TeamLinks?
    
    5. Are there are any error messages in the File Cabinet Server error
       & log files?
    
    6. Can you try having the File Cabinet Server restarted?
    
    Cheers
    
    Stuart
123.3WOODY::FABBRIWed May 14 1997 14:4023
	Hello Stuart,


I have checked with the customer.

1. The File Cabinet Server is running OK 

2. The user is on a cluster (2 nodes) but there is only 1 AIDA Server so it is 	
   not possible to connect on the second node.

3. The user as the same problem from another PC. (He has tested only with 2     
   pc's).

4. The user does not have Teamlinks installed.

5. There are no error messages in the File Cabinet Server error/log files.

6. The File Cabinet Server is restarted every night for backup.


Any other idea ??

Michel
123.4Stale passwordsIOSG::jonpc1.reo.dec.com::alffa::ButtonWed May 14 1997 16:286
Michel,

Does the user cache his password, or does he enter it each time that he starts 
Exchange?

Jon
123.5WOODY::FABBRIWed May 14 1997 18:2111
He does not use the password cache.

I don't think that it's a password problem because the error message comes when
he tries to open his ALL-IN-1 drawer when he is in Exchange and not when typing
the password.

Also we have checked if he his connected on the AIDA server with SM/MAS/MSS/ISC
and he is.


Michel
123.6IOSG::MAURICEBack in the eggThu May 15 1997 11:3022
    Hi,
    
    To gain access to the File Cabinet Server a TCP/IP connection must be
    made. The File Cabinet Server shows which port number it is running on
    from the ALL-IN-1 menu SM MFC MFS. By default the number is 7373, but
    may be changed.
    
    The client software gets the port number from the Windows registry. Run
    up REGEDIT and find the key:
    
    HKEY_LOCAL_MACHINE\SOFTWARE\DigitalEquipmentCorporation\RDASL\TCPIP
    
    In this key there should be a value for OA$FCS, which should show as
    being the port number as you found from the ALL-IN-1 menu. Note that
    the display shows the hexadecimal equivalent, but also shows the
    decimal value in brackets, e.g. 0x00001ccd (7373).
    
    So could you please check the port numbers match OK.
    
    Cheers
    
    Stuart
123.7IOSG::MAURICEBack in the eggThu May 15 1997 12:4710
    Hi,
    
    Another thing to check is the user's drawer. From ALL-IN-1 type FC DRM
    and select the MAIN drawer. Type R to read the drawer and check that
    the system field shows either the Cluster name or the Node name on
    which the File Cabinet Server is running.
    
    Cheers
    
    Stuart
123.8It works...WOODY::FABBRIThu May 15 1997 15:0211
Thank you Stuart, 

The problem was that in the cluster of two nodes only one File Cabinet Server
had the 7373 port configured and the system field of the user's MAIN drawer was
declared on the other node.
We have configured the two File Cabinet Servers with TCP/IP and now it works
fine.

Thanks again

Michel