Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, November 15, 2011 2:51 PM
I have used the Article ID: 2249906 to try and resove this error. It only started since I have created a dediacted SQL 2008 Server on the network. This is my attempt, so far using icacls:
icacls "C:\Users\Public\Documents\Hyper-V\Virtual hard disks\XYZ-SQL.vhd" /grant "NT VIRTUAL MACHINE
\13101CB0-271Z-4434-9736-E1DE331D316BZ":F
NT VIRTUAL MACHINE\13101CB0-271Z-4434-9736-E1DE331D316BZ: No mapping between account names and security
IDs was done.Successfully processed 0 files; Failed processing 1 files
Any ideas as this is becoming very disruptive to the network as the VM is a DC.
Many Thanks
Paul.B
All replies (5)
Tuesday, November 15, 2011 3:51 PM âś…Answered | 2 votes
The simplest way to repair permissions is to use the Hyper-V Management console, open the setting of hte VM, select the IDE interface, then browse to and select the disk, and apply.
This will force a reset of the permissions on the VM objects (including the VHD).
Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Wednesday, November 16, 2011 12:07 PM
Hi Brian,
I tried your suggestion, but it did not work. Here is the potted history: A Virtual DC was created-the idea was to promote this instead of the Physical DC which is currently running the AD Services. When creating the V-DC it created a V-Hard Drive-the SQL.vhd.
Later when I was looking to create a Project Server, it had two pre-requisites; a SharePoint Server and a SQL server/instance. The SQL Server was created using the existing SQL V-HD. This may have added an extra layer of security, and may have overwritten some of the Root system files-I'm not sure? I think this may have caused the problem? ANy advice.
Paul.B
Wednesday, November 16, 2011 2:30 PM | 1 vote
From your description it sounds as if you have two VMs trying to use the exact same virtual disk. And this is not possible without using differencing disks in between. (it will give the error you describe when trying to power on the second).
Beyond that, I would have expected the configuraiton change to work. Another possibility is simply creating a new VM using the existing virutal disk. This is non-descructive as well and absolutely re-creates all of the VM objects and generates new security identifiers.
If that does not work, then there is more to this puzzle than has been mentioned here and you will need to provide greater detail.
Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Friday, May 18, 2012 9:26 AM
Life saver - I moved my Snapshots (cut and paste -won't be doing that again) and so changed all SID Permissions. I was looking around trying to restore them but this saved me. Cheers.
Geoff Courts, Operations Manager, Macnamara IT www.macnamara.it
Monday, March 16, 2015 8:47 AM
This is an old thread, but I ran into this issue myself and the VM didn't have any snapshots, and I got the same error trying to use the icacls command as recommended by the MS KB article, so I was stuck. I solved it with an extra step, so wanted to add to this thread in case any one else came across it.
Brian's suggestion didn't work at first: I browsed the disk and re-selected it (it was an existing disk on the VM) and applied the changes, but the permissions still didn't have the ACL.
So I tried removing the hard disk from the VM, saving that change, then re-adding it. This step accomplished what Brian was suggesting and it silently repaired the permissions on the VHD file and the VM booted successfully.
Thanks for the hint!