axinthefield: TempDB Errors in AOS event log after SQL Server Cluster Failover or AlwaysOn Availability Groups Failover

[Logger]

Comments :

karabela
March 4, 2014 at 1:51 pm
get-service -name AOS60$01 -ComputerName AOSSERVER1, AOSSERVER2, AOSSERVER3 | Restart-Service -whatif

start powershell with elevated rights. remove -whatif if you want to actually restart the aos services


Michael DeVoe
February 28, 2014 at 12:21 pm
@jaestevan, I will admit I am not a PowerShell guru, but if I find the time and find some commandlets I can "borrow" from I will write one and add it to the article.


Michael DeVoe
February 28, 2014 at 11:52 am
@Phil A, I completely understand your frustration as I helped a customer build an AlwaysOn Availability Group for Failover, ETL data loads for Data Warehouse, and doing back-up from only to find out that when it failed over, the AOS servers starting throwing errors left and right. The only consolation I can offer you is that it will be fixed in a later CU for AX.


jaestevan
February 28, 2014 at 1:53 am
Can you give us an example of this powershell script to refresh all services?


Phil A
February 28, 2014 at 1:09 am
I find it appauling that Microsoft's recommended high availability configuration for Dynamics AX doesn't actually serve any purpose at all because of this bug in the product. Our customer purchased an Enterprise license for SQL just to use AlwaysOn with Dynamics AX, and yet they still have to reboot their AOS's everytime a failover occurs, otherwise half the application stops working. What a joke.