AbandonAllHope 0 Posted December 16, 2015 Share Posted December 16, 2015 Running ESET for Exchange version 6.2 with Exchange 2013. Used the ESET GUI to create a scheduled database scan. The scan fails with "Database scan could not be started. Scan account not set." in the ESET log files. The 6.2 install nor the schedule setup requested any Account. Anyone else having this issue. Link to comment Share on other sites More sharing options...
Administrators Marcos 3,890 Posted January 1, 2016 Administrators Share Posted January 1, 2016 You can set the account (username/password) for database scans under Server -> On-demand database scan in the advanced setup. Link to comment Share on other sites More sharing options...
AbandonAllHope 0 Posted January 8, 2016 Author Share Posted January 8, 2016 Thank you. Link to comment Share on other sites More sharing options...
Recommended Posts