Service fabric error – Enable failed for plugin (nam Microsoft.Azure.ServiceFabric.ServiceFabricNode, version 1.0.0.33) with exception

Service fabric error – Enable failed for plugin (nam Microsoft.Azure.ServiceFabric.ServiceFabricNode, version 1.0.0.33) with exception

While deploying service fabric cluster i got below error at the end of deployment and the node was in failed state.

Error – Handler ‘Microsoft.Azure.ServiceFabric.ServiceFabricNode’ has reported failure for VM Extension ‘node1_ServiceFabricNode’ with terminal error code ‘1009’ and error message: ‘Enable failed for plugin (nam
Microsoft.Azure.ServiceFabric.ServiceFabricNode, version 1.0.0.33) with exception Command C:\Packages\Plugins\Microsoft.Azure.ServiceFabric.ServiceFabricNode\1.0.0.33\ServiceFabricExtensionHandler.exe of
Microsoft.Azure.ServiceFabric.ServiceFabricNode has not exited on time! Killing it…'”

Detail error –

Microsoft.Compute/virtualMachineScaleSets ‘node1’ failed with message ‘{
“status”: “Failed”,
“error”: {
“code”: “ResourceDeploymentFailure”,
“message”: “The resource operation completed with terminal provisioning state ‘Failed’.”,
“details”: [
{
“code”: “VMExtensionHandlerNonTransientError”,
“message”: “Handler ‘Microsoft.Azure.ServiceFabric.ServiceFabricNode’ has reported failure for VM Extension ‘node1_ServiceFabricNode’ with terminal error code ‘1009’ and error message: ‘Enable failed for plugin (nam
Microsoft.Azure.ServiceFabric.ServiceFabricNode, version 1.0.0.33) with exception Command C:\Packages\Plugins\Microsoft.Azure.ServiceFabric.ServiceFabricNode\1.0.0.33\ServiceFabricExtensionHandler.exe of
Microsoft.Azure.ServiceFabric.ServiceFabricNode has not exited on time! Killing it…'”
}]}}’

 

Solution – 

The nodes are failing since downloading some component failed. Usually this is because of incorrect certificate values passed to ARM or some  policy restriction on vnet/network

1> check if you have correct certificate thumbprint , vault url and other certificate detail without any blank space while passing it to ARM

2> check if you have any restrictions set on network and try to create new vnet and use ip from that vnet. in my case i had to create new vnet since some one set policies on existing vnet.

 

(Visited 135 times, 1 visits today)
One Comment

Add a Comment

Facebook