That looks like a good start. You may need to cast the file line as a string first though
exists file “D:\Program Files\BigFix Enterprise\BES Relay\logfile.txt” whose (exists lines whose (it as string contains “GetExpectedVersionOfParent Error: Parent response did not contain a site version”) of it)
Of course, try that in the fixlet debugger first.
Unless all of your relays use the same installation path, you shouldn’t hard-code the “D:\Program Files…” path. There is a client setting that tracks the path of the relay files, which could make this work cross-platform (Windows and Linux relays).
Also, note that after doing whatever you are doing to fix it, you’d need to move or clear the log file - after the relay restarts, it would still have the older messages in the log.
And, by default, the relay log continues to grow, it’s not auto-rotated, so when the file grows large enough this relevance may evaluate very slowly.
I’m not sure that this message always indicates a problem though. I think that can be expected if the parent relay has not yet gathered a version of the site (and the parent should begin a gather based on this child relay’s request, and have the site available later). Also, there are cases such as “a new operator has been created but has never logged on or sent an action” in which the operator site has not been created yet, so this message may repeat for some operator sites. You may need to find a more specific message for which to search, you might find thid message on relays that are working fine.