• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4111
  • Last Modified:

VMM P2V Failure

Hey,
 
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
0
EveryNetwork
Asked:
EveryNetwork
1 Solution
 
brent_caskeyCommented:
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.

There are also some recommended updates that you should apply to the system: http://support.microsoft.com/kb/962941 


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\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
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

0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now