SCVMM error 3101

Whenever i try to create a new virtual machine or do a P2V i constantly get a error 3101 stating that

VMM failed to mount the VHD file
internal error code: 0x80990c1d

Recommended Action: To check device manager/system devices to ensure that virtual server storage bus is installed and functional if not, install VHD mount component of virtaul server. Restart virtual disk service.

I have followed the above actions and all the things seems to be in place.

Any Suggestion will be highly appreciated.

Thanks

Inam

Email: Inam.haq@aku.edu

jaweddeshmukhAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

plimpiasCommented:
It seems something is either missing or corrupt with SCVMM. I would repair the installation or reinstall if it does not work.
0
jaweddeshmukhAuthor Commented:
Nothing is missing with the install, it was a clean one. I have already tried a reinstall but to no avail.
0
mdmiddleCommented:
Are you trying to bring up the new VHD on a Hyper-V Failover Cluster?
Is the target path using a drive letter or a volume GUID?
Is the target volume SCSI, iSCSI, Fibre Channel, local disk?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

jaweddeshmukhAuthor Commented:
There is no Hyper-V failover cluster involved.
The VHD is there on a Local Disk. (No shared storage is present)
I am trying to P2V on a physical host that is running Win server 2003, with Virtual Server 2005.
0
jaweddeshmukhAuthor Commented:
No it is not an IBM SAN!
0
jaweddeshmukhAuthor Commented:
However the issue got resolved, after I logged a support call in MS.

The resolution is as follows:
This issue appears if you try to use a Beta version of Hyper V with the latest version of SCVMM. The recommended procedure is to freshly install a server, apply all updates on it and then enable HyperV role on the server that is to be used as the hosting platform for virtualized machines.

Requesting to close the question.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Virtual Server

From novice to tech pro — start learning today.