Live Migration failed with error 0x00002745

I just got a strange error message during a failed live migration.

Type: Error
Event-ID: 21502
Source: Hyper-V-High-Availability

Message:   

”Virtual Machine {server}' live migration did not succeed at the source
 ....
Could not send data to the remote node: An Established connection was aborted by the software in your host machine (0x00002745)


or in german stating

"Es konnten keine Daten vom Remoteknoten empfangen werden: Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer abgebrochen. (0x00002745)"

Long story short:  Live Migration failed, we tried a quick migration which worked "well" but couldn't start the VM. After opening the console of the vm and trieing to start the saved quick migrated state we saw the real error "not enough memory available"

SnapManager Exchange or SQL Service failed to start

or why .NET-Applications need long to start: "A common cause that I have seen often recently is Certificate Revocation List (CRL) checking when generating Publisher Evidence for Code Access Security (CAS)."[1]

In my case the Exchange Sever didn't had anymore direct access to the internet. The CRL checking during the SM Serverice Startup failed. This took longer than 30 seconds and causes the service start to time out. Adding some lines to the SnapMgrService.exe.config prevent the service to do the online CRL check. No further timeouts, services starts.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
        <generatePublisherEvidence enabled="false"/>
    </runtime>
    ...

Same issue some month's later with a SnapManager SQL installation. Good to have a cheat sheet for the most wired thing online.

[1] Best Practice - <GeneratePublisherEvidence> in ASPNET.CONFIG

Granting Permissions to Domain Admin group on SQL Server 2008 Instance

I just wondered about why i couldn't login as member of the domain administrators group to the SQL-Server after i added this group to the SQL as sysadmin. If i add me as user itself the login workes fine.  Here is the right "procedure":


- Add Domain Admins group in the SQL Server Security Login
- Give Sysadmin rights to the Domain Admins group

AND (if you login as member of the group)


- Disable UAC or start the SQL Server Management Studio as an Administrator

Host CPU is incompatible...

Ups... i forgot somethign basic: If i power on a Windows 2008 R2 virtual machine within a ESX testing environment i get the following error:

Host CPU is incompatible with the virtual machine's requirements at CPUID level 0x80000001 register 'edx'.
Host bits: 0000:1100:0001:0000:0000:1000:0000:0000
 Required: xx1x:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Mismatch detected for these features:
* Longmode; required when a virtual machine is configured for a 64-bit guest OS. For systems with Intel CPUs, enabling VT in the BIOS is required for longmode support.
 
For incompatibilities other than NX/XD or longmode: if possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212. In the absence of EVC, see KB article 1993.

The solution is so simple that i forgot it the second time during the last months: Enable "virtualisation technology" and "Execute Disable" within the servers bios. After a reboot you should be able to power on the VM.

SnapManager VI fails to create snapshots

Currently troubleshooting the backup of a brand new VMware 4.1.0 installation... 

VMware shows up with the following error:

Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine

After some research[1][2] i found a hint to follow these steps:

1. Backup the following regkey: _HKLM\Software\Microsoft\EventSystem _
2. Erase the regkey HKLM\Software\Microsoft\EventSystem{26c409cc-ae86-11d1-b616-00805fc79216} an below
3. Reboot
4. Verify that things are working by running

Even if it might worke well you never should follow these steps!

Better: Uninstall the VMware Tools and Reinstall them using the custom installation option. Disable the VMware VSS provider component and retry the backup.


----
[1] http://communities.vmware.com/docs/DOC-11987
[2] https://kb.netapp.com/support/index?page=content&id=2014932