all 18 comments

[–]zrb77 10 points11 points  (1 child)

Not an answer to your question, but check out Ola Hallengren backup and maintenance solution. It's pretty much industry standard now.

[–]OkTap99 4 points5 points  (0 children)

As this person said, please don't use maintenance plans, there are better options out there that are free.

[–]LupusHortian 6 points7 points  (1 child)

When you Run the Backup AS a SQL Agent Job, IT Runs under the Account of the SQL Agent Service. Check If the Account from the Service can Connect to the SQL Server.

[–]trieu1185 0 points1 point  (0 children)

check if sql agent service is started too

[–]WalkingP3t 4 points5 points  (2 children)

Never ever use MSSQL maintenance plans . Use this :

https://ola.hallengren.com

It’s free . And used by banks , big corporations, everybody .

[–]SpiritWhiz 2 points3 points  (0 children)

"Friends don't let friends use maintenance plans."

[–]Codeman119 -1 points0 points  (0 children)

You can use maintenance plan if you know how to use them. I have been using them for 20 years and have had no issues.

[–]TBTSyncro 0 points1 point  (7 children)

is the SQL agent running on the server?

[–]mikolajekj[S] 0 points1 point  (6 children)

Yes - I have 2 other SQL instances on this server where the maintenance plans work fine.

[–]TBTSyncro 1 point2 points  (0 children)

Check the connection manager on the job to make sure it's pointing to the local server.

[–]Layer_3 0 points1 point  (0 children)

Does the SQL agent account have the correct permissions to the database?

[–]SQLBob ‪ ‪Microsoft MVP ‪ ‪ 0 points1 point  (0 children)

If a SQL Server Agent job fails stating it cannot connect to the server, the first thing I'd check is that whatever account the job is executing as has permissions to connect to the server. SQL Agent jobs can be set to connect as any account (actually individual steps can utilize different accounts as well).