Post reply

SQL Log error 14150,Severity 10, State 1

  • June 11, 2002 at 10:13 am

    #57840

    Recently we have lines of 'error 14150,Severity 10, State 1' showing in SQL log. They showed while every replication(snap or merge) job is running. Actually these errors are reporting 'Replication-Snapshot agent XXXX-31 successed' but annoying us. I post part of error lines here:

    2002-06-10 03:50:07.68 spid23 Replication-Snapshot: agent DB2000-GradGuide-GradGuidePub-31 succeeded. A sna

    2002-06-10 03:50:07.68 spid23 Error: 14150, Severity: 10, State: 1

    2002-06-10 04:00:20.42 spid53 Replication-Distribution: agent DB2000-GradGuide-DIGEXWEBDB-35 succeeded. App

    2002-06-10 04:00:20.42 spid53 Error: 14150, Severity: 10, State: 1

    2002-06-10 04:00:34.46 spid23 Replication-Distribution: agent DB2000-ProServe-KOPL380150-14 succeeded. Appl

    2002-06-10 04:00:34.46 spid23 Error: 14150, Severity: 10, State: 1

    All spid are the logins to invoke the agent(s). We are using SQL 7 sp2 on Windows NT 4 sp6.

    Any help appreciated!

  • June 11, 2002 at 3:00 pm

    #430681

    Is it possible that someone recently setup a Severity 10 Alert in Sql Agent?

    I believe that even if thier isn't an alert action setup it will still log errors in the error log file.

  • June 11, 2002 at 6:06 pm

    #430696

    Check under SQL Agent in EM in the Alerts section. The alert that outputs this message may be turned on and can be disabled. I made this mistake originally when I was have it do net send alerts to me and had it enabled as well.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • June 12, 2002 at 7:22 am

    #430721

    Both of your ideas are right. The alert 'Replication Agent success' is turned on somehow so it reports 'succeess...' error msg.

    Big thanks!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply