Error 0x80070005 of Hyper-V when exporting

[N I C K]

Hi friends, I just installed virtual server 2005 R2 server on my 2008.
The installation was completed successfully without any error message.
However, once I run the website administration I came across an error message saying :

• HTTP Error 401.2 - Unauthorized
  You are not authorized to view this page because the header invalid credentials.

Module IIS Web Core
Notification AuthenticateRequest
Manager StaticFile
Error Code 0x80070005

Have you managed to find a solution? I installed virtual server being the server admin. Also I have observed same error code at friend's place while exporting Hyper-V VMs over the Network.!!

[Pratim]

Virtual Server 2005 is administered through a Web interface. This interface is created automatically during installation. It is physically stored in the installation directory of the product but is accessible through a virtual directory in IIS. True to the security philosophy introduced with Vista, the installation of IIS is reduced to an absolute minimum. It is then the administrator to select components to be installed on the machine. Installing Virtual Server 2005 R2 VISTA is ultimately the same as Windows XP. However, the configuration of components related products like IIS and the firewall is greatly impacted by this new edition of Windows since these two components have completely reworked.

[Damien25]

Here are the steps for creating a rule authorizing the remote control of virtual machines and the Web interface of Virtual Server :
I

1. n the MMC console tree, click on "Inbound Rules"
2. In the right pane, click "New Rule ..."
3. In the Rule Wizard, select "Port" to create a rule allowing some input port
4. On the "Protocol and Ports" add ports 80, 443 and 5900 in TCP (the first two correspond to the Web interface and the last customer VMRC)
5. In the "Action", select "Allow the connection"
6. Double click on "Next", give a name to the rule, and confirm!

[NGV BalaKrishna]

Between the release of Service Pack 1 for Windows Vista, the Windows Server 2008 Service Pack 3 finally Windows XP, an update of our favorite software virtualization seemed necessary. It is therefore timely since Microsoft offers us nothing but a SP1 for VPC 2007 and an update for VS 2005 R2 SP1. For that you will have to Update virtualization software.

[shivendra]

Can you tell me from where comes your VM? It seems that the VM from a previous installation of Hyper-V. To migrate VMs from one facility to another, it must use the import / export of Hyper-V. In addition, the system state (save state) are not compatible with Hyper-V R1 and R2. I would advice you to do the following things, to fix that error :

1. Remove the VMs to Hyper-V (do not remove the disc).
2. Re-create new VMs and move the VHD in suitable locations.
3. Attach VHD disks
4. Reconfigure the network in the VM

[taher]

According to me the best is rather to use Hyper-V. If not for the installation of Virtual Server, chances are it is like to install on Vista. Ensure the permissions allow the Computer account of the Hyper-V host performing the Export to update the shared folder. Updating the share level permissions :

1. On the destination server, do the Right-click on the shared folder and then select Properties.
2. After selecting the properties, select the Sharing tab.
3. Then click Advanced Sharing.
4. On the Advanced Sharing dialog, click Permissions and then Add.
5. After that click Object Types and select Computers if not already done and click OK.
6. In the dialog "Enter the object names to select" provide the name of Hyper-V host machine and click Check Names.
7. With the Hyper-V host machine name select, click Allow by "Full control" and click OK.