Forums

[mingleforum]

Comments (2)

  • Idana

    |

    Your article perfectly shows what I needed to know, tankhs!

    Reply

  • namanthakral

    |

    got errors after executing this trigger
    “SQL SERVER – Fix : Error : 17892 Logon failed for login due to trigger execution. Changed database context to ‘master’.”

    and was really stucked in this mess but DAC saved my life
    C:\Users\Administrator>sqlcmd -S LocalHost -d master -A
    1> DROP TRIGGER block_ipaddress ON ALL SERVER
    2> go

    Reply

Leave a comment

CAPTCHA Image
*

Recent Comments

Amit Bhatt

|

Hi Deepak,

Thanks for such a nice article.

You missed one thing to add in code:
@article = ‘all’,

Hence the script will be like this:
EXEC sp_addsubscription
@publication = ‘mypublication’,
@article = ‘ALL’,
@subscriber = ‘Subscriberservername’,
@destination_db = ‘mydestinationdbname’,
@reserved=’Internal’

Error 18486 | Platformblog

|

[...] SQL-Articles » Troubleshooting Login failed Error 18456This is one of the infamous error message (and number) that most of the DBAs …. 18486. Login failed for user ‘%.*ls’ because the account is currently locked out. [...]

VidhyaSagar

|

Naveen,
I’ll check this out and get back to you.

balakiran

|

Thanks man, Very simple & easy to understand !!!!

Rating