RE: Server freeze for 10'ish seconds : Event ID 7011



Hi,

Unfortunately we fixed the problem by reinstalling the server. We spoke to
an engineer at IBM who advised us that they normally recommed removing
anti-virus/backup software to see if that resolves it, he added that in 80%
of the time it doesn't and the only option is a reinstall. Sorry for the bad
news but that is what we ended up doing ourselves and touch wood haven't had
the problem since.

cheers

Richard

"Joshbish1979" wrote:

> Hello,
>
> I am also having a similar issue. It started happening on an existing
> Exchange 2003 server (running on Windows 2003 standard) about two months ago.
> The server has been up since last summer. The only thing I can think that I
> changed was a few days before the error started appearing in the event log
> was that I upgraded from 1gb of RAM to 2gb of RAM and made the adjustments
> necessary for Exchange to function properly with more than 1GB of RAM (/3GB
> switch in boot.ini). Any leads as to the cause would be greatly appreciated.
>
> Thanks,
>
> Joshua Bishop
>
> "msnews.microsoft.com" wrote:
>
> > When I access my W2K3 server, it stops responding for approximately 30 to 60
> > seconds while the hard disk light remains on. When I check the system event
> > logs, there is an entry with eventid 7011 from Service Control Manager that
> > corresponds with the server's non-response: Timeout (30000 milliseconds)
> > waiting for a transaction response from the NtFrs service.
> >
> > I've done a full HD check including a bad sector check, no problems found.
> > It's a new IBM x206 server one of about 10, this is the only one with the
> > problem. It's running a single 80Gb sata HD and is only about 2 months old.
> >
> > Seen someone else with the same error but no solution was offered, any
> > sugestions as to where to start looking ?
> >
> >
> >
.



Relevant Pages

  • RE: Server freeze for 10ish seconds : Event ID 7011
    ... The server has been up since last summer. ... changed was a few days before the error started appearing in the event log ... was that I upgraded from 1gb of RAM to 2gb of RAM and made the adjustments ...
    (microsoft.public.windows.server.general)
  • Re: Alocated Memory Error (SQLSERVR)
    ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: High memory usage (*HELP*)
    ... you can use Computer Management MMC to view the server logs. ... a server with 4 GB RAM, I doubt you need the second page file on D. So ... The virtual memory on D: drive is set to: 1550/3075 ... throttled ISA and Monitoring. ...
    (microsoft.public.windows.server.sbs)
  • Re: High memory usage (*HELP*)
    ... I rebooted the server, I should have just restarted the service for report ... a server with 4 GB RAM, I doubt you need the second page file on D. ... The virtual memory on D: drive is set to: 1550/3075 ...
    (microsoft.public.windows.server.sbs)
  • Re: Alocated Memory Error (SQLSERVR)
    ... FWIW I am not using sbs 2003 premium, ... non ever going about 200mb of memory usage. ... on what you should throttle the RAM to. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)

Quantcast