During a full migration from Windows Server 2008 with SQL Server 2012 on physical hardware to Windows Server 2012 with SQL Server 2012 on VM, we have discovered a weird issue.
Some of the SQL Agent jobs won't even run if the 32-bit runtime is checked. Some other jobs would run only a few steps, not given much as far as troubleshooting error information. In order to make some progress, that option has been unchecked. That seems to be directly related.
It is weird that this option is checked by default, but mostly weird that from one OS to another, we ended with such situation.
Anything encountered the same situation during similar migrations?
