05-03-2019 07:38 AM - edited 02-20-2020 09:08 PM
We updated AMP Connector on a server Monday night to 6.2.19, Tuesday morning the users starting having issues who use a database utility to import from one database on one server, to another one with the issue. Exclusions for this software have already been added previously.
This didn't occur until after the connector was updated on Monday. I attached the install logs from the programdata folder.
I had to uninstall this from the affected server because it is impacting production. I already tried disabling the tetra engine and it didn't change anything. Please help.
Thanks,
Chris
05-04-2019 07:52 AM
I recommend opening a TAC case immediately. For production-affecting issues on a licensed installation, the TAC is always the best bet.
Cisco community can be quite helpful at times but we are primarily volunteers making best-effort answers in our spare time.
05-16-2019 02:25 PM
I'm curious about your exclusions. Do they include the parent process and apply to all child process's ?
05-27-2019 10:20 AM
Hello,
you may test this tool to analyse a connector Diagnostic file to see which files are scanned.
https://github.com/CiscoSecurity/amp-05-windows-tune
Greetings,
Thorsten
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: