"Joe Webb" <joew@webbtechsolutions.com> wrote in message
news:ODECXnblEHA.1356@TK2MSFTNGP09.phx.gbl...
> Of course, you should make sure that an accurate subscription has been
> created. If you inadvertantly specified the wrong device in your
> subscription, everything would appear to work, but no notifications
> would/could be delivered.
>
> HTH...
> Joe Webb
>
> Joe Webb wrote:
>
> > Hi Zatoichi -
> >
> > A few things to check:
> >
> > - If there is an error in your transform (.xslt) file, notifications
> > will not be produced. Make sure you transform file is free from errors.
> >
> > - Does the c:\test folder exist? Does the service account have
> > permissions to write to the c:\test folder?
> >
> > HTH...
> >
> > Joe Webb
> >
> >
> >
> > Zatoichi wrote:
> >
> >> I can't get NS to even write to a simple text file.
> >>
> >> I get the message below in my Notifications table:
> >> "Delivery never attempted: first try pending" or "Delivery failed ".
> >> Can someone take a look at my Config and ADF excerpts and point me in
> >> the right direction?
> >>
> >> Thanks in advance.
> >>
> >> Configuration file:
> >>
> >> <DeliveryChannel>
> >> <DeliveryChannelName>FileChannel</DeliveryChannelN
> >> ame>
> >> <ProtocolName>File</ProtocolName>
> >> <Arguments>
> >> <Argument>
> >> <Name>FileName</Name>
> >> <Value>C:\test\Results.txt</Value>
> >> </Argument>
> >> <Argument>
> >> <Name>Encoding</Name>
> >> <Value>utf-8</Value>
> >> </Argument>
> >> </Arguments>
> >> </DeliveryChannel>
> >>
> >> From the ADF:
> >>
> >> <ContentFormatter>
> >> <ClassName>XsltFormatter</ClassName>
> >> <Arguments>
> >> <Argument>
> >> <Name>XSLTBaseDirPath</Name>
> >> <Value>C:\Test</Value>
> >> </Argument>
> >> <Argument>
> >> <Name>XSLTFileName</Name>
> >> <Value>My_format.xslt</Value>
> >> </Argument>
> >> </Arguments>
> >> </ContentFormatter>
> >> <DigestDelivery>false</DigestDelivery>
> >> <Protocols>
> >> <Protocol>
> >> <ProtocolName>File</ProtocolName>
> >> </Protocol>
> >> ...
> >>
> >> Here are some Event warnings I received:
> >>
> >> The processing of a work item was aborted due to too many consecutive
> >> failures on the delivery channel.
> >> EventParameters:
> >> Distributor Work Item Id: 345
> >> Delivery Channel Name: FileChannel
> >>
> >> InstanceName: MyInstance
> >> ApplicationName: Programs
> >> Component: Distributor
> >> ComponentDetails: DistributorName: ProgramsDist1
> >> Thread: 5
> >>
> >> A delivery failure was reported.
> >> EventParameters:
> >> Distributor Id: 1
> >> Distributor Name: ProgramsDist1
> >> Delivery Channel Name: FileChannel
> >> Notification Id: 95798
> >> NotificationClassName: CampusNewNotifications
> >> Notification Status Info: Notification Text: Notification Sent
> >> Time: 9/7/2004 5:32:01 AM
> >>
> >> InstanceName: MyInstance
> >> ApplicationName: Programs
> >> Component: Distributor
> >> ComponentDetails: DistributorName: ProgramsDist1
> >> Thread: 5
> >>
> >> The distributor is processing a notification.
> >> EventParameters:
> >> Distributor Work Item Id: 345
> >> Notification Id: 95798
> >>
> >> InstanceName: MyInstance
> >> ApplicationName: Programs
> >> Component: Distributor
> >> ComponentDetails: DistributorName: ProgramsDist1
> >> Thread: 5
> >>

>-----Original Message-----
>Also, there should be error messages in the Application
event log
>corresponding to each delivery failure. Those error
message will describe
>the reason the delivery protocol was unable to deliver
the notification.
>-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.
>---------------------------------------------
>"Joe Webb" <joew@webbtechsolutions.com> wrote in message
>news:ODECXnblEHA.1356@TK2MSFTNGP09.phx.gbl...
>> Of course, you should make sure that an accurate
subscription has been
>> created. If you inadvertantly specified the wrong
device in your
>> subscription, everything would appear to work, but no
notifications
>> would/could be delivered.
>>
>> HTH...
>> Joe Webb
>>
>> Joe Webb wrote:
>>
>> > Hi Zatoichi -
>> >
>> > A few things to check:
>> >
>> > - If there is an error in your transform (.xslt)
file, notifications
>> > will not be produced. Make sure you transform file
is free from errors.
>> >
>> > - Does the c:\test folder exist? Does the service
account have
>> > permissions to write to the c:\test folder?
>> >
>> > HTH...
>> >
>> > Joe Webb
>> >
>> >
>> >
>> > Zatoichi wrote:
>> >
>> >> I can't get NS to even write to a simple text file.
>> >>
>> >> I get the message below in my Notifications table:
>> >> "Delivery never attempted: first try pending"
or "Delivery failed ".
>> >> Can someone take a look at my Config and ADF
excerpts and point me in
>> >> the right direction?
>> >>
>> >> Thanks in advance.
>> >>
>> >> Configuration file:
>> >>
>> >> <DeliveryChannel>
>> >>
<DeliveryChannelName>FileChannel</DeliveryChannelN
>> >> ame>
>> >> <ProtocolName>File</ProtocolName>
>> >> <Arguments>
>> >> <Argument>
>> >> <Name>FileName</Name>
>> >> <Value>C:\test\Results.txt</Value>
>> >> </Argument>
>> >> <Argument>
>> >> <Name>Encoding</Name>
>> >> <Value>utf-8</Value>
>> >> </Argument>
>> >> </Arguments>
>> >> </DeliveryChannel>
>> >>
>> >> From the ADF:
>> >>
>> >> <ContentFormatter>
>> >> <ClassName>XsltFormatter</ClassName>
>> >> <Arguments>
>> >> <Argument>
>> >> <Name>XSLTBaseDirPath</Name>
>> >> <Value>C:\Test</Value>
>> >> </Argument>
>> >> <Argument>
>> >> <Name>XSLTFileName</Name>
>> >> <Value>My_format.xslt</Value>
>> >> </Argument>
>> >> </Arguments>
>> >> </ContentFormatter>
>> >> <DigestDelivery>false</DigestDelivery>
>> >> <Protocols>
>> >> <Protocol>
>> >> <ProtocolName>File</ProtocolName>
>> >> </Protocol>
>> >> ...
>> >>
>> >> Here are some Event warnings I received:
>> >>
>> >> The processing of a work item was aborted due to
too many consecutive
>> >> failures on the delivery channel.
>> >> EventParameters:
>> >> Distributor Work Item Id: 345
>> >> Delivery Channel Name: FileChannel
>> >>
>> >> InstanceName: MyInstance
>> >> ApplicationName: Programs
>> >> Component: Distributor
>> >> ComponentDetails: DistributorName: ProgramsDist1
>> >> Thread: 5
>> >>
>> >> A delivery failure was reported.
>> >> EventParameters:
>> >> Distributor Id: 1
>> >> Distributor Name: ProgramsDist1
>> >> Delivery Channel Name: FileChannel
>> >> Notification Id: 95798
>> >> NotificationClassName: CampusNewNotifications
>> >> Notification Status Info: Notification Text:
Notification Sent
>> >> Time: 9/7/2004 5:32:01 AM
>> >>
>> >> InstanceName: MyInstance
>> >> ApplicationName: Programs
>> >> Component: Distributor
>> >> ComponentDetails: DistributorName: ProgramsDist1
>> >> Thread: 5
>> >>
>> >> The distributor is processing a notification.
>> >> EventParameters:
>> >> Distributor Work Item Id: 345
>> >> Notification Id: 95798
>> >>
>> >> InstanceName: MyInstance
>> >> ApplicationName: Programs
>> >> Component: Distributor
>> >> ComponentDetails: DistributorName: ProgramsDist1
>> >> Thread: 5
>> >>
>
>
>.