Hi,

I need to prepare the reports in excel sheet and send it as part of
notification message.

As the current notification (Built in SMTP Delivery protocol) doesn't
support attachments, I am creating a cursom delivery protocol (implementing
IDeliveryProtocol) to send a email with attachments using CDO(Microsoft CDO
For Exchange 2000 Library).

When I make the necessary changes in appconfig, appADF files and start the
service, I am not getting any emails.

No error was logged in the event log.

When I started debugging the custom delivery protocol , I am getting the
control in Initialize method. I am able to see the all the parameters. Then
the control goes the Flush and Close method. The control never comes to
DeliverNotification method.

What could be the problem.?

Thanks.

Regards,
R.Balaji

Balaji,
This looks like the classic subscriber devices not configured correctly
problem. A few questions:

1. Do you have a delivery channel defined that uses your custom protocol?
2. Are your subscriptions associated with subcriber devices configured for
the delivery channel that uses your custom protocol?
3. Are you provinding the correct "DeviceName" value in your match rule?
4. Have you added a configuration section for your new protocol in the
relevant <NotificationClass> definitions in your applications?

1, 2, and 3 are probably the cause of your problem. To expand upon #3:

In the Notifications table NS<NotificationClassName>Notifications, there are
columns for SubscriberID and DeviceName. Are you certain that, for the
notifications you're looking at, the [SubscriberId, DeviceName] pair matches
a valid record in the NSSubscriberDevices table in the Instance
(<InstanceName>NSMain) database?

If your notifications specify non-existent or invalid subscriber device
names, the distributor will not route them to the proper delivery protocol.
-shyam


--
Learn more about SQL-NS:
http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/
---------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
---------------------------------------------
[quoted text, click to view]

[quoted text, click to view]
the delivery channel that uses your custom protocol?

That was the issue.

While adding the subscriber, I was refering the default SMTP protocol and I
expect the service to deliver the notification to my protocol.

We were fully worried about the appADF.xml and appconfig.xml file.
We completely forgot the subscription module part.

Thanks shyam to point it out correctly.

Regards,
R.Balaji




[quoted text, click to view]