microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: Event Info

Subject: Re: Event Info
From: Joe Webb
Date: Wed, 29 Jun 2005 05:45:43 -0500
Newsgroups: microsoft.public.sqlserver.notificationsvcs
>The only reason for using FSW is to prototype our solution. It was very 
>frustrating to be stuck on what seemed the easy part.

Agreed on both counts!  :)   I know the feeling.



-- 
Joe Webb
SQL Server MVP


~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)


On Wed, 29 Jun 2005 03:39:01 -0700, "andyjax"
<[email protected]> wrote:

>The only reason for using FSW is to prototype our solution. It was very 
>frustrating to be stuck on what seemed the easy part.
>
>Thanks for the help. I will continue to build my prototype, and yes if I 
>change my XML data file to match the name in XSD it works.
>
>"Joe Webb" wrote:
>
>> The I read his post was that Andy had a typo in the sql:relation
>> attribute within the XSD.
>> 
>>    <xsd:element name="event" sql:relation="WrongStockEventsName">
>> 
>> Although I must admit it's been a while since I've used the FSW (and I
>> haven't verified it with a simple test), I believe that this would
>> cause what he was seeing.
>> 
>> What do you think, Shyam?
>> 
>> -- 
>> Joe Webb
>> SQL Server MVP
>> 
>> 
>> ~~~
>> Get up to speed quickly with SQLNS
>> http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 
>> 
>> I support PASS, the Professional Association for SQL Server.
>> (www.sqlpass.org)
>> 
>> 
>> 
>> 
>> On Tue, 28 Jun 2005 12:48:13 -0700, "Shyam Pather [MSFT]"
>> <[email protected]> wrote:
>> 
>> >Andy,
>> >The event schema file does not need to have the same name as the event 
>> >class - you just need to specify what the filename is in the event provider 
>> >configuration in the ADF.
>> >
>> >For future reference, you should get in the habit of looking in the 
>> >Application Event Log for error messages when NS doesn't do what you 
>> >expect. 
>> >All errors, warnings, status information etc. is written to the Application 
>> >Event Log (go to Adminstrative Tools/Event Viewer to see it).
>> >-shyam
>> 
>> 


<Prev in Thread] Current Thread [Next in Thread>