27 August 2013

SCVMM 2012 SP1 library issues and fixes

System Center Virtual machine Manager 2012 SP1 includes support for Windows Server 2012 and Hyper-
V 3.0  Logically you would think that VMM 2012 is now fully supported and supporting of the Windows Server 2012 technology stack, but you would be wrong.

Error 2905
When adding an additional VMM Library server hosted on Windows Server 2012 you may run  into the following issue:


Error (2905)
The file name, folder name, or volume label syntax \\<ServerName>\CommonLibrary\ApplicationFrameworks\SAV_x64_en-US_4.9.37.2003.cr\SCVMMCRTag.cr is incorrect on the <ServerName> server.
The filename, directory name, or volume label syntax is incorrect (0x8007007B)

The alternate error popup has the following wording.

The file name, folder name, or volume label syntax \\<ServerName>\CommonLibrary\ISOs\en_windows_7_ultimate_x64_dvd_x15-65922.iso is incorrect on the <ServerName> server.
Ensure that the path name does not contain the characters (\ / : * ? " < > | ), and then try the operation again. ID: 2905 Details: The filename, directory name, or volume label syntax is incorrect (0x8007007B)

If you look at the Change Tracking section of the task that terminated with the error you will notice that some of the information is actually being pulled through.



If you look at the actual file structure you would also notice that the default resources are actually successfully created.



Resolution
It took a while to figure this one out but turns out that the VMM Library must be on NTFS.  If you attempted to use ReFS it will simply not work, you would get the errors above.



Error / Information 10804
When moving your default VMM library to another server you start seeing warning during library refresh tasks.



Information (10804)
Unable to import \\<servername>\VMM-LIB\VHD's\Blank Disk - Large.vhdx because of a syntax error in the file.
The file structure does contain the vhdx files listed in the alert but they are not visible when checking the library.

Resolution
This error occurs when VHDX files are located in a library share that is hosted on an OS older that Windows Server 2012.  Since the library is populated by resources that the OS indexes it has to be able to interpret the new VHDX format which only came with 2012.


Error - Virtualization platform does not support shared ISO Images
Despite having set up ISO sharing correctly,  this happens when you deploy a new virtual machine. At creation you attempt to add an existing ISO to the hardware configuration and you "Share image file instead of copying it."  Copying the file works fine and does not generate any errors.



The two error messages that can manifest are:

When deploying to a host:


Virtualization platform on host <servername> does not support shared DVD ISO images.

When deploying to a cloud:


The virtual machine workload <VM Name> cannot be deployed to the hardware supporting cloud <Cloud Name>  Contact the cloud administrator and provide Task ID.................


Resolution
Shared images cannot be attached during deployment.  To use a shared images you need to attach it to the VM after the initial deployment.



No comments:

Post a Comment