Probs with BBWin 0.7 🔗 link

On Mon, Jun 05, 2006 at 11:13:45PM +0200, Roger WJ Alterskjær wrote:

I've sent an email to the BBWin list but am wondering if troubleshooting
this client is done on this list instead. (I've read Jason Chambers
quick plea for help from a few hours ago.)

P.S. Hobbit ROCKS! This weekend I did an install of the latest BB, was
about to install BBGen then discover the Hobbit project. An immediate
switchover to Hobbit later and I'm a happy camper!

 Hi!
I've sent an email to the BBWin list but am wondering if troubleshooting
this client is done on this list instead. (I've read Jason Chambers quick
plea for help from a few hours ago.)

P.S. Hobbit ROCKS! This weekend I did an install of the latest BB, was
about to install BBGen then discover the Hobbit project. An immediate
switchover to Hobbit later and I'm a happy camper!

-Roger Alterskjær

-- 

On Mon, 2006-06-05 at 23:59 +0200, Etienne Grignon wrote:

Well, I didn't receive any message from the BBWin mailinglist. You may
explain your problem here  (I have Henrik agreement :) ) for the
moment so I can help you faster.

 On Mon, 2006-06-05 at 23:59 +0200, Etienne Grignon wrote:

Well, I didn't receive any message from the BBWin mailinglist. You may
explain your problem here  (I have Henrik agreement :) ) for the moment so I
can help you faster.

Hi!
I'm new to the list and BB/Hobbit. Just did a fresh (and successful)
install of BB server and clients (linux and windows servers) when I
discovered Hobbit. Installed Hobbit only to find out that the lates BB
client couldn't talk to Hobbit.

After that I found out about this project and the the cool BBWin version
0.7. The transition from BB client to BBWin went smoothly on Windows 2003
Server. The VBS-script for generating BBWin.cfg is brilliant. However, the
script didn't like running on a 64-bit Windows 2003 Server. FYI, I had to
tweak the HKLM-registery line to read something like this:
...\Software\Wow6432Node\BBWin\...
Problem solved!

 Got a problem, though: My one and only Windows 2000 Server seems to not

like the service. Trying to restart the service couldn't stop it; had to
resort to 'pskill'. Still, it's not reporting to my Hobbit server and I've
gone over it from the registery settings to my bb-hosts file. Everything
says it 'should' be working. But I'm a bit suspicious since the service is
so difficult to do a restart. (The old BB client to BB server did work
perfectly...)

 Other than that, I have to say this is a fantastic utility!! Thank you!!!

-Roger Alterskjær

On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:

Some users still report me that sometimes, they can't stop the
service. In reality, it seems that one agent never starts successfuly,
which mean that one of the agent is breaking the all threads at
startup and that's why you can't stop it after and why it never
reports. 
For this bug, I'm still figure out what's happen in this case because
for the moment, I never succeed to reproduce this behavior in Visual C
++ debugger on my Windows XP station.
However, the agent cpu is for the moment the suspicious agent which
may cause this strange crash. You may try starting BBWin on your
Win2000 without the cpu loading directive. 

On Tue, 2006-06-06 at 16:28 +0200, Roger WJ Alterskjær wrote:

On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:

Some users still report me that sometimes, they can't stop the
service. In reality, it seems that one agent never starts
successfuly, which mean that one of the agent is breaking the all
threads at startup and that's why you can't stop it after and why it
never reports. 
For this bug, I'm still figure out what's happen in this case
because for the moment, I never succeed to reproduce this behavior
in Visual C++ debugger on my Windows XP station.
However, the agent cpu is for the moment the suspicious agent which
may cause this strange crash. You may try starting BBWin on your
Win2000 without the cpu loading directive. 

On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:

Some users still report me that sometimes, they can't stop the
service. In reality, it seems that one agent never starts successfuly,
which mean that one of the agent is breaking the all threads at
startup and that's why you can't stop it after and why it never
reports. 
For this bug, I'm still figure out what's happen in this case because
for the moment, I never succeed to reproduce this behavior in Visual C
++ debugger on my Windows XP station.
However, the agent cpu is for the moment the suspicious agent which
may cause this strange crash. You may try starting BBWin on your
Win2000 without the cpu loading directive. 

 On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:

Some users still report me that sometimes, they can't stop the service. In
reality, it seems that one agent never starts successfuly, which mean that
one of the agent is breaking the all threads at startup and that's why you
can't stop it after and why it never reports.
For this bug, I'm still figure out what's happen in this case because for
the moment, I never succeed to reproduce this behavior in Visual C++
debugger on my Windows XP station.
However, the agent cpu is for the moment the suspicious agent which may
cause this strange crash. You may try starting BBWin on your Win2000 without
the cpu loading directive.


Okay, it looks like you were right about the cpu agent. I disabled it
yesterday and it BBWin looks pretty stable. Even restarted the entire server
early this morning without any incident: BBWin shutdown and restarted
nicely.

Don't know how much time and effort should be put into the Win 2k problem.
For me, this is our last W2K server and it will be retired within a years