BBWIN Client running on Exchange server issues?
list Bruce White
Anyone had problems running the BBWIN client on Windows running MS exchange? We have it installed and running on two different MS exchange servers (both running MS Exchange 2003, one on Win2K, the other Win2003) and for some reason the client hangs. If you try to stop the service, it stays in a "stopping" state and the only way to get it restarted is to cycle the machine. We are running BBWIN 0.9, but my windows guys are afraid to go to 0.11. Has anyone experienced this before? Will upgrading to 0.11 solve the issue? Thanks, Bruce 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.
list David Gilmore
Bruce, I have had v0.8-v0.10 running on my Exchange box for a while. It was first running v.8 and v.9 on a W2k3 box with E2k3 and never experienced a client issue. I currently have v.10 running on a W2k3 x64 and E2k7 box. Have plans to move to v.11 but have not gotten to it. I would also suggest that you look for a copy of kill.exe from the old NT Resource Kit. It will save you a lot of reboots when services hang. Did you check the BBWIN logs? David
▸
From: White, Bruce [mailto:user-58f975e8bf9d@xymon.invalid]
Sent: Monday, March 17, 2008 6:56 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWIN Client running on Exchange server issues?
Anyone had problems running the BBWIN client on Windows running MS exchange? We have it installed and running on two different MS exchange servers (both running MS Exchange 2003, one on Win2K, the other Win2003) and for some reason the client hangs. If you try to stop the service, it stays in a "stopping" state and the only way to get it restarted is to cycle the machine. We are running BBWIN 0.9, but my windows guys are afraid to go to 0.11. Has anyone experienced this before? Will upgrading to 0.11 solve the issue?
Thanks,
Bruce
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.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
list Josh Luthman
I am being serious when I ask this.. Isn't that a normal Windows thing?
▸
On 3/17/08, White, Bruce <user-58f975e8bf9d@xymon.invalid> wrote:Anyone had problems running the BBWIN client on Windows running MS exchange? We have it installed and running on two different MS exchange servers (both running MS Exchange 2003, one on Win2K, the other Win2003) and for some reason the client hangs. If you try to stop the service, it stays in a "stopping" state and the only way to get it restarted is to cycle the machine. We are running BBWIN 0.9, but my windows guys are afraid to go
to 0.11. Has anyone experienced this before? Will upgrading to 0.11solve the issue?
▸
Thanks,
Bruce
*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.
--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer
list Josh Luthman
On that note I suggest pskill by Sysinternals: http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx
▸
On 3/17/08, David Gilmore <user-70507ff7198d@xymon.invalid> wrote:Bruce, I have had v0.8-v0.10 running on my Exchange box for a while. It was first running v.8 and v.9 on a W2k3 box with E2k3 and never experienced a client issue. I currently have v.10 running on a W2k3 x64 and E2k7 box. Have plans to move to v.11 but have not gotten to it. I would also suggest that you look for a copy of kill.exe from the old NT Resource Kit. It will save you a lot of reboots when services hang. Did you check the BBWIN logs? David *From:* White, Bruce [mailto:user-58f975e8bf9d@xymon.invalid] *Sent:* Monday, March 17, 2008 6:56 PM *To:* user-ae9b8668bcde@xymon.invalid *Subject:* [hobbit] BBWIN Client running on Exchange server issues? Anyone had problems running the BBWIN client on Windows running MS exchange? We have it installed and running on two different MS exchange servers (both running MS Exchange 2003, one on Win2K, the other Win2003) and for some reason the client hangs. If you try to stop the service, it stays in a "stopping" state and the only way to get it restarted is to cycle the machine. We are running BBWIN 0.9, but my windows guys are afraid to go to 0.11. Has anyone experienced this before? Will upgrading to 0.11solve the issue? Thanks, Bruce *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. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
-- Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer
list Lárus Rafn Halldórsson
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
▸
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid] Sent: 17. mars 2008 23:21 To: user-ae9b8668bcde@xymon.invalid Subject: Re: [hobbit] BBWIN Client running on Exchange server issues? On that note I suggest pskill by Sysinternals: http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx On 3/17/08, David Gilmore <user-70507ff7198d@xymon.invalid> wrote: Bruce, I have had v0.8-v0.10 running on my Exchange box for a while. It was first running v.8 and v.9 on a W2k3 box with E2k3 and never experienced a client issue. I currently have v.10 running on a W2k3 x64 and E2k7 box. Have plans to move to v.11 but have not gotten to it. I would also suggest that you look for a copy of kill.exe from the old NT Resource Kit. It will save you a lot of reboots when services hang. Did you check the BBWIN logs? David From: White, Bruce [mailto:user-58f975e8bf9d@xymon.invalid] Sent: Monday, March 17, 2008 6:56 PM To: user-ae9b8668bcde@xymon.invalid Subject: [hobbit] BBWIN Client running on Exchange server issues? Anyone had problems running the BBWIN client on Windows running MS exchange? We have it installed and running on two different MS exchange servers (both running MS Exchange 2003, one on Win2K, the other Win2003) and for some reason the client hangs. If you try to stop the service, it stays in a "stopping" state and the only way to get it restarted is to cycle the machine. We are running BBWIN 0.9, but my windows guys are afraid to go to 0.11. Has anyone experienced this before? Will upgrading to 0.11 solve the issue? Thanks, Bruce 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. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. -- Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer --
ESVA scan result: Clean
list Vernon Everett
Hi
Is anybody monitoring any Windoze applications with BBWIN and Hobbit?
Exchange, Sharepoint, SQL-Server, etc.
What level of success have you experienced?
What scripts and/or applications are you using to do it?
Regards
Vernon
NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.
list Graeme A Shea
I monitor more windows services using BBWin or the bb BTF client, specifically I do: Distributed File System access and replication NT Backup file sizes and dates as well as checking the backup log and event log for backup errors. I run dcdiags and netdiags every night and check for errors I defrag every night and check for errors (Defrag is a good forwarner of problems rather than there be any need to defrag every night). DHCP is responding and still has free addresses to lease (DNS is done by netdiags above). Symantec AV and interface errors on switches and ping times to them and anything else you want to ping (like a printer on the far end of your LAN). These are all done by VB scripts and the external facility of BB BTF or BBWin. There is a difference between how BBWin 0.9 and BB BTF client handle the external files created by the scripts and not all these scripts have been updated to work on BBWin. See http://sourceforge.net/forum/forum.php?thread_id=1875682&forum_id=460874 for more info. I don't know if this has been fixed, I haven't found mention in the release notes. If you promise not to laugh at the coding you can download the scripts for a short while from www.shea.com.au/downloads/BBScripts.zip. feel free to post them on the shire. As for the original examples you gave I monitor the Exchange, SQL and Sharepoint services as well as their web site response. I haven't expanded on these because as counter intuitive as it seems my Exchange and SQL are non critical services and the chance of me not catching the errors with such simple monitoring is fairly slim. Your Windows admins should be able to script something they will be happy with if you give them the above scripts as examples. Hope these help Regards Graeme
▸
From: Everett, Vernon [mailto:user-9da1a1882f49@xymon.invalid]
Sent: Tuesday, 18 March 2008 3:25 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWIN - beyond the basics
Hi
Is anybody monitoring any Windoze applications with BBWIN and Hobbit?
Exchange, Sharepoint, SQL-Server, etc.
What level of success have you experienced?
What scripts and/or applications are you using to do it?
Regards
Vernon
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
list Etienne Grignon
Hello, 2008/3/18, Lárus Rafn Halldórsson <user-415184c713bc@xymon.invalid>:
▸
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
list Bruce White
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: user-a031f2e39640@xymon.invalid
[mailto:user-a031f2e39640@xymon.invalid] On Behalf Of Etienne
Grignon
Sent: Friday, March 21, 2008 11:48 AM
To: user-ae9b8668bcde@xymon.invalid; BBWin mailing list
Subject: Re: [bbwin-users] [hobbit] BBWIN Client running on Exchange server
issues?
Hello,
2008/3/18, Lárus Rafn Halldórsson <user-415184c713bc@xymon.invalid
<mailto:user-415184c713bc@xymon.invalid> >:
▸
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.
list Rafal Roginela
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:user-58f975e8bf9d@xymon.invalid]
Sent: Friday, March 21, 2008 12:26 PM
To: 'Etienne Grignon'; user-ae9b8668bcde@xymon.invalid; 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: user-a031f2e39640@xymon.invalid [mailto:user-a031f2e39640@xymon.invalid] On Behalf Of Etienne Grignon
Sent: Friday, March 21, 2008 11:48 AM
To: user-ae9b8668bcde@xymon.invalid; BBWin mailing list
Subject: Re: [bbwin-users] [hobbit] BBWIN Client running on Exchange server issues?
Hello,
2008/3/18, Lárus Rafn Halldórsson <user-415184c713bc@xymon.invalid>:
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.
list Etienne Grignon
Hi Bruce, 2008/3/21, White, Bruce <user-58f975e8bf9d@xymon.invalid>:
▸
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).
I may know where the problem could come from. For people who has the problem, I would like them to enable the option in bbwin.cfg file : <setting name="logreportfailure" value="true" /> Then, you should check when it comes purple if you get events like this : "BBWin failed to send the client data successfuly to the hobbit server. The error was : can't connect to host : Only one usage of each socket address (protocol/network address/port) is normally permitted.." This error happen when we reach the maximum number of sockets available on the box. This link documents differents ways to handle this type of error : http://blogs.msdn.com/dgorti/archive/2005/09/18/470766.aspx Let me know if it is your case. Thank you in advance, -- Etienne GRIGNON
list Bruce White
Etienne,
Thanks! As I said, I'm the Unix guys and the chef proponent of hobbit. I
will see if I can get the windows guys to restart the BBWIN Client, but it
may not happen.
......Bruce
-----Original Message-----
From: Etienne Grignon [mailto:user-87c74c1037a4@xymon.invalid]
Sent: Thursday, April 03, 2008 10:28 AM
To: White, Bruce
Cc: user-ae9b8668bcde@xymon.invalid; BBWin mailing list
Subject: Re: [bbwin-users] [hobbit] BBWIN Client running on Exchange serve r
issues?
▸
Hi Bruce,
2008/3/21, White, Bruce <user-58f975e8bf9d@xymon.invalid>: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).
I may know where the problem could come from. For people who has the problem, I would like them to enable the option in bbwin.cfg file : <setting name="logreportfailure" value="true" /> Then, you should check when it comes purple if you get events like this : "BBWin failed to send the client data successfuly to the hobbit server. The error was : can't connect to host : Only one usage of each socket address (protocol/network address/port) is normally permitted.." This error happen when we reach the maximum number of sockets available on the box. This link documents differents ways to handle this type of error : http://blogs.msdn.com/dgorti/archive/2005/09/18/470766.aspx Let me know if it is your case. 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.