In my case all attempts to follow the articles below failed. I traced it down to an installation of HP Web Jet Admin ver. 10 which uses a SQL instance. I uninstalled it and everything started working again.
- Error number: 4814, error message: "Login failed for user <user name>". The user is not associated with a trusted SQL Server connection" - See Event ID 18452 from source MSSQLSERVER.
In our case, the error was due to a SQL server instance that was disabled in the services snap-in. Per Symantec's instructions, we removed the disabled instance name from the InstalledInstances key in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server) and the error was resolved.
If the 0011 error is in reference to the "SBSMONITORING" database on a 2003 Small Business server, this is due to the integrated monitoring not being set up, so the associated service (MSSQL$SBSMONITORING) is disabled. Backup Exec sees it as a valid database but cannot connect to it (as per "Veritas TechNote ID: 274303"). I fixed this by running the "Monitoring Repors & Alerts" wizard from Server Management, configuring it for no e-mails and unchecking all the items to minimize any potential unnecessary activity. This enabled the service and the database, so Veritas was then able to properly ignore it as specified in my backup job.
- Error number: 0011, error message: "SQL Server does not exist or access denied" - See Veritas TechNote ID: 264616.
For more details check Veritas TechNote ID: 246587.