All of our Windows clients are firing the following log entry in the endpoint security platform error.log
mfeesp(7880.10420) <SYSTEM> GTIBL.GTI.Error (GTIImpl.cpp:644): TS_RateConnection failed. Returned = 1
We just recently made some changes to our FW and EP policies. The first error we saw after these changes were this.
mfetp(6312.7944) <SYSTEM> BoBl.NIPS.Error (NIPS:0): [k] @Invalid signature function index: 0xffffffff
This was learned to be caused by an out of date EP content version, which stopped firing after we pushed out an update. When we fixed the NIPS logging, the GTI logging above started.
Any ideas? We have an SR open as well but havent had luck just yet and would really like to get this resolved asap.
Solved! Go to Solution.
Hi @lerrico,
Thank you for your post. ESP errors are meant for troubleshooting purposes from support and Engineering end as it contains modules that are not yet activated but will be in future releases as well. hence the logging information could be superfluous and may not be entirely useful to us. We would request you to ignore the same.
Having said that, As @patrakshar mentioned, you can report the functional issue here so that we can investigate the same accordingly.
If you are worried about GTI connectivity, you can always perform the Artemis test and let us know if you find an issue on the same.
https://kc.mcafee.com/corporate/index?page=content&id=KB53733
I sincerely hope this helps!
Hi @lerrico
Thanks for posting here. I would like to know what is the functionality issue you have for which this log has been checked. Can you please explain what exactly the functionality issue you have with ENS on the machine?
We don't seem to have any functionality issues. We updated the EP content version which cured one log, and then immediately afterwards the GTI error log stared. The only changes we made were to the GTI sensitivity in our FW policy and turned on NIPS in the EP policy.
Hi @lerrico,
Thank you for your kind response. In that case, I would recommend ignoring the errors as they are meant only for support and Engineering to troubleshoot during functional issues.
Hi @lerrico,
Thank you for your post. ESP errors are meant for troubleshooting purposes from support and Engineering end as it contains modules that are not yet activated but will be in future releases as well. hence the logging information could be superfluous and may not be entirely useful to us. We would request you to ignore the same.
Having said that, As @patrakshar mentioned, you can report the functional issue here so that we can investigate the same accordingly.
If you are worried about GTI connectivity, you can always perform the Artemis test and let us know if you find an issue on the same.
https://kc.mcafee.com/corporate/index?page=content&id=KB53733
I sincerely hope this helps!
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA