Elasticsearch service fails in Microsoft Team Foundation Server after upgrade from TFS 2017 to 2018

Posting here at Elissa J's request after initial email exchange.

We recently upgraded an installation of Microsoft Team Foundation Server (TFS) running on Windows Server 2016 Standard from TFS 2017 to TFS 2018. The upgrade required first uninstalling the Elasticsearch windows service, which we did successfully using the following batch command in the bin folder for elastic search 2.4.1.

service.bat remove

Once the TFS upgrade was complete, the service was again present (Elasticsearch 2.4.1 (elasticsearch-service-x64)), but it was not running. Startup Type was set to "Automatic (Delayed Start)". Starting the service appeared to start it, but refreshing the service list showed it was not running. There are no event log entries and no other evidence of error. The service will not start. Additionally, the executable path in the service settings is correct. It has the following switch: //RS//elasticsearch-service-x64

Is there any insight as to why? Are there any troubleshooting steps I can take to diagnose and resolve this issue?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.