Hyper-v Certificate Error
Contents |
MOC Labs, the date & time needs to be reverse (back to the future!) As most of the lab machines could not initialize machine remoting system. error: 'element not found.' (0x80070490) are cloned using the actual date & time, Hyper-V creates a certificate hyper v could not find a usable certificate error element not found the moment the Virtual Machine is being created and started; only during the class, the date & time will be reverted element not found 0x80070490 hyper v back in time. When attempting to Connect (or literally remote control) the VM, the status of the VM will show as ‘Starting…' and subsequently throw with errors: An Error Occurred
Hyper-v 0x80070490
while attempting to start the selected Virtual Machine(s): ‘Virtual Machine Name' could not initialized Could not initialize machine remoting system. Error: ‘Element not found.' (0x80070490). Could not find a usable certificate. Error: ‘Element not found.' (0x80070490). To resolve this matter, follow the steps below: Start > Run > MMC Add the Certificates Snap-In Select Service Account Under the Select Account to Manager, select Hyper-V Image Management Service Complete the Snap-In Wizard Expand the Certificates under Personal Category Notice the certificate generated has been created ‘for the future' (assuming you're suppose to revert the date & time to 2010, the certificate should display as invalid because it was created at 2013) Delete the Certificate(s) Go to the Services Console and Restart all Hyper-V Services Now, go back to the Hyper-V Manager and the VMs should be able to be ‘Connected' right now. Share this:ShareTwitterFacebookEmailGoogleLike this:Like Loading... Related MVP Logo Recent Posts Symantec.Cloud - Can't Access the Symantec.CloudService Provisioning a Skype for Business Online MeetingRoom 2015 in review Unable to install Windows 10 on a GPTPartition/Disk Assigning Office 365 Licensing - InBulk Recent Comments Andrey on Couldn't find the Enterp…Best MMO on File Store Sharing & NTFS…Finding Accounts in… on Insufficient access rights to…Moraine (@moraineban… on Can't Sign In toLy…jamesosw on Can't Sign In toLy… Favorite Sites Lou Leong Life with O365 Lync IdeaScale My Skype Lab Great Lync Bloggers Elan Shudnow's Blog Jeff Schertz's Blog Justin Morris on UC NextHop UCs
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Cannot start virtual machine on Windows Server 2012 Windows Server > Hyper-V Question 0 Sign in to vote Hello, I have a weird problem and have been unable to find a solution to it after two days of searching. I have Windows Server 2012 host on IBM x3500M2 machine. I set up a hyper-v platform (added the role, configured the storage and network) and created two virtual machines. Now when I try to start either one of these VMs, using the Hyper-V manager, it throws this error: "machine https://jamesosw.wordpress.com/2013/06/07/hyper-v-could-not-find-a-usable-certificate/ name" could not initialize Could not initialize machine remoting system. Error: Element not found. (0x80070490). Could not find a usable certificate. Error: Element not found. (0x80070490) In the event log there is a similar error with the event IDs: 3040, 12460, 12500. I tried clearing up the certificate from vmm/personal folder to recreate it again but to no avail. I found few articles regarding a similar problem on Windows Server 2008R2 but https://social.technet.microsoft.com/Forums/windows/en-US/e120fe36-7ba7-4c74-a086-7d5fb352be53/cannot-start-virtual-machine-on-windows-server-2012?forum=winserverhyperv from what I can see this problem mainly occurs with SCVMM... Wednesday, June 19, 2013 7:32 AM Reply | Quote All replies 1 Sign in to vote Hi Restart Server orVirtual Machine Management(vmms) services in the services . after that and you have same problem see this You cannot connect to a virtual machine when the Windows Server 2008 Hyper-V VMMS certificate has expired I Love God,because he help me to find Technet. Edited by YahyaZahedi Wednesday, June 19, 2013 8:12 AM Add content Proposed as answer by Yan Li_Moderator Monday, June 24, 2013 6:44 AM Wednesday, June 19, 2013 8:10 AM Reply | Quote 1 Sign in to vote Now when I try to start either one of these VMs, using the Hyper-V manager, it throws this error: "machine name" could not initialize Could not initialize machine remoting system. Error: Element not found. (0x80070490). Could not find a usable certificate. Error: Element not found. (0x80070490) Tried using powershell? get-vm "name" | start-vm -verboseMarius Davidsen Hyper-V & Powershell enthusiast Wednesday, June 19, 2013 9:21 AM Reply | Quote 1 Sign in to vote Hi, Please restart your server orrestart VMMS service tocheck the result. In addition, I searched the internet and found that someone with the same issue has solved it byremo
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job https://www.experts-exchange.com/questions/28475522/Hyper-V-Could-not-initialize-machine-remoting-system-Could-not-find-a-suitable-certificate.html Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Hyper-V / "Could not initialize http://news.softpedia.com/news/Fix-Hyper-V-Expired-Virtual-Machines-105860.shtml machine remoting system" "Could not find a suitable certificate" Want to Advertise Here? Solved Hyper-V / "Could not initialize machine remoting system" "Could not find a suitable certificate" Posted on 2014-07-14 Virtualization Windows Server element not 2008 Hyper-V 1 Verified Solution 23 Comments 2,088 Views Last Modified: 2014-11-12 Hello, looking for some assistance on an error we are receiving on an Windows Server 2008 R2 Hyper-V installation. This is a full server installation, not a core install. We have one VM and it will not start, the error is "Could not initialize machine remoting system. Error: Element not found (0x80070490)" It is then following by element not found the error "Could not find a usable certificate. Error Element not found (0x80070490)", See the attached screenshot for the full error. So far I have done quite a bit of troubleshooting that has included: 1. Restarting the Hyper-V services. 2. Restarting the server. 3. Creating a new VM that will not start. This tells me it is a Hyper-V issue and not particular to the VM that won't start. 4. Removed all local FQDN certificates from all certificate stores. 5. Imported the local FQDN self generated certificate into the Hyper-V vhdsvc\Personal certificate store. 6. Uninstalled the Hyper-V role, rebooted and re-installed the Hyper-V role and rebooted. The only information I can find on this error says the certificate is supposed to be generated once the hyper-v services start but that doesn't fix the issue. Any help would be appreciated. HyperVError.png 0 Question by:htsupport Facebook Twitter LinkedIn Google LVL 1 Active today Best Solution byhtsupport Unfortunately not. Microsoft worked on this issue for about 2 weeks and did many of the same things we had already tried and that you had suggested. This included using makecert to create a certificate Go to Solution 23 Comments LVL 28 Overall: Level 28 Windows Server
GO A hotfix is available from Microsoft Mar 3, 2009 11:00 GMT · By Marius Oiaga · Share: Microsoft has acknowledged the existence of an issue related to virtual machines running under Windows Server 2008 with the Hyper-V role enabled or Microsoft Hyper-V Server 2008, where items can no longer be executed or accessed because of a certificate error. According to Microsoft, attempts to connect to a vm would result in an error message: “Cannot connect to the virtual machine because the authentication certificate is expired or invalid. Would you like to try connecting again?” At the same time, starting a vm will produce the following error message: “'VMName' failed to initialize. Could not initialize machine remoting system. Error: ‘Unspecified error’ (0x80004005). Could not find a usable certificate. Error: ‘Unspecified error’ (0x80004005),” Microsoft revealed. The Redmond giant is not offering an update to resolve the issue, however, the company did publish the KB Article 967902 hotfix offering affected customers a fix. The article also describes a workaround designed to also take care of the problem. All virtual machines have to be shut down or saved, following which the Hyper-V VMMS will have to be restarted. These simple steps can ensure that the vms will start and function under normal parameters. “Even if you are not currently experiencing this issue, we recommend you download and install this update,” revealed Bryon Surace, senior program manager, Windows Virtualization. “Though this error may occur, the Hyper-V service will continue to operate. Neither the Hyper-V host nor the running virtual machines will go offline. It is not expected that this issue can be exploited for malicious purposes. Customers running Windows Server 2008 R2 Hyper-V beta won’t experience this error.” The update is designed to integrate exclusively with Windows Server 2008, Standard (Hyper-V role enabled); Windows Server 2008, Enterprise (Hyper-V role enabled); Windows Server 2008, Datacenter (Hyper-V role enabled); and Microsoft Hyper-V Server 2008. #Hyper-V#Windows Server 2008#virtualization#virtual machine subscribe feedly old reader newsblur digg reader rss feed reddit it! flip it share it tweet it Related · Hot right now · Latest news Codename Velocity CTP3 for Vista SP1/XP SP3 Drops in March 2009 Windows 7 Beta Application Incompatibility Behavior Windows 7 Beta Web Servi