Resolving UNC Path Issue in Application Configuration Manager (ConfigurationManager 2.3.0.9)
When creating an application using the wizard in Application Configuration Manager (ConfigurationManager 2.3.0.9), you may encounter a "Specify valid UNC path" dialog, which appears when you browse for files or manually enter a file path. This article will provide a detailed explanation of UNC paths and how to resolve this issue.
Understanding UNC Paths
UNC (Universal Naming Convention) paths are used to identify resources on a network. A UNC path has the following format:
For example:
Resolving the "Specify valid UNC path" Issue
To resolve the "Specify valid UNC path" issue, you can try the following steps:
- Check the file path for any typos or errors.
- Make sure that the file path is a valid UNC path.
- Verify that the file path is accessible from the computer where ConfigurationManager is installed.
- Check if the file is currently in use by another application or user.
- Make sure that the file path does not contain any special characters or spaces.
- Try mapping the network share to a drive letter and use the mapped drive letter instead of the UNC path.
Code Example
Here's an example of how to map a network share to a drive letter using PowerShell:
References
This article provided a detailed explanation of UNC paths and how to resolve the "Specify valid UNC path" issue in ConfigurationManager 2.3.0.9. By following the steps outlined in this article, you should be able to successfully create an application using the wizard in ConfigurationManager.