SQL Server Hyper-V error – The application encountered an error while changing the state – VM could not be initialized – Failed to set/change partition property

Hi Friends,

I had built a SQL Server Hyper-V virtual machine on my laptop which has Windows Server 2008 R2 with Service Pack 1. I deployed the VM on my client’s machine with Windows Server 2008 R2 (no SP1). I ran the VM and got the following error:



It wasn’t immediately apparent that Service Pack 1 for Windows Server 2008 R2 was a pre-requisite since in earlier cases my VMs, that I built on SP1, did run on Windows Server 2008 R2 machines without SP1.

This error that you see above is a common error that pops up due to multiple reasons. I check into Hyper-V error logs and found the actual error 3040 which said:

<virtual machine name> Failed to set/change partition property

Upon investigating and reading this URL: http://support.microsoft.com/kb/2517374, I realized that the client machine’s latest hardware supports Intel’s VX feature which is not supported by Windows Server 2008 R2. Thus, I need to apply Service Pack 1 to my client’s PC, which I did and things worked fine.

Lesson to be learnt: As usual, the immediate error messages are less meaningful and very common, so dig into error logs to find the root cause of an issue.




About Amit Bansal

Amit Bansal is always brainstorming around SQL Server. Despite working with SQL since 1997, he is amazed that he keeps learning new things every single day. SQL Server is AB's first love, and his wife does not mind that. He tries to share as much and spreads the SQL goodness. Internals and Performance Tuning excites him, and also gives him sleepless nights at times, simply because he is not a genius, but quite a hard worker and does not give up. It has been a long and exciting journey since 1997, you can read here: http://sqlmaestros.com/amit-bansal/ He is on Twitter: https://www.twitter.com/A_Bansal

View all posts by Amit Bansal →

Leave a Reply

Your email address will not be published.