FAST ESP installation system checks for the following
1. Machine is ping-able
2. All 4000 ports from 13000 to 16999 are free
3. Rest checks such as Java installed, directory exists etc…
Now the interesting part, all system checks succeeded and installation succeeded with 0 errors. Spent another hour to install all the patches, only to find the ESP failing to create a collection and default views.
The following error is thrown
Failed to deploy views '[oursite, espsystemwebcluster]' (deployment id: 1956). Failed to perform deployment transaction. Deployment failed: Could not deploy resource 'no.fast.messages.resourceservice.ResourceHandle@2c91b364'
The above error gave a hint on communication error while deploying the resource files for collection creation. But did not get convinced as the system status showing as follows
Later I started searching over microsoft support site for the resolution for this issue, glad to find the issue suggesting restarting the ESP solves the issue, happily restarted but no luck!!!!.
After a day of analyzing the issue which includes uninstall and reinstallation of FAST ESP, finally decided to open a ticket with Microsoft. Before opening the ticket, I executed on all 4 servers ipconfig to collect the network information BINGOOO…. Except one server rest are all having the 10.1.x.x, the other server showed 169.x.x.x. Network folks immediately recognized this IP is incorrect.
What I am going to write below FAST documentation has to include it in the installation guide
From windows millennium edition onwards Microsoft assigns an automatic IP address for the enabled network adapters. With automatic IP addressing, the IP address can be configured automatically. This method decreases administration time and means that IP addresses can be reused. Also, this method is recommended for all sizes of networks that do not have a direct Internet connection or available DHCP service.
Please check the link below
http://support.microsoft.com/kb/307287
http://support.microsoft.com/kb/956196
Resolution:
Just disabled all the adapters except the adapter holding the static IP, solved the issue!!!!!
