Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Development / March 2005

Tip: Looking for answers? Try searching our database.

EventSink did't unload

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Andree Zaja - 22 Mar 2005 10:40 GMT
Hi,

I wrote an Exchange EventSink in VC++ and installed it on my system.
The sink implements the OnSyncSave() method and also an own dummy method
Test().
I told the component manager to unload the DLL after one minute of
inactivity. If I call the method Test(), I can see that the DLL is loaded
into memory and after one minute it is unloaded. If one event fired
OnSyncSave() I can see that the DLL is loaded an if I only read the
affected record it is also unloaded after one minute, but my EventSink
also needs information about the parent folder of the item that fires the
event. So I create a connection and a record to read the folder attributes.
After that the DLL did not unload after one minute. Why?

I do a Close() on the created record and connection object.

More confusing is the fact that if I call Test() after that, the DLL
unloads again after one minute.

What's wrong?
Andrew
tester - 25 Mar 2005 21:35 GMT
Desperate User Andree Zaja said:
> Hi,
>
> I wrote an Exchange EventSink in VC++ and installed it on my system.
So You have got a new car;)

> The sink implements the OnSyncSave() method and also an own dummy method
> Test().
Oh, it has automatic drive transmission so it can be driven by You;) (You have
got a real luck;) )

> ... but my EventSink
> also needs information about the parent folder of the item that fires the
> event. So I create a connection and a record to read the folder attributes.
> After that the DLL did not unload after one minute. Why?
1.Becouse You haven't heard about inline debugging (using fprintf and so on...)?
2.Becouse You haven't heard about catching exceptions from interfaces anywhere?

> I do a Close() on the created record and connection object.
>
[quoted text clipped - 3 lines]
> What's wrong?
> Andrew
1.The serious problem has probably materna.de by employing not properly prepared
"programmer" for self-solving simple task. ( maybe outsourcing???;) )
2.Maybe sending the offer to "IT-Service-Management" team solve someone's
finanacial problems...?;)

Conclusion: Try to self-debug the way of thinking about solving problems.

Regards,
Tester.
Andree Zaja - 29 Mar 2005 16:47 GMT
>  > ... but my EventSink
>  > also needs information about the parent folder of the item that fires the
>  > event. So I create a connection and a record to read the folder attributes.
>  > After that the DLL did not unload after one minute. Why?
> 1.Becouse You haven't heard about inline debugging (using fprintf and so on...)?
> 2.Becouse You haven't heard about catching exceptions from interfaces anywhere?

There occures no exception. I know it, because I catch all kinds and use
inline debugging (fprintf and so on...).

>  > I do a Close() on the created record and connection object.
>  >
[quoted text clipped - 13 lines]
> Regards,
> Tester.

Typical useless information.
Looking for a job?
Sorry, I don't have one for guys who don't have the courage to sign
their postings with their name.
tester - 30 Mar 2005 00:04 GMT
User Andree Zaja said:

>>Conclusion: Try to self-debug the way of thinking about solving
>>problems.

 >
> Typical useless information.
The best answer for the useless information You have provided which "describes
Your problem" - in Your opinion. You **request** help from the worldwide for
**free** not providing any useful information to interest anyone.
Your request is something like: "My car is out of order. How to fix it?. I have
a couple of tools in the **black box** in the garage, HELP!!!"

1. Can't You confirm that you return from EventSink procedure and You are not in
endless loop ? (becouse of re-firing event in Your EventSink Procedure code??? -
do a simple counter to confirm if You can't do in other way)
2. Can't You confirm that you destroy all objects after their job to release the
App from memo ?
3. Can't You just snap-in Your "super-classified-code" instead of writing any
baby-tales about unloadable events?
You have the bug for sure or You can't check the code You've written...

The best help You can get is from Yourself , becouse only You know what You've
written in Your code.

Bye.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.