SCVMM 2008 BETA: error id: 1612, connection to the Virtual Machine Manager server was lost.
While I'm working with SCVVM console ( view properties, operate VMs, etc), and happen each 10-20 minutes, show me a popup error:
------------------------------------
The connection to the Virtual Machine Manager server xxxxx was lost.
1) Verify that xxxxxx is online and can be accessed from your computer. Then try to
connect again.
2) Verify that the Virtual Machine Manager on xxxxx is then try to
connect again. If the problem persists, restart Virtual Machine AManger service
ID: 1612
-------------------------------------
In Eventlog can see that the VMMServices stop unexpectedly and start.
---------------------------------------------------------------------------------
Log Name: System
Source: Service Control Manager
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
The Virtual Machine Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service.
-----------------------------------------------------------------------------------But, always, a few minutes before the service has been stoped, It is restarted WMI Services.
I have re-installed in same and diferent host, and the problem persist.
Any idea ?.
Answers
Hi -
You can pull the RC1 patch from the connect site, which should resolve your issue.
Please let us know if it does not.
Cheers!
-b
All Replies
You obviously have something going on that is causing your VM Management Service to keep crashing, thus your MMC keeps losing connectivity.
And the 10 - 20 minute range is one of the polling ranges for devices.
A little more about your environment:
SCVMM is installed where? In its own VM? Within a Hyper-V parent partition?
Your Hyper-V server is at path level RC0 (not RC1)?
Also, are you managing VMware from SCVMM? If so, is there NFS storage in that VMware environment?
I tried with two installations. In the first, SCVMM was installed in parent partition (RC0), in the second (the current) It's installed on Windows 2008 VM over VirtualServer (host with Windows 2003). The problem happend in both settings.
All of my Hyper-v servers are at RC0.
Thank you.
I don`t manage VMware and there isn`t a NFS storage.
Thank for your question, I had seen the threat (with the similar error as me) that you find the source of problem, NFS storage / VMware; but my environment is diferent.
I have the same problem.
My setup is Windows 2008 Server Standard install, not server core. SCVMM 2008 Beta 2 is installed on the same "host" machine.
Perhaps related to this error message, my library does not refresh. I've added a VHD file to the library share through Windows Explorer. Neither waiting on the 60 minute default refresh nor the manual "refresh library" option makes the VHD file appear. It's typically after performing the manual refresh that I'll receive this error.
I am not managing VMware installs and am not using NFS storage.
can you all file bugs through the connect site "connect.microsoft.com" and also capture traces from both the administrator client machine and the vmm server. tracing instructions are located at http://blogs.technet.com/chengw/archive/2008/05/08/how-to-collect-scvmm-traces.aspx
Try to collect the traces for a sufficient amount of time to diagnose this issue
Because Hyper-V RC1 is not supported by SCVMM 2008 beta, iI'll wait a few until the next version of SCVMM that support RC1.
I am having the exact same problem.
SCVMM 2008 Beta installed on my host Enterprise Hyper-V server (not core). RC1, all guests up to RC1.
My connection fails very frequently. I get less than a minutes use before the connection drops.
It seems to drop quicker when viewing a guest machine, ie, with the performance graph etc.
I know its a Beta, but this is ridiculous.
Gav.
I've had this exact problem - but it was before I found out that Hyper-V RC1 was not supported.
I've since wiped my server, installed 2008 Enterprise 64 and the Hyper-V role which I manually upgraded to RC0. You have to be careful that RC1 isn't installed from Windows Updates.
I then installed VMM 2008 BETA
At the moment I am converting a P2V and by jove it looks like it is going to work, as it's completed the copying of the hard drive contents already.
My previous attempts all failed with the 1612 error very early on.
I'll update you further with more information about my system if needed once it finishes properly.
Yes, I can confirm that is all worked perfectly now. Needed a new build of course, but these are the versions installede on my Server 2008 64 Enterprise server ( 8GB RAM)
VMM 2008 BETA 2.0.3194.0
Hyper-V 6.0.6001.18004Let me know if you want any more details.
Thanks.
Is this the RC1 version of HyperV?
Hyper-V 6.0.6001.18004
Also, how do you get the version info? Where is the file located on the system?
Finally, this "working" install is Server 2008 Full Install -- NOT server core?
You can chek out how to determine versions here:
http://itproctology.blogspot.com/2008/04/determining-versions-under-hyper-v.html
Greg Treanor wrote: Is this the RC1 version of HyperV?
Hyper-V 6.0.6001.18004
Also, how do you get the version info? Where is the file located on the system?
Finally, this "working" install is Server 2008 Full Install -- NOT server core?
Yep, it is "Full" server 2008 install and RC0. RC1 is not compatible.
I found the version number by opening up "Hyper-V Manager" and then looking in "Help" >> "About Hyper-V Manager"
My laptop has RC1 and I've just checked - it's version is: 6.0.6001.18010, so RC0 is 6.0.6001.18004
Hope that is of use to you
Kieran
Unfortunately, despite following the recommendations above, I'm having the issue.
Reinstalled Server 2008 Ent. 64 bit. Added HyperV role. Installed RC0. Accepted HyperV license terms. Installed SCVMM 2008 Beta 2 on host machine. Added host machine as host server. Started P2V conversion wizard. When the wizard opens the "Additional Properties" page, the application fails with the same ID:1612 message. After the app restarts, I noticed in the Jobs log the following entry which corresponds with my P2V conversion attempt in terms of time:
"Error (1711)
The Virtual Machine Manager service on the SERVER2008 server stopped while this system job was running. This may have been caused by a system restart. The job will automatically run again later."
I've posted this same issue to the Connect web site.
Sorry to hear that Greg. I was sure that my fix would also fix yours
Not sure what you can try next. What kind of spec server are you running this on?
Mine was a core duo (not core 2 duo) with 2 SATA hard drives and 8GB RAM.
The Hyper-V RC1 Update from connect fixed the issue for me.
I'm currently running
-
Windows Server 2008 Standard (build 6001: service pack 1)
-
Hyper-V RTM (build 6.0.6001.18016)
-
SCVMM 2008 Beta (build 2.0.3194.1)
on a 4 Gb machine.
-
Hi -
You can pull the RC1 patch from the connect site, which should resolve your issue.
Please let us know if it does not.
Cheers!
-bI also have the same problem,
I have an HP Proliant DL380 G5 with quad core Intel Xeon CPU and 24GB Ram. I originally had Server 2008 Enterprise Full install with Hyper-V RC1 installed and then installed SCVMM 2008 Beta along with the update. Once the RTM was release I installed that and all still worked fine. However due to needing to change the RAID configuration, I have since rebuilt the server from scratch and this time installed Server 2008 Enterprise, installed the RTM version of Hyper-V and enabled the Role. Then installed SCVMM 2008 Beta and now I get the constant restarting service.
Do you think that we still need to install the RC1 Update from the connect site?
Cheers,
Keith
Keith,
I know I installed from scratch and had to install the RC1 Update. So I guess so.
Regards
- Hi,
I also am having the same issue. I've reinstalled SCVMM08 beta twice on two different servers with the same disconnect 1612 error after about 15 minutes. I have hyper-v rtm with the most recent scvmm08 rc1 beta, which is scvmm08 version 2.0.3194.1 (as shown in Add/Remove Programs). I'm using scvmm08 with the sql express edition db. I'm also using it to manage my vmware virtual center environment. Once i login to scvmm and do nothing for about 10-15 minutes, it will just disconnect with the 1612 error id. I can click ok to restart the admin console which will work 80% of the time, the other 20% of the time I usually reboot the box since it wont log me in.
Is this a known issue in the scvmm08 beta?
I've also verified that the following files are updated to "2.0.3197.0" by the scvmm rc1 patch:
ViridianImplementation.dll
WsManWrappers.dll
Engine.VmOperations.dll.
Thanks,
Nate Hi Brenden,
I'm having the same problem but your post doesn't clarify which version of Hyper-V I should be using.
I'm now using the RTM version of Hyper-V (18016) and I've got the described problems.
Are you saying that the SC VMM 2008 Beta does not work with the RTM version of Hyper-V and I should downgrade to the RC1 version of Hyper-V and then get the RC1 patch from the connect site ?
Hyper-V cannot be downgraded.
If you are running RC1 or RTM of Hyper-V then you must apply the SCVMM 2008 Beta RC1 compatibility patch.
You must also install the Hyper-V RC1 (or RTM) patch on your SCVMM Server.
(this is for WinRM compatibility (and other things)).
I am 90% sure that if you try to add a host to scvmm that is hyperv rtm it will broke your scvmm installation, even if you applied the scvmm patch. If you add an rc1 hyperv and then upgrade it everything will be fine.
Regards,
Corrado
CMollica wrote: I am 90% sure that if you try to add a host to scvmm that is hyperv rtm it will broke your scvmm installation, even if you applied the scvmm patch. If you add an rc1 hyperv and then upgrade it everything will be fine.
Regards,
Corrado
I'm having this situation too. I think the "FAQ for SCVMM regarding to Hyper-V RTM" should be updated.
Getting the same Error 1612
I have a VMM 2008 Beta on Windows 2K8 enterprise edition. I installed the following:
VMM Beta 2.0.3194.0
Hyper V Manager 6.0.6001.18016I am trying to convert a 2008 server to a virtual 2008 server and its failing. At 99% of the completion of virtualizing the server the Virtual Machine Manager Service terminates unexpectedly. Everytime I try to restart the job it starts and fails.
It was doing this identically to everyone else's post where every 20 minutes it would fail.
I am running the Hyper V and the VMM on the same machine, and I am wondering if they can or cannot be installed on the same machine. There are no other things running on this server since it is for testing purposes only within our lab environment.
Can anyone let me know how to get the trace started so I can figure out why this thing is bombing.
From your post I can't tell if you applied the QFE for VMM 2008 that provides support for Hyper-V RTM hosts? Yes, VMM 2008 and Hyper-V can exist on same server.
The QFE for VMM 2008 is available on connect.microsoft.com .
Hi Guys
I am facing the same issue. "error 1612" while refreshing the hyper v cluster.
My setup is
Windows Server 2008 Standard (build 6001: service pack 1)Hyper-V RTM (build 6.0.6001.18016)SCVMM 2008 Beta (build 2.0.3194.1) - From Control panel. But on the VMM console the version is build 2.0.3194.0.I am having a dedicated HP BL460c (8GB Mem/2XQuad processors).
Shan
- I've noticed that as well. The SCVMM08 beta admin console shows version 2.0.3194.0 even after the scvmm rc1 patch. Control panel shows it as 2.0.3194.1.
Is this a known issue? If so is there a workaround besides having to reinstall everything all over again?
Thanks,
Nate - Hello everybody
For the second time, I also have the following error:
-----------------------------------------------------------------------------
The connection to the Virtual Machine Manager server localhost was lost.
1) Verify that localhost is online and can be accessed from your computer. Then try to connect again.
2) Verify that the Virtual Machine Manager service on localhost is started, and then try to connect again. If the problem persists, restart the Virtual Machine Manager service.
ID: 1612
-----------------------------------------------------------------------------
For the first time, i got the error message with the following set up:
- Windows Server 2008 64Bit fully updated
- Hyper-V Manager Version: 6.0.6001.18016
- Windows Server 2008 64Bit fully updated
- SCVMM Admin Console (without SCVMM Hyper-V RC1 Update)
After installting SCVMM Hyper-V RC1 Update it worked fine - the problem was fixed.
But after adding a VMWare ESX Server in the SCVMM Admin Concole the same error message (ID: 1612) happened again.
Set up:
- Windows Server 2008 64Bit fully updated
- Hyper-V Manager Version: 6.0.6001.18016
- Windows Server 2008 64Bit fully updated
- SCVMM Admin Console (with SCVMM Hyper-V RC1 Update)
I hope there will be soon an update to fix this problem.
For furhter information, just write a post, i'll follow the conversation here.
Thanks, Dominique Could this error be related to managing esx with scvmm08? Now, if I try to remove my VC server, I get the 1612 error every time. So I'm stuck and I cant remove my VC server.
Are others having this problem?
Thanks,
Nate
- Read the last post bevor yours :-)
I run SCVMM without problems with HyperV but after integrating VMWare ESX te problem returned.
Dominique Dominique Huber wrote: Read the last post bevor yours :-)
I run SCVMM without problems with HyperV but after integrating VMWare ESX te problem returned.
DominiqueI don't think this has anything to do with VMware. I am having the same issue with 3 different servers, and never tried to manage VMware with this product. It connects fine after the installation, but once you start "working" with the product, doing things like creating or deleting virtual machines, exporting / importing, converting from VMware, adding libraries, etc. I get the error. I tried with SQL STD on a separate server, on the same server, and SQL express. Again and again, the same results.
This issue is very frustrating, and the people at the connect forum who are supposed to help you with the issues with beta programs only make things worse by closing the threads without providing a solution claiming that they have fixed it. You can see that behavior in all the various threads about this issue in the connect site. I guess some well trained mouse-clicking monkey is making an easy buck by closing those treads without providing a valid solution for this issue.
I have searched everywhere for a solution but all I find is a lot of desperate people having the same issue on different configurations, but no one has a real solution for the problem.
If you have found a fix for this, please post it here, so we all can keep beta testing this product for Microsoft, while we wait for the bug-free RTM version promised for the near future.
For what is worth…. The servers that experienced the problem did not have a dedicated NIC for managing Hyper-V. I recently rebuilt two of those servers with an extra NIC just for managing Hype-V like MS recommends, and they are still working fine after two days (knock on wood). A new record for what I have experienced. This makes me wonder if this issue we are seeing is the reason why MS “encourages” you to use a dedicated NIC for management. Has anyone experienced the issue on a server that has a dedicated NIC for management?
- Yes, I have a dedicated NIC for management and still experience the continual 1612 error
Could you please post your configuration and installation steps. It is very weird that my two servers that were broken before, now are working fine after I rebuilt them with the extra NICs.
The way I set them up this time was:
1.- MS Automatic Update downloaded and installed the Hyper-V RTM patch.
2.- Installed Hyper-V (dedicated NIC for management). Disabled Jumbo Frames (I had this disabled on another server that was broken but I think is worth mentioning).
3.- Installed SCVMM Beta on same server. Used default ports and SQL express.
4.- Stopped the SCVMM service and Agent Service.
5.- Patched SCVMM with the patch provided on MS Connect, and restarted services.
6.- Installed the Console in another server. Connected successfully.
Did the same on the second test server and everything worked fine too.
Hopefully this is not just plain luck.
I did step 2 first and then step 1 and my SCVMM beta and SCVMM console are on the same remote server instead of different servers, the rest is the same as what I did.
At this point I'm just going to wipe and reload everything see if that changes anything and if your steps work for you I'll give it a try that way and will post an update with my results.
Thanx
- I wiped adn reloaded all 3 servers and I still have the same error id 1612 issues...
I’m very sorry to hear that. Did it break right after the installation, or after running a job?
One of my servers broke during the weekend with the connection error after a failed attempt to convert a VMware vm. After deleting the folder for the failed vm, and removing everything else in the library it started to work again. It broke again a couple of times doing the same activity, and I was able to get it back to work by removing the objects in the library. Right now I do not have anything at all in the library, and once I’m done with a process, I go ahead and clean the library. So far, so good. You might like to give this a try. You don’t need to delete your files if you don’t want to, just move them out of the library share, so the items become missing and you can go ahead and remove them.
I'll give that a try but if it doesn't change anything I'm just going to abandon this for a while and go back to server 2003 and VS 2005 I need to get these servers into production
Thanx
WOOT! I figured out what the problem is...at least for me...I have Qlogic 2460 FC adapters in my Dell servers and I wanted to setup and test NPIV so I can use the SAN transfer capabilities this require QLogic HBA driver version 9.1.7.16 which is what I've been using in test...when i rolled the driver back to version 9.1.4.6 which is what I use in production the error 1612 went away!
Now just to keep it interesting I loaded up server 2003 and installed VS 2005 sp1 with VMM 2007 and loaded the Qlogic driver 9.1.7.16 and guess what it even crashes the VMM 2007 with error 1612, when I rolled back to the 9.1.4.6 version it started working again.
Hope this helps someone else
Hi
Even I feel it's something to do with one of the drivers (But don't know which one - as I don't want to mess with my production system) . SCVMM2008 was working fine for me during my test phase. But in production I updated my HP Servers (Hyper-V) with the latest Proliant Support Pack 8.10 and then the problems started. I think MS should have a look in to this and release an SCVMM patch or something.
Shan
- Do step 5 EVERYONE (from RCRUZ's post above!)- Install the SCVMM Patch on MS Connect. ("SCVMM Hyper-V RC1 Update"). this fixed it for me!
In some cases the patch is fixing the problem. But for me SCVMM version is RC1 (already patched).
- I have the same problem. I have Hyper-V RTM as perimetr host. I have "dc1" - Windows 2008 x64 Domain Controller Installed on one of the Virtual Machine in Hyper-V host. On dc1 I have install SCVMM 2008 Beta + (Update for Hyper-V RC1). When I try to add Hyper-V perimetr host, SCVMM console stop responding with error ID:1612, and Virtual Machine Manager Service terminated unexpectedly. Restart of the service do not help to me! Even the service is started, console could not connect to the scvmm 2008 server, and vmmservice.exe crash again and again.
Obviously this is a bug. I'm getting the same error:1612 as many of you are and have applied the suggested patch for SCVMM 2008 beta without luck.
Currently running:
Windows 2008 x64 full install
Hyper-V - 6.0.6001.18016 - RTM
SCVMM - 2.0.3194.0
Do I even attempt to uninstall the beta and give 2007 a shot?
TD2
SCVMM 2007 will not manage Hyper-V VMs......
Todd
I have the similar problem as do have vmware attached. I also have NFS shares on the VMware environment.
What is NFS has to do with this error?
Hi
Is this post closed. Did somebody find a solution or are we still waiting for a patch from MS?
Shan
- I don't think it's any one thing that causes this behavior...for me it was a Qlogic Fiber Channel driver issue so I'm working with EMC, Qlogic, and Dell to resolve the issue.
All,
let me try to explain my environment as well as my issues here.
I have Server2008 Ent endition installed and configured with Hyperv with the latest patch.
I have installed SCVMM 2008 beta on the host server itself.
Initially I had issues with error 1612 and after applying the latest SCVMM patch from the connect website, the issue got resolved. 9 at elast I had a stable VMM for 2-3 hours without disconnect)
Now I added Vmware virtual center to the VMM console and the disconnect issue is back again.
if I start the VMM console it tries to connect for 1 minute and then times out and give me a box with servername
ortExample: Win2k8TST:8100. if I click on the connect button it will come back with a ID 1602 ( VMM service did not respond).What is the issue here?
I went to the services console and check the status of Virtual machine manager service..it was stopped...What is cauing this? I have now started the service....and is now able to use the VMM manager console...but getting disconnected in 2 minutes....with error ID 1612 again.
Do you think adding the VMware Virtual center is cauing this issue?
What VMM manager console is taking so much time to connect?
My hardware is failrly new..it is a HP DL 385 G2 with 4GB RAM and two dual core processors.
I'm a Windows Admin but working on Vmware for the past 3-4 years...I was happy to know that Microsoft is coming up with some thing great and now, it looks like all my interest towards that product is slowly getting diminished. Why MS is releasing a product ( though it is a Beta) without even resolving the basis issues.
I had issues adding my HyperV server to the VMM initially and the issue was a disjoint dns domain,
meaning, if your Host server's primary DNS is a BIND or a CISCO DNS, it cannot added to VMM as it look for that dns name in the AD. After chaning my primary DNS server on the Host server to AD DNS it allowed me to add it to VMM.
I think, I'm wasting my time here.....if I could spend all these valuable time researching some thing from VMware, I could have gained some thing by now.....
Above is my furstration..I know there are issues and problems we have to go through to get a real good product....let us work together and hope we will have a good product soon. I need to be a Virtulization guy, not just a Vmware or HyperV guy....
Can someone from Microsoft address this issues....Is it advicable to add VMware Virtual center to VMM at this point?
I mean with this problamatic Beta version? What all precuations we need to take to have a stable environment to do some testing...
if you need to contact me, send me Mails at deepu_c@hotmail.com
Deepu.
I have a exact same problem....This needs to be addressed ASAP. If we remove the ESX hosts ( within the one min time you get), will it work normal?
It seems to be some compatibility issues. I've only Windows servers but SCVMM is crashing for me also. What I remember doing is updating my HP servers (Host Machines) with the latest Proliant Support Pack CD. MS should give us a solution.....
- Im not sure if managing vmware is part of the issue. Like yourself, I've installed SCVMM08 beta and applied the latest patch around 5 times now, 4 of which were on totally different hardware. All of the installs had the same disconnect issue. Currently, im using scvmm08 beta to ONLY manage vmware as im in the midst of doing some testing. So far, no disconnects with just managing vmware. Once i add in my hyper-v servers I'm positive that ill get a disconnect.
I too would like an official statement from MS that they're at least working on the problem. The clients I work for are kind of hesitant to go with 100% hyper-v due to these issues. Although it seems that the scvmm08 might GA in a few weeks at their virtualization event. Ill just have to wait for that.
Thanks,
Nate Lee,
I just jumped in to this thread as soon a receive a alert that there was a new post. I thought someone might have come up with a solution. Unfortunetly it was not.
As you said , I'm not sure how long we have to wait for a new update to come.
I did notice that if you remove the Hyper-V server, it stays connected. But the question is why do I have to use SCVMM to manage my ESX hosts and VM's..I have a wonderful fully working VC 2.5 :-)
Thanks
Deepu
- Hi Deepu,
I'm currently testing the scvmm08 functionality with vmware for some of my customers who are planning to deploy both hyper-v and esx. From my results so far, i wouldnt recommend managing esx with scvmm. It actually adds complexity to the environment when you have to still use VC to do some things and then use scvmm to do other things. Not to mention the strange things it does to VC for some tasks. I might as well just use vc for vmware and server manager/scvmm for hyper-v. Ill have to wait until the GA is released to see if MS improved any functionality, but most likely my customers will stay away from scvmm managing esx.
Thanks,
NateL I have a new windows 2008 server with Hyper-V installed. It is fully patched. I am experiancing the exact same issue.
The connection to the virtual machine manager server localhost was lost.
ID: 1612
Same thing here, completely new HP ML150 G5 server, fresh server 2008 x64 installation, fully patched. When I try to add the localhost machine to SCVMM 2008 beta I receive the error 1612, connection is lost.
In the details of the job it says:
1. add virtual machine host - 66%
1.1 install virtual machine manager agent - 100%
1.2 enable hyper-v - 100%
1.3 refresh host - 0% (marked with a red cross as in failed)
removed host, started job again, no go.
This is very frustrating, was trying to do a demo at a customers, this will not help them deciding on migrating from Vmware to Hyper-v.
regards,
Edek
Well here we are in November and SCVMM 2008 is RTM. I've gone ahead and installed the latest security patches from MS on my Hyper-V host, my SCVMM server, as well as the target server to be converted using the P2V wizard. I get the same exact error as with the beta version. Anyone else?- I got the 1612 error once after I resolved the port 443 certificate issue, then it just started working
Hi
I've done a re-installation of my SCVMM 2008 server with the RTM and is using it ever since without any problem. (almost 3 weeks now) and I love it. Now I am no more getting the 1612 error and the console is not crashing at all. I even did a P2V of a dell server and the activity took only 15 minutes without any errors.
Thanks guys...
Brgds
Shanavas
- Glad to hear. I'm still having the same issue
- This finally fixed the issue for me : http://systemcentertech.wordpress.com/2008/07/30/scvmm-2008-refresh-library-error-1612-resolved/
Daniel McNamara
