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

Re: Error while initialising Custom Event Provider

Subject: Re: Error while initialising Custom Event Provider
From: "Chris"
Date: Thu, 9 Jun 2005 05:11:03 -0700
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Hi Joe,

Thanks for the explanation. For this project I can use v1.0 of the Framework 
for the subscription app so no problems once I change the referenced 
Framework version.

Very helpful!

Thanks again,

Chris

"Joe Webb" wrote:

> Chris - 
> 
> Here's an excerpt from the SQLNS readme file that explains .net
> framework versioning when building custom components.
> 
> 
> -----------------------------------------------------------
> 4.15 Using Custom Components Built With Version 1.1.4322 of 
>      the .NET Framework
> -----------------------------------------------------------
> Notification Services 2.0 SP1 is built using the 1.0.3705 
> version of the .NET Framework. By default, Notification 
> Services attempts to load and use this version. If a custom 
> component is built using version 1.1.4322 of the .NET 
> Framework, this version is also loaded. When Notification 
> Services and the component use different versions of the .NET 
> Framework, differences in the class libraries can cause 
> application errors, such as the following:
> 
>  * 2009: Notification Services failed to instantiate the event 
>          provider.
>  * 6005: The assembly does not contain the required content 
>          formatter class.
> 
> To resolve these errors, build custom components using version 
> 1.0.3705 of the .NET Framework. To do this, add the directory 
> containing the 1.0.3705 assemblies to the references path for 
> the custom components project.
> 
> If you must build custom components with version 1.1.4322 of the
> ..NET Framework, you can force Notification Services to use the 
> same version. To do this, add a <startup> node to the 
> NSService.exe.config file, which is in the vN.N.N.N\Bin folder 
> of Notification Services. The following example shows the file 
> with the <startup> node:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration>
>     <startup>
>         <supportedRuntime version="v1.1.4322"/>
>         <supportedRuntime version="v1.0.3705"/>
>     </startup>
>     <system.diagnostics>
>         <switches>
>             <add name="LogAdministrative" value="2"/>
>             <add name="LogService" value="2"/>
>             <add name="LogEventProvider" value="2"/>
>             <add name="LogEventCollector" value="2"/>
>             <add name="LogGenerator" value="2"/>
>             <add name="LogDistributor" value="2"/>
>             <add name="LogVacuumer" value="2"/>
>             <add name="LogOther" value="2"/>
>             <add name="LogPerformanceMonitor" value="2"/>
>         </switches>
>     </system.diagnostics>
> </configuration>
>     
> The <supportedRuntime> elements restrict the versions of the 
> ..NET Framework that Notification Services can use. The order of 
> the listed versions determines the order in which Notification 
> Services attempts to load the .NET Framework versions. In the 
> example above, Notification Services will first attempt to load 
> version 1.1.4322 of the .NET Framework. If it is not available, 
> Notification Services will attempt to load version 1.0.3705 of 
> the .NET Framework. 
> 
> You must restart the NS$<instance_name> service to apply changes 
> made to NSService.exe.config. 
> 
> 
> HTH...
> 
> 
> -- 
> 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 Thu, 9 Jun 2005 00:29:02 -0700, "Chris"
> <[email protected]> wrote:
> 
> >Microsoft.SqlServer.NotificationServices.dll was compiled against v1.0.3705 
> >of the Framework
> >
> >"Chris" wrote:
> >
> >> Anyone know of the top of their head why version 1.1 of the Framework 
> >> doesn't 
> >> work?
> >> 
> >> "jplankala" wrote:
> >> 
> >> > This was due to the .NET framework version which I was using to develop 
> >> > the 
> >> > event provider.  I made the configuration changes for this and resolved 
> >> > t.
> >> > 
> >> > Thanks.
> >> > 
> >> > Jplankala
> >> > 
> >> > "jplankala" wrote:
> >> > 
> >> > > I am trying to use a custom hosted event provider.I have implemeted 
> >> > > all the 
> >> > > methods of the interface "IScheduledEventProvider " in the new 
> >> > > Provider.  
> >> > > When I try to start the service it is failing to initialise the 
> >> > > Provider. The 
> >> > > error log is given belowplease. Please help me to resolve this.
> >> > > 
> >> > > <NotificationServicesEvent>
> >> > >        <Description>
> >> > >                Notification Services failed to instantiate the event 
> >> > > provider.
> >> > >        </Description>
> >> > >        <Context>
> >> > > <EventParameters>
> >> > >        <ProviderName>TestEventProvider</ProviderName>
> >> > >        <ProviderAssembly>C:\temp\HostedEvent.dll</ProviderAssembly>
> >> > >        <ProviderClassName>HostedEvent.TestEvent</ProviderClassName>
> >> > > </EventParameters>
> >> > > 
> >> > >        </Context>
> >> > >        <Description>
> >> > >                Method Initialize in type HostedEvent.TestEvent from 
> >> > > assembly Initialize 
> >> > > does not have an implementation.
> >> > >        </Description>
> >> > >        <Instance>RealtorInstance</Instance>
> >> > >        <ApplicationName>Realtor</ApplicationName>
> >> > >        <Component>Event provider host</Component>
> >> > >        <Thread>43</Thread>
> >> > > </NotificationServicesEvent>
> >> > > 
> >> > > JPlankala
> 
> 

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