DOCUMENT:Q140462  04-NOV-1999  [pcmail]
TITLE   :PC DirSync: LISTDS.EXE Does Not Reset REQCONF.GLB
PRODUCT :Microsoft Mail For PC Networks
PROD/VER:WINDOWS:3.5
OPER/SYS:
KEYWORDS:

======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Mail for PC Networks, version 3.5 
-------------------------------------------------------------------------------

SYMPTOMS
========

When you use the LISTDS.EXE utility against a Directory Synchronization
(Dir-Sync) requestor, it will not reset all the pointers in the REQCONF.GLB on
the requestor as specified.

STATUS
======

Microsoft has confirmed this to be a problem in versions 3.5 of Microsoft Mail
for PC Networks. We are researching this problem and will post new information
here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION
================

The REQCONF.GLB file contains four file pointers: SRVTRANS.GLB, USRTRANS.GLB,
GWTRANS.GLB, and NMETRANS.GLB. These pointers are not reset properly by running
LISTDS.EXE with the following command:

   ListDS -d -r -z <NET> <PO> <Password>

where:
-d is the network drive.
-r indicates the requestor.
-z resets REQCONF.GLB to a zero state.

Additional query words: 3.50

======================================================================
Keywords          :  
Technology        : kbMailSearch kbZNotKeyword3 kbMailPCN350
Version           : WINDOWS:3.5

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1999.