Event sinks stop firing
Exchange Server Forum Index Exchange Server
Discussion forums for Microsoft Exchange Server users.
Microsoft Outlook
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web ExchangeServerHelp.com
Event sinks stop firing

 
Post new topic   Reply to topic    Exchange Server Forum Index -> Development
Author Message
Sorry
Guest





Posted: Mon Oct 17, 2005 4:57 pm    Post subject: Event sinks stop firing Reply with quote

Hi,

Sometimes the async eventsink on a user calendar stops firing.
Deleting and recreating the eventsink item in the calendar fixes the situation.

Windows Server 2003
Exchange server 2003 SP1
Outlook 2003 SP1

no eventlog errors.

Is this a known Exchange server bug?
Any way to troubleshoot this?

thanks,
John

Back to top
Joe Richards [MVP]
Guest





Posted: Mon Oct 17, 2005 4:58 pm    Post subject: Re: Event sinks stop firing Reply with quote

Have the sink output debugstrings to let you know where it is at at all times,
most likely the sink is hanging in a bad section of code.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Sorry wrote:
Quote:
Hi,

Sometimes the async eventsink on a user calendar stops firing.
Deleting and recreating the eventsink item in the calendar fixes the
situation.

Windows Server 2003
Exchange server 2003 SP1
Outlook 2003 SP1

no eventlog errors.

Is this a known Exchange server bug?
Any way to troubleshoot this?

thanks,
John
Back to top
Sorry
Guest





Posted: Mon Oct 17, 2005 11:50 pm    Post subject: Re: Event sinks stop firing Reply with quote

Thanks for your suggestion Joe. However I don't think that's the case.
The sink simply passes the item url to a com+ dll to do it's thing.
As it is async there is nothing to keep it hanging... the sync is not
waiting for the process to finish.
the com+ component is multi-instance.. even if one instance would hang (and
it that was not an observation), other instances are available to process
the request.

I see this behavior on one out of maybe 10 to 15 exchange servers. reboot
won't help.. after republishing the sink item it will work for a while..
days.. weeks and it's broken again.
maybe it has something to do with one of the outlook client builds.. cached
mode maybe?


"Joe Richards [MVP]" <humorexpress@hotmail.com> wrote
news:OPQsO5y0FHA.2428@tk2msftngp13.phx.gbl...
Quote:
Have the sink output debugstrings to let you know where it is at at all
times, most likely the sink is hanging in a bad section of code.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Sorry wrote:
Hi,
Sometimes the async eventsink on a user calendar stops firing.
Deleting and recreating the eventsink item in the calendar fixes the
situation.
Windows Server 2003
Exchange server 2003 SP1
Outlook 2003 SP1
no eventlog errors.
Is this a known Exchange server bug?
Any way to troubleshoot this?
thanks,
John


Back to top
Mailing Lists
Guest





Posted: Tue Oct 25, 2005 4:58 pm    Post subject: Re: Event sinks stop firing Reply with quote

We have seen similar behavior with an event sink running in a public
folder. Are you sure this only occurs on specific Exchange servers?
Are there any observable differences between the servers it works on
and those it doesn't? Could you you send me your code? I'd be
interested to see what else we have in commmon.

Sorry wrote:
Quote:
Thanks for your suggestion Joe. However I don't think that's the case.
The sink simply passes the item url to a com+ dll to do it's thing.
As it is async there is nothing to keep it hanging... the sync is not
waiting for the process to finish.
the com+ component is multi-instance.. even if one instance would hang (and
it that was not an observation), other instances are available to process
the request.

I see this behavior on one out of maybe 10 to 15 exchange servers. reboot
won't help.. after republishing the sink item it will work for a while..
days.. weeks and it's broken again.
maybe it has something to do with one of the outlook client builds.. cached
mode maybe?


"Joe Richards [MVP]" <humorexpress@hotmail.com> wrote
news:OPQsO5y0FHA.2428@tk2msftngp13.phx.gbl...
Have the sink output debugstrings to let you know where it is at at all
times, most likely the sink is hanging in a bad section of code.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Sorry wrote:
Hi,
Sometimes the async eventsink on a user calendar stops firing.
Deleting and recreating the eventsink item in the calendar fixes the
situation.
Windows Server 2003
Exchange server 2003 SP1
Outlook 2003 SP1
no eventlog errors.
Is this a known Exchange server bug?
Any way to troubleshoot this?
thanks,
John
Back to top
Sorry
Guest





