Event ID 34 – the driver disabled the write cache

15 pts.
Windows 2000 Server
I have a Windows 2000 Server, SP4, which is hosting a CISCO ACS Wireless Authentication application, ver 3.0. We have had 2 crashes of the ACS in the past week, where users can't authenticate to the network via wireless (Active Directory integrated). A reboot restores access.The above error has been evident in the event log, but I can't find anything about it in searching Microsoft's Knowledge base. I know the system needs a memory upgrade, as monitoring software points this out. Does anyone know what this error means, and what wil fix it?

Answer Wiki

Thanks. We'll let you know when a new response is added.

follow this link : http://www.microsoft.com/technet/support/ee/result.aspx?EvtSrc=disk&EvtID=34&ProdName=Windows+Operating+System&LCID=1033&ProdVer=5.0

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Kinsden
    I do not think the crashing of the application has to do anything with this event. If your 2000 server is a DC, then its a normal behaviour for the OS to log these events. The reason is Windows disables the write cache on the hard disk to prevent data corruption (not to forget, the AD database). More info at: http://support.microsoft.com/default.aspx?scid=kb;en-us;233541
    0 pointsBadges:
  • JamesTPHP
    I agree that this error would most likely not be the cause of your crashes. Some things I would check first are: Event logs filling up memory or disk space. This has caused our ACS to crash several times. Low memory. If you get lots of hits on the server and memory is low, it can certainly lead to a crash. Also, is the ACS service still running when you crash, or does the entire OS crash? Here is a link from Cisco that notes potential, although less likely issues. http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/csnt30/rnacs302.pdf This link show how to setup debugging on the server. This may help identify your problem, unless logs filling up is the problem, then you may see the problem drastically increase once you turn on more logging. I would recommend doing this only when you can schedule a down time or when a potential crash will have the least impact As always, please have a current backup of your system and a plan to restore the system in the event testing causes more problems than it fixes. http://www.cisco.com/warp/public/480/9.pdf Hope some of this may help. If you don?t have a current Cisco CCO account you may have to contact Cisco or your local rep for these documents.
    0 pointsBadges:
  • Barbazg
    for clarificatrion, the W2K server never realy crashed, but the ACS server access from clients stopped. Adding additiona memory didn't solve the issue. It turns out that the culprit was the built in database backup tool in the ACS set program. If thresholds are set properly for automated backups, the system will shut down access from the clients. Having removed the backup schedule as it was, the system has remained stable. thanks for the info on the logs. the above serve is also a domain controller, which explains the logging.
    15 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: