- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsHey,
I am trying to convert a physical server to a virtual server using SCVMM. After running through the wizard, the conversion process stops at 40% and I receive the following error message in VMM on the Host server.
Error (3154)
An internal error has occurred trying to contact an agent on the MPO-MGMT.venrock.com server.
(Internal error code: 0x8099319E)
Recommended Action
Ensure the agent is installed and running. Ensure the WMI service is installed and running, then restart the agent.
I am new to VMM, this is my first attempt to convert a server and I am not sure how to verify whether the VMM agent is installed or how to go about un-installing and re-installing. I looked at the log files as suggested on one of the websites that I found and it indicated that the agent is installed successfully.
MSI (s) (58:9C) [09:53:20:477]: Product: Microsoft System Center Virtual Machine Manager P2V Agent -- Installation completed successfully.
MSI (s) (58:9C) [09:53:20:477]: Cleaning up uninstalled install packages, if any exist
MSI (s) (58:9C) [09:53:20:477]: MainEngineThread is returning 0
MSI (s) (58:90) [09:53:20:586]: Destroying RemoteAPI object.
MSI (s) (58:74) [09:53:20:586]: Custom Action Manager thread ending.
Has anyone run into this before and if so can you offer some feedback.
Thanks in advance.
Report post as abusive
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: brent_caskeyPosted on 2009-02-17 at 23:13:59ID: 23667582
I have seen this error before. There are a couple of reasons for it though. I believe that at 40%, it is running the BITS transfer. BITS uses port 443 by default. Sometimes, port 443 is blocked or in use on one of the servers. Make sure that the WWW publishing service is disabled on both the source server and the scvmm system. If you are also running the self service console, make sure that is turned off on the SCVMM system as well. If there are any firewalls on either system, make sure those are disabled.
om/kb/9629 41
osoft\Micr osoft System Center Virtual Machine Manager Server\Settings
There are also some recommended updates that you should apply to the system: http://support.microsoft.c
The 3 services that are needed to be installed / running are the following:
VMM Agent
Windows Remote Management (WS Management)
Windows Managament Instrumentation
You may need to do the following to get around the 443 port issue:
1. Go to Regedit->HKLM\Software\Micr
2. Create a new DWORD reg entry named P2VBITSTcpPort and give it a decimal value of say 500 or any other port that is not being used on the host machine.
3. Go to system services (services.msc) and restart Virtual Machine Manager service and BITS