Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 Replication Agent and Notification

Author  Topic 

C_Hudson
Starting Member

1 Post

Posted - 2006-01-09 : 16:47:55
A newcomer to SQL Server, I have been working in a test environment in anticipation of going into production later this month.

I have established transactional replication of data (push) to a subscriber server, and was testing what happens when replication fails. I created a change in a record, verified that the change was propagated successfully, and then created another change to be propagated.

I understand that agent notification depends on operators and a configured MAPI interface. I have created operators, I have a MAPI interface which SQL says is working - Outlook 2003 is installed on the server - and have enabled what I think are the relevant alerts: agent failure and agent success. I have selected the operators for email distribution of the alerts.

To test the failure, I stopped the subscription server. Failure occurred, and was noted in the replication monitor, and in the system (Windows Server 2003) event log. No email was sent, however, nor was one sent on success in the occasions when replication was successful.

I tried installing Outlook 2000. That too was unsuccessful. I tried installing XPSMTP.dll. I tested that installation and verified that it worked, but the agent alert does not use it. I installed Db Maint SMTP Alerter, which uses XPSMTP to send an email after reading the log for existence of an error. That hasn't worked either.

I'm not sure what I've done wrong but I have two clues: First, the alert Agent Failure, eror # 14151, which is enabled and which I can see run, reports that it has never occurred. I don't know why. Second, while the system log (event viewer > application) reports the occurrence of an error 14151 promptly, within a minute or so of failure, while the SQL log takes longer to record the fact.

The easiest way out of this seems to use a system log event monitor enabled to send emails after searching for a particular error message. Does anyone have a recommendation for such an application?

Thanks for your responses.


Charles Hudson

jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2006-01-10 : 20:53:09
When you stopped the replication agents, the failure was not invoked unexpectedly but will be treated as normal stop (from what I've tried before)

If you want to propagate a failure, try to delete a record at the subscriber and then update that record from the publisher or make any changes on the subscriber. This will invoke an error and replication failure because all changes must be made on the publisher with regards to the articles.

If you want to catch these type of errors, you are correct, specify them.

As for email notification, I created an application that uses smtp.

HTH

--------------------
keeping it simple...
Go to Top of Page
   

- Advertisement -