Re: Server semi-shutdown

From: Andrew H (ajhpms_at_hotmail.com)
Date: 10/03/04 

Date: Sun, 3 Oct 2004 14:47:48 +0200

Hi Dave

In my case, ino_flpy.sys is the same version, but ino_fltr.sys is
5.0.6100.135. I couldn't get this info from the tray icon (it just shows
program & signature versions, not driver versions), but from properties on
the files themselves. I'll try locate the .136 version you have - could you
perhaps post a link to it?

The problem did re-occur this weekend - sometime between Friday 4pm (when I
left) and Sunday 2pm (when I checked in on the system). That does
correspond with approximately 6 days uptime. I tried clicking the shortcut
to shut down the eTrust engine I had created on the desktop, but had no
response and had to hit the big red button again. Perhaps if I'd been more
patient something might have happened.

Once again, backups to USB disk on Friday morning went fine, so for right
now I'll take that out of the equation.

Regards

Andrew

"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:%23VTJnI9pEHA.800@TK2MSFTNGP14.phx.gbl...
> There's something strange in the downloads pages at CA. I'm going in to
> the 7.1 updates and finding a driver update dated 9/9/04 that indicates
> it's for 7.x, which led me to believe it was the 7.0 and 7.1 driver. When
> I go into the 7.0 updates, it shows the date of 7/15 but it appears to be
> the same drivers.
>
> In any case, the driver versions that fixed my SBS are 5.0.6100.136
> (Ino_fltr.sys) and 5.0.6100.106 (Ino_flpy.sys). You can see what version
> you're on by r-clicking the AV tray icon and clicking Version. If you're
> not on the current ones, I'd update.
>
> I've been troubleshooting this since April, including months with CA and a
> couple of weeks with PSS. Interestingly, CA is so sure this driver is the
> fix to my problem they apparently closed the ticket without ever checking
> back with me. IMO this is a glaring example of poor support, especially
> now that I see a driver that fixed it was released in July. I don't
> believe there are any differences between 7.0 and 7.1 other than reports
> and UI changes, so they could have released that driver for 7.1 when they
> released it for 7.0 - it's the same file anyway. They say I'm the only
> one who had the problem, yet they were so sure it was the driver they
> assumed that fixed it, without even bothering to check.
>
>
> "Andrew H" <ajhpms@hotmail.com> wrote in message
> news:O86Jew6pEHA.592@TK2MSFTNGP11.phx.gbl...
>> Hi Dave
>>
>> The latest driver I can see at CA is dated 7/15/04. Is this the one?
>>
>> Regards
>>
>> Andrew
>>
>> "Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in
>> message news:e8gdipWpEHA.1576@TK2MSFTNGP12.phx.gbl...
>>> Andrew - FYI, I installed the new eTrust driver released by CA around
>>> 9/12. I'm currently 3 days past the longest I've gone without the server
>>> becoming unresponsive, so I'm getting close to calling that the
>>> solution. CA can point to a fix in that driver that they credit with
>>> solving this problem. They say an issue with a particular control caused
>>> medium-severity performance issues for some of their customers, and
>>> they're thinking that I had an extreme case of what they had seen more
>>> moderately elsewhere.
>>>
>>> So if your problem is eTrust rather than USB, the driver update is
>>> probably your answer.
>>>
>>> HTH,
>>> Dave
>>>
>>>
>>> "Andrew H" <ajhpms@hotmail.com> wrote in message
>>> news:OyTkASvnEHA.2576@TK2MSFTNGP10.phx.gbl...
>>>> I've been experiencing a problem with an SBS2003 server the last
>>>> several weeks, apparently during the weekend. Each Monday the server
>>>> is non-responsive - the mouse moves, but nothing will open and there is
>>>> no response to Ctrl-Alt-Del. The task bar is shown in outline, with
>>>> the buttons inaccessable - Explorer is frozen.
>>>>
>>>> However, I am able to login at a workstation, use files on the server,
>>>> connect to the Internet using the server's ISA, and use the Event
>>>> Viewer to look at the server's event logs. Remote desktop access to
>>>> the server freezes and Companyweb won't open, but Outlook opens and
>>>> connects to the server.
>>>>
>>>> On the server, I eventually have no choice but to hard reset on Monday
>>>> morning. Once the server restarts, everything is back to normal. I
>>>> can't see anything in the event logs that explains the problem, except
>>>> for the fact that the server believes it was shut down the previous
>>>> Friday, not on the Monday it was actually shut down. There is nothing
>>>> in any of the event logs between the "Friday" shutdown and the restart
>>>> on Monday.
>>>>
>>>> I also had the experience of working late one Friday evening, keeping
>>>> an eye on the workstation's clock to get an idea of time. After what
>>>> seemed a few hours activity, according to the workstation and the
>>>> server it was approximately 10pm - but the sun was rising outside, and
>>>> the real time was somewhere around 6am. I had inadvertently worked
>>>> through the night because I relied on the server clock. My guess is
>>>> that the clock gradually slowed down during the evening to the point it
>>>> hardly moved, and somehow this must be another aspect of the server
>>>> semi-shutdown.
>>>>
>>>> The only thing I can think of that has changed in the last few weeks
>>>> relating to the weekend is that the backup wizard has been scheduled to
>>>> do a backup to a new external USB 2.0 Iomega HDD at 4am on Friday
>>>> mornings. This backup completes, according to the logs, and I've done
>>>> manual full system backups without any issues.
>>>>
>>>> Server and workstations are fully patched (HFNetChk Pro) and have been
>>>> scanned using latest Antivirus signatures.
>>>>
>>>> I know time flows differently for Microsoft systems than in the real
>>>> world, but this is ridiculous.
>>>>
>>>> Any suggestions as to next step, please?
>>>>
>>>
>>>
>>
>>
>
>

Loading