Joel- Wednesday, June 11, 2003, 2:13:18 PM, you wrote:
JJ> My problem seems to be different. It appears to be some sort of JJ> deadlock situation (although I don't pretend to have any special JJ> knowledge of the architecture). The thing is, if I kill one, or JJ> sometimes two of the copies, the remaining ones will come back to life JJ> as if nothing had ever happened. JJ> Are many people out there using the networking features? I've been seeing this same problem on a client site lately. I've got exactly the same setup at home and it's been running completely stable for several years with two clients and one server. There are only a few differences between my site and my client's site: they're running Symantec antivirus and I'm running NOD32; they've got the win2k server sp3 patch on their server and I'm still at sp2; they've got a different backup system that runs in the background; I'm running a beta 1.63 copy and they're running TB 1.61. We've tried various things and have gotten it down to not hanging *as often* as it used to, but it still happens a few times a day. The symptoms are the same - 100% server CPU usage by TB; TB launch on workstations taking up to 10 minutes; killing the server process frees up the deadlock and everything's fine for a while. It sure sounds like some kind of a threading problem to me. Of course, every time I go into the office to work on it TB behaves itself, and I've never seen these symptoms here at home. Your workstations *do* have different NT logons to your server, no? The client is starting to look into places that host MS Exchange servers for you offsite. I'd hate to have them move off TB, but I need to stabilize their email system. I'll be curious to see what happens with your downgrade to 1.53... -Mark Wieder Using The Bat! v1.63 Beta/7 on Windows 2000 5.0 Build 2195 Service Pack 2 -- ________________________________________________________ http://www.silverstones.com/thebat/TBUDLInfo.html
