Same here. How do I resolve this?
The on-access driver failed to determine the name for a file. [e03d0056] seems of little use.
I would suggest to suppress it: e03d0056 as a 32-bit signed dec is: -532873130.
There is a table in the 'core' database called: "ErrorAlertFilters"; you could try using this to filter it out in the future, for example the command (admin prompt):
sqlcmd -E -S .\sophos -d SOPHOS550 -Q "INSERT INTO ErrorAlertFilters (Source, Number) VALUES ('SAV', '-532873130') "
I have assumed a default local Sophos instance (.\sophos) is being used and SEC 5.5, hence the SOPHOS550 database name.
For more details on the database name see: https://community.sophos.com/kb/en-us/17323
For locating the instance of SQL in use by SEC see: https://community.sophos.com/kb/en-us/113030
This will prevent the "SAV" message being displayed in SEC in the future if you acknowledge the current ones.
Hopefully that helps.
Regards,
Jak
The on-access driver failed to determine the name for a file. [e03d0056] seems of little use.
I would suggest to suppress it: e03d0056 as a 32-bit signed dec is: -532873130.
There is a table in the 'core' database called: "ErrorAlertFilters"; you could try using this to filter it out in the future, for example the command (admin prompt):
sqlcmd -E -S .\sophos -d SOPHOS550 -Q "INSERT INTO ErrorAlertFilters (Source, Number) VALUES ('SAV', '-532873130') "
I have assumed a default local Sophos instance (.\sophos) is being used and SEC 5.5, hence the SOPHOS550 database name.
For more details on the database name see: https://community.sophos.com/kb/en-us/17323
For locating the instance of SQL in use by SEC see: https://community.sophos.com/kb/en-us/113030
This will prevent the "SAV" message being displayed in SEC in the future if you acknowledge the current ones.
Hopefully that helps.
Regards,
Jak