The MNSFileShare path is invalid
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2007-03-27
Microsoft Exchange Server 2007 setup cannot continue because the MNSFileShare path is invalid.
The MNSFileShare value must be set to a string value that contains the Universal Naming Convention (UNC) path of a file share that is external to the cluster such as \\server\sharename.
To address this issue, provide a value for the MNSFileShare property that is a valid UNC path.
For more information about how to configure the MNSFileShare property, see "How to Configure the File Share Witness" (http://go.microsoft.com/fwlink/?LinkId=78278).