Two months. That's right, two $*#!!*$ months. Still getting a BSOD on my Trend 8.0 server without generating any .dmp files. I've spent probably 25 hours or so with Trend and MS tech support. Webex sessions, specialists, conference calls, tin foil hats, barking at the moon. Updated BIOS, Perc, Nic, video, RAID drivers. UN-installed the Trend client from the server. Only Trend Service running is the Master Service. Nothing else on the server except a print queue that myself and one other person uses on a fairly limited basis. Any thoughts or suggestions appreciated. In the interim, I'm going to go stick a pencil in my eye. Thanks for letting me rant. Steve
-------------- Forwarded Message: -------------- From: "Terry Dickson" <[EMAIL PROTECTED]> To: "NT System Admin Issues" <[email protected]> Subject: RE: Trend 8.0 server hang Date: Thu, 10 Apr 2008 14:24:03 +0000 Good question, but also how do you have Windows Updates set, do you have automatic updates turned on? -----Original Message----- From: Miller Bonnie L. [mailto:[EMAIL PROTECTED] Sent: Thursday, April 10, 2008 9:00 AM To: NT System Admin Issues Subject: RE: Trend 8.0 server hang Steve-when you say patched, do you mean the OSC server has been patched with Trend's patch 2 or 3 (3 just came out yesterday), or are you talking about Windows patches? There are some serious problems prior to patch1. If it is all patched up from Trend, make sure you have automatically restart unchecked (control panel, system, advanced, startup and recovery settings). That way if it is BSOD'ing, you can see the screen in the morning. One other thing I've seen with Trend (both 7.x and 8.x) is kernel memory issues (again, mostly prior to the latest patches, but I haven't tried patch3 yet). During the time your server is "hung", can you RDP to the console session? If it kicks you back to the server name screen, or gives you a strange error about session 0, I'd put money on a kernel memory issue. We've found we pretty much can't use the /3GB switch in the boot.ini when we see this happening, but it also can take some registry tuning. Another way to troubleshoot on this is to try and RDP-if it fails, connect remotely with computer management to the server. Stop the Officescan realtime scanner service, and RDP will generally start working. Still takes a reboot to clear the problem, but that would also indicate the kernel mem issue. If you leave the system long enough, it will eventually BSOD. -Bonnie From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, April 10, 2008 6:46 AM To: NT System Admin Issues Subject: Trend 8.0 server hang Fresh install of Office Scan 8.0 patched on a fresh W2K3 standard server SP1. Serve reboots or hangs usually around 1-3 AM intermittantly. No memory dumps, no event log info other than the reboot was unexpected. This morning, server appeared to be up and running but could not get any programs or desktop icons to respond. Hard reboot was needed. Event viewer states unexpected reboot at 1:03 AM but server appeared to be up and running. Any one else encountered anything like this? I will call Trend (again) but my phone system coughed up a large hair ball overnight so I thought I'd throw this out to the list. Thanks. Steve ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
