PC Win: Mail Fails on Wollongong TCP/IP and LAN Manager 2.2Last reviewed: October 23, 1995Article ID: Q111374 |
The information in this article applies to:
SYMPTOMSWhen you use Wollongong TCP/IP with Microsoft LAN Manager version 2.2, the Mail Windows client may fail when you access the Mail message file. Error conditions include:
CAUSEThis problem is caused by Wollongong's TCP, which does not support the full command set of Microsoft TCP. When a session is broken, Wollongong TCP does not inform the workstation, causing Mail to exhibit the behavior above. When you run LAN Manager version 2.2, the opportunistic locking function (called Oplocks and designed to enhance performance by caching server data on the workstation) disconnects Mail's session. Mail normally opens the Mail message file twice (for STORE.DLL and MSSFS.DLL). When one of the DLLs writes to the Mail message file, the server issues an Oplock Broken command that is supposed to inform all users of the file to flush their buffers and re-read the server file. This is to ensure that the cached data on the workstation is current. If the re-read operation does not occur within a time-out period (definable in the server heuristics) then the connection is broken by the server to ensure the data on the workstation is valid. When this happens to Mail, one of the two DLLs (the one that hasn't written to the Mail message file yet) still attempts to use the (now invalid) session. The DLL fails and one of the error conditions above occurs.
RESOLUTIONDo one of the following to eliminate the problems:
|
Additional reference words: 3.00 3.20
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |