HI Bruce,

I'm running the client the same way on our Exchange 2003 servers too with no issues. The one thing to check is the configuration of the client and making sure that:

A) you have minimal logging set in your local BBWin.cfg file "<setting name="logreportfailure" value="false" />" otherwise agent will post to event log

B) I've included my config for the <msgs> section to show you how I mitigate the high level of reporting that can happen with Windows Event Viewer ESPECIALLY on an EXCHANGE SERVER:

<setting name="alwaysgreen" value="false" />

        <match logfile="System" type="error" delay="1h" alarmcolor="red" />

        <match logfile="Application" type="error" delay="1h" alarmcolor="red" />

        <match logfile="Application" eventid="9688" delay="1h" alarmcolor="red" />

        <ignore logfile="System" eventid="1111" />

        <ignore logfile="System" eventid="16" />

        <ignore logfile="System" eventid="10020" />

        <ignore logfile="System" eventid="5805" />

        <ignore logfile="System" eventid="5723" />

        <ignore logfile="System" eventid="12294" />

        <ignore logfile="Application" eventid="3008" />

        <ignore logfile="Application" eventid="1000" />

        <ignore logfile="Application" eventid="56" />

        <ignore logfile="Application" eventid="35" />

        <ignore logfile="Application" eventid="3015" />

Setting up to watch the event log in Windows can be tricky because Windows can generate ALLLLOT of messages for a very small issue that is not worth noting except during a monthly check. As you can see this gives me visibility into errors only, as I regularly check over my logs for oddities in warnings. And I want you to know that this list does change as I adjust the servers and the environment. Good luck, please contact me if you need additional help.

And sorry if I missed the question somehow.. :-)

Thank you,

Rafal Roginela

From: White, Bruce [mailto:bewhite at fellowes.com] Sent: Friday, March 21, 2008 12:26 PM To: 'Etienne Grignon'; hobbit at hswn.dk; BBWin mailing list Subject: [hobbit] RE: [bbwin-users] [hobbit] BBWIN Client running on Exchange server issues?

Thanks for the response.

We are running BBWIN 0.9 in local mode.

All columns produced by BBWIN turn purple, in time.

The last time BBWIN hung on our two servers 1 reported 340 out of 1400+ messages matched, the other report 748 out of 2589 matched.

I am the Unix guy in the shop. I brought hobbit on-board. The windows guys will not run BBWIN on these servers again until I can prove it is not causing all their problems (i.e.. 748 system level error messages).

  .......Bruce

From: bbwin-users-bounces at lists.sourceforge.net [mailto:bbwin-users-bounces at lists.sourceforge.net] On Behalf Of Etienne Grignon Sent: Friday, March 21, 2008 11:48 AM To: hobbit at hswn.dk; BBWin mailing list Subject: Re: [bbwin-users] [hobbit] BBWIN Client running on Exchange server issues?

Hello,

2008/3/18, Lárus Rafn Halldórsson <lalli at slepja.com>:

No need to reboot the machine... only kill the bbwin.exe in task manager and refresh services list. Then restart bbwin service.

I am having this trouble with an Exchange server and the source is that its logging very much in the system log and that seems to piss off the bbwin client. Same issue with BBWIN 0.9 and 0.10.. have not tried 0.11 yet. This happens 2-3 times a week.

Hope this helps,

Larus

BBWin should not have this behavior. I would need theses informations :

Are you running BBWin with central or local mode ? Do you have some columns which turn to purple color ? Could you check the msgs columns to see how many events are reported ? Could you try to run BBWin for a week without these agents : stats.dll, msgs.dll (and filesystem.dll if you are running the central mode) to see if the behavior is the same or not ?

Thank you in advance,

-- Etienne GRIGNON

Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.