XCLN: Newprof Fails to Create a Profile

Last reviewed: February 3, 1998
Article ID: Q158708
The information in this article applies to:
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0

SYMPTOMS

Newprof.exe fails to create a profile if the command line path to the profile descriptor file (.PRF) contains a space.

WORKAROUND

To work around this problem:

  1. Find the 16-bit directory name for the directory with a space in its name. To find the 16-bit name, view the directory in File Manager.

  2. Substitute the 16-bit directory name for the entry with a space after the -P switch.

    For example, instead of using the command line

          C:\EXCHANGE\NEWPROF.EXE -P c:\test newprof\default.prf
    

    use:

          C:\EXCHANGE\NEWPROF.EXE -P c:\testne~1\default.prf
    

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The workaround described above is usually not a viable option if you are using the variable %USERNAME% in a Windows NT login script to signify the directory where the profile descriptor file is located and the path to the user's home directory contains a space.


Additional query words: kbfaq Profgen newprof profile stfedit setup editor
Keywords : XCLN kbusage
Version : 4.0 5.0
Platform : WINDOWS


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.

Last reviewed: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.