0

We have some older maintenance plans that were built with SSMS 2014 on a Sql Server 2014 instance. The connection defined for the plan uses a Sql Server account with sysadmin perms. When you edit with SSMS 2014, all works just fine. On my local box, I have SSMS 2016, also have sysadmin perms. When I edit the plan, the "Notify Operator Task" has a blue indicator that something is wrong

Error

When I try to edit the task, I get the following error: enter image description here

The sql error log shows the following errors:

Error: 18456, Severity: 14, State: 8.
Login failed for user 'SqlAccount'. Reason: Password did not match that for the login provided. [CLIENT: xx.x.x.x]

The SqlAccount is the one defined in my "manage connections" from the maintenance plan. Is there some new permission that SSMS 2016 needs? Are plans created in SSMS 2014 not fully compatible with the SSMS 2016 editor?

Improve this question
5
  • Are you using version 13.0.15600.2?
    – Antoine Hernandez
    Commented Jul 20, 2016 at 17:13
  • I am not. I will update when I get the chance and retest my issue.
    – HunterX3
    Commented Jul 20, 2016 at 17:16
  • I updated SSMS to that version. Error still occurs.
    – HunterX3
    Commented Jul 21, 2016 at 14:50
  • I think the blue indicator is just the way the icon looks in the new SSMS version; it doesn't necessarily mean anything is wrong as the icons changed with SSMS switching from VS 2010 to VS 2015 shell. In trying to reproduce your steps, I created a plan on a 2014 server with the 2014 SSMS with the Notify Operator Task. I then saved this plan and opened it on the 2016 SSMS and had no issues. What version SQL Server 2014 are you using? I'm using 12.0.5000. Other than that, the only thing I can think of is wrong password stored for SqlAccount user in connection.
    – Antoine Hernandez
    Commented Jul 24, 2016 at 18:20
  • Antoine, Thanks for testing. My SSMS 2014 version is 12.0.4439.1. However, I am unsure now, what version of SSMS was used to create the plan. Maybe it was older? I know there are known issues with old SSMS version plans.
    – HunterX3
    Commented Jul 25, 2016 at 14:31

1 Answer 1

Reset to default
1

In your maintenance plan's "Manage Connections" define a new connection with integrated Windows authentication. Use that connection with your Notify Operator Task (set it here right-clik->Properties->Connection) and it should work.

Improve this answer
1
  • That worked, thanks. Do you have an explanation?
    – HunterX3
    Commented Aug 23, 2016 at 18:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.