The virtual machine could not be added. The virtual machine configuration could not be added. A configuration with this name already exists.
2008-01-31 17:43
621 查看
The virtual machine could not be added. The virtual machine configuration could not be added. A configuration with this name already exists.
使用Microsoft Virtual Server 2005 R2,当添加新的虚拟机配置文件时会碰到这样的错误提示.这个大致发生的原因是:没有使用管理界面的移除虚拟机选项进行虚拟机的移除,而是直接删除了虚拟机文件.当再次添加相同名称的虚拟机时,就会发生.
解决办法是到C:\Documents and Settings\All Users\Application Data\Microsoft\Virtual Server\Virtual Machines 删除掉该虚拟机名称的Shortcut,这样再次添加的时候就不会出问题.要注意这个可能是隐藏文件,因此你需要设置显示隐藏文件和文件夹才可以找到.
每次添加虚拟机配置文件的时候都会添加一个这样的Shortcut,所以如果手动删除虚拟机的话,除了要删除配置文件,还要过来删除下这个.
使用Microsoft Virtual Server 2005 R2,当添加新的虚拟机配置文件时会碰到这样的错误提示.这个大致发生的原因是:没有使用管理界面的移除虚拟机选项进行虚拟机的移除,而是直接删除了虚拟机文件.当再次添加相同名称的虚拟机时,就会发生.
解决办法是到C:\Documents and Settings\All Users\Application Data\Microsoft\Virtual Server\Virtual Machines 删除掉该虚拟机名称的Shortcut,这样再次添加的时候就不会出问题.要注意这个可能是隐藏文件,因此你需要设置显示隐藏文件和文件夹才可以找到.
每次添加虚拟机配置文件的时候都会添加一个这样的Shortcut,所以如果手动删除虚拟机的话,除了要删除配置文件,还要过来删除下这个.
相关文章推荐
- This platform could not be created because a solution platform of the same name already exists解决方法
- This platform could not be created because a solution platform of the same name already exists.
- ES报错:Can not be imported as a dangling index as index with same name already exists in cluster me
- WCF分布式开发常见错误(23):This could be due to the fact that the server certificate is not configured properly with HTTP.SYS
- A server with the specified hostname could not be found.
- ES报错:Can not be imported as a dangling index as index with same name already exists in cluster me
- 【iOS系列】-A server with the specified hostname could not be found.问题解决
- The source control provider associated with this soluation could not be found.
- this install package could not be opened. verify that the package exists and that you can ac
- 【解决方法】this install package could not be opened. verify that the package exists and that you can ac
- WARNING: The host '$hostname' could not be looked up with resolveip.
- MBean with the same name could not be unregisted
- TroubleShooting The virtual machine could not be started because the hypervisor is not running
- GetModuleFileName False failed with error 126 (The specified module could not be found)
- “A configuration with this name already exists” error in eclipse run configurations
- MBean with the same name could not be unregisted
- The virtual machine could not be started because the hypervisor is not running
- A 'Android Application' configuration with this name already exists
- Eclipse 出现A configuration with this name already exists问题解决方法
- Eclipse中提示A 'Java Application' configuration with this name already exists解决方案