failure to deploy winplatform/runtime node to galaxy

Based on the error in the deploy logs. The possible reasons are.

1. The aabootstrap service on the remote node is not running.
2. The remote  node node has a old version of the product.
3. The hostname resolution for the remote node has some issue and resolving to the different IP where the product is not installed.

Hi mr Sriniwasa, you were right for some reason it was disabled.... no idea why, but now i was able to deply :) Thank you!!

Jakob Agustsson , Thanks for the confirmation. Can you mark my suggestion as solution. This may help others with the same issue.

Hi! 

I have seen several times that the bootstrap service get stuck in Disabled if you perform a repair of your installation, or uninstall / modify components of your installation.
Could this be the case?

glad you managed to get it resolved, good catch by Jakob Agustsson !

 Richard Köhlerstrand  I agree with you on the reason why aaBootstrap could have been disabled. One clarification, actually its a good catch by me. The problem issue is from Jakob Agustsson and solution is by me!!  ha ha! just kidding. 

Looks like I have 2 accounts. But I prefer to go with this.

You are right! I was a little hasty there,

Credit where credit is due!

Thank you to "both" accounts ;)

And it is a nasty scenario since the errors that comes from this situation is not to helpful, so I do hope that this post finds anyone else with similar issue, and all of your suggestions are valid.

Hi Richard, that was exactly what I was doing, didn't expect to be disabled. I was uninstalling and re-installing historian to be exact.  Thank you so much for your help!

Hi Richard, that was exactly what I was doing, didn't expect to be disabled. I was uninstalling and re-installing historian to be exact.  Thank you so much for your help!