Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Exchange 2000 Server or Exchange Server 2003 ExIFS may not start after ExIFS is manually stopped


View products that this article applies to.

This article was previously published under Q246216

↑ Back to the top


Symptoms

A component known as the Exchange Installable File System (ExIFS) is included with Microsoft Exchange Server 2003 and with Microsoft Exchange 2000 Server. The ExIFS runs as a hidden service on an Exchange server and allows file-level access to various items within a private or public information store. A manifestation of the ExIFS service is a drive that maps as M listed in Explorer on the Exchange server.

Because the ExIFS runs as a hidden service, it is not visible in the Services applet within the Administrative Tools program menu. However, you can still issue a net stop or a net start command to start or stop the ExIFS service. Stopping the ExIFS service does not cause the drive that maps to M to disappear.

When you stop the ExIFS service and then attempt to restart it, you receive the following error message:
System error 2 has occurred.

The system cannot find the file specified.

↑ Back to the top


Workaround

This workaround applies to Exchange 2000 servers. The workaround also applies to Exchange 2003 servers that have the M drive enabled. By default, the M drive is disabled.

If you manually stop the ExIFS service by issuing a net stop command, you must issue the following command before restarting the ExIFS:
subst m: /d
Then the ExIFS service can be started by issuing the net start command as shown below:
net start exifs

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: KB246216, kbpending, kberrmsg, kbbug

↑ Back to the top

Article Info
Article ID : 246216
Revision : 5
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 386