02-18-2008 07:16 PM
I'm getting errors in my application log from BE 11 that in my opinion should never be occurring. I have ACT! 2008 installed with its own named instance and this is not selected in the selections list (unchecked). I do not have this excluded in any other way. Although this is effectively benign, this is on a SBS 2003 box and the daily reporting always shows these errors and I have to check these everyday (i.e. it would be nice to have no alerts and since BE11 is causing this to have a non-clean bill of health when in fact it should never be touching them I'm more than a little concerned).
(errors detailed @ end of post)
It seems that BE11 is pre-scanning and effectively disregarding that it should not be touching this database in any way (the errors show up twice - once about 1 minute after the job starts and the second time about 5 minutes into the job - hence my comment that this is a credentials check or a prescan). In either case, to prescan or attempt to open a non-selected SQL instance is not good (in my eyes this is a major issue/"bug"/whatever you want to call it). A program by any other name would be called malware for doing this. Anyway, I'm trying to at worst find a workaround to remove the occurrence of these errors so that my reports (as they should) show a clean bill of health.
BE11 is liveupdated to the latest version.
Source
Event ID
Last Occurrence
Total Occurrences
Backup Exec
57860
2/17/2008 10:04 PM
2 *
An error occurred while attempting to log in to the following server: "hidden". SQL error number: "4818". SQL error message: "Login failed for user 'hidden\Administrator'. ". For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Source
Event ID
Last Occurrence
Total Occurrences
MSSQL$ACT7
18456
2/17/2008 10:04 PM
2 *
Login failed for user 'hidden\Administrator'. [CLIENT: a.b.c.d]
02-19-2008 07:38 AM
02-19-2008 08:22 AM
02-20-2008 05:53 AM