Posted: Tue Oct 25, 2005 11:45 pm    Post subject: Re: Event sinks stop firing Reply with quote

Hi,
There is no code, only an event registration.
Yes only on some 2003 servers.
For the last week not incidents were reported so maybe Microsoft did a
silent repair already.


"Mailing Lists" <ml010241@berkea.com> wrote
news:1130253729.963183.103210@g44g2000cwa.googlegroups.com...
Quote:
We have seen similar behavior with an event sink running in a public
folder. Are you sure this only occurs on specific Exchange servers?
Are there any observable differences between the servers it works on
and those it doesn't? Could you you send me your code? I'd be
interested to see what else we have in commmon.

Sorry wrote:
Thanks for your suggestion Joe. However I don't think that's the case.
The sink simply passes the item url to a com+ dll to do it's thing.
As it is async there is nothing to keep it hanging... the sync is not
waiting for the process to finish.
the com+ component is multi-instance.. even if one instance would hang
(and
it that was not an observation), other instances are available to
process
the request.

I see this behavior on one out of maybe 10 to 15 exchange servers. reboot
won't help.. after republishing the sink item it will work for a while..
days.. weeks and it's broken again.
maybe it has something to do with one of the outlook client builds..
cached
mode maybe?


"Joe Richards [MVP]" <humorexpress@hotmail.com> wrote
news:OPQsO5y0FHA.2428@tk2msftngp13.phx.gbl...
Have the sink output debugstrings to let you know where it is at at all
times, most likely the sink is hanging in a bad section of code.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Sorry wrote:
Hi,
Sometimes the async eventsink on a user calendar stops firing.
Deleting and recreating the eventsink item in the calendar fixes the
situation.
Windows Server 2003
Exchange server 2003 SP1
Outlook 2003 SP1
no eventlog errors.
Is this a known Exchange server bug?
Any way to troubleshoot this?
thanks,
John
Back to top
Jason Johnston [MSFT]
Guest





Posted: Fri Oct 28, 2005 10:33 pm    Post subject: Re: Event sinks stop firing Reply with quote

I would take a look at the event registration item after it is "broken."
Have any values changed? I've seen this before, but it was due to another
process modifying the item and causing the contentclass to change...

"Sorry" <Sorry@microsoft.com> wrote in message
news:%23$EcHRZ2FHA.2472@TK2MSFTNGP12.phx.gbl...
Quote:
Hi,
There is no code, only an event registration.
Yes only on some 2003 servers.
For the last week not incidents were reported so maybe Microsoft did a
silent repair already.


"Mailing Lists" <ml010241@berkea.com> wrote
news:1130253729.963183.103210@g44g2000cwa.googlegroups.com...
We have seen similar behavior with an event sink running in a public
folder. Are you sure this only occurs on specific Exchange servers?
Are there any observable differences between the servers it works on
and those it doesn't? Could you you send me your code? I'd be
interested to see what else we have in commmon.

Sorry wrote:
Thanks for your suggestion Joe. However I don't think that's the case.
The sink simply passes the item url to a com+ dll to do it's thing.
As it is async there is nothing to keep it hanging... the sync is not
waiting for the process to finish.
the com+ component is multi-instance.. even if one instance would hang
(and
it that was not an observation), other instances are available to
process
the request.

I see this behavior on one out of maybe 10 to 15 exchange servers.
reboot
won't help.. after republishing the sink item it will work for a while..
days.. weeks and it's broken again.
maybe it has something to do with one of the outlook client builds..
cached
mode maybe?


"Joe Richards [MVP]" <humorexpress@hotmail.com> wrote
news:OPQsO5y0FHA.2428@tk2msftngp13.phx.gbl...
Have the sink output debugstrings to let you know where it is at at
all
times, most likely the sink is hanging in a bad section of code.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Sorry wrote:
Hi,
Sometimes the async eventsink on a user calendar stops firing.
Deleting and recreating the eventsink item in the calendar fixes the
situation.
Windows Server 2003
Exchange server 2003 SP1
Outlook 2003 SP1
no eventlog errors.
Is this a known Exchange server bug?
Any way to troubleshoot this?
thanks,
John


Back to top
 
Post new topic   Reply to topic    Exchange Server Forum Index -> Development All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




Windows Server Dedicated Servers
New Topics Powered by phpBB