I'm getting a connection error when I try to run even the most basic plan, fails with scheduled or manual runs.
The user is both a local-admin on all 3 nodes, and a SQL SA member. All engine processes and agent processes run-as that same AD account too. Everything works great (failovers etc), just the jobs won't run.
I even tried a FQDN on the hostname and a manual SQL-Login with the SA credentials in the job plan and that connection still didn't work.
I can run both SSMS and connect to the database locally and remotely without error with that AD account, but running the jobs: no luck.
Instance name is default MSSQLSERVER for all replicas, in a primary+1 synchronous-commit for all 3 nodes (15.0.4003.23)
All the databases are fully synched.
Prod is configured the same (but without HA) and the backup jobs work fine.
I'm fairly certain it would run, if it could somehow successfully connect.
Error Msg as per Job history:
Executed as user: DomainName\DEV-SQL-HA. Microsoft (R) SQL Server Execute Package Utility Version 15.0.2000.5 for 64-bit Copyright (C) 2019 Microsoft. All rights reserved. Started: 2:46:06 PM Could not load package "Maintenance Plans\Test" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.). The SQL statement that was issued has failed. Source: Started: 2:46:06 PM Finished: 2:46:06 PM Elapsed: 0.188 seconds. The package could not be loaded. The step failed.
I even thought it was the job's complexity so I simplified to just a single step basic file del cleanup task and even that didn't help any:
EXECUTE master.dbo.xp_delete_file 0,N'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Backup\Daily',N'bak',N'2019-12-31T14:53:57'
If I manually run a backup to the same path that is successful, so it's not a file-path or file-permission thing.
BACKUP DATABASE [DEV_SensorsDB] TO
DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Backup\Daily\fdsa2.bak'
WITH COPY_ONLY, NOFORMAT, NOINIT, NAME = N'DEV_SensorsDB-Full Database Backup',
SKIP, NOREWIND, NOUNLOAD, STATS = 10
Processed 616 pages for database 'DEV_SensorsDB', file 'Sensors' on file 2.
80 percent processed.
90 percent processed.
100 percent processed.
Processed 246 pages for database 'DEV_SensorsDB', file 'Sensors_log' on file 2.
BACKUP DATABASE successfully processed 862 pages in 0.470 seconds (14.320 MB/sec).
Completion time: 2020-01-28T15:04:05.5541443-08:00
I'm out of ideas...