- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Windows 2000 Server Event Log Warning ID 3588
ProLiant Servers (ML,DL,SL)
1753954
Members
7564
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2004 08:52 AM
тАО03-05-2004 08:52 AM
Windows 2000 Server Event Log Warning ID 3588
Twice this week we got a raft (about 100) of
these event log entries on a Proliant DL580 Server with an MSA1000 array controller. The
entire eventlog message string is as follows:
"Received write request at IRQL2 for \device\HarddiskVolume1". It says the Event ID is 3588 and the source is cxbf. There is no mention out on the network of cxbf or event id 3588. I can't tell you how many times we seem to get into trouble that no one in the world has ever seen before. I figured I'd ask here first and if there is no explaination, I'll call in a support request.
Thanks,
Dennis Herrick
ADE Corporation
dherrick@ade.com
these event log entries on a Proliant DL580 Server with an MSA1000 array controller. The
entire eventlog message string is as follows:
"Received write request at IRQL2 for \device\HarddiskVolume1". It says the Event ID is 3588 and the source is cxbf. There is no mention out on the network of cxbf or event id 3588. I can't tell you how many times we seem to get into trouble that no one in the world has ever seen before. I figured I'd ask here first and if there is no explaination, I'll call in a support request.
Thanks,
Dennis Herrick
ADE Corporation
dherrick@ade.com
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2004 10:26 PM
тАО03-05-2004 10:26 PM
Re: Windows 2000 Server Event Log Warning ID 3588
Hi Dennis,
Could it be a virus?
See the following on MyDoom-A...
http://lists.ibiblio.org/pipermail/freetds/2004q1/015390.html
Regards,
Brian
Could it be a virus?
See the following on MyDoom-A...
http://lists.ibiblio.org/pipermail/freetds/2004q1/015390.html
Regards,
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-06-2004 12:45 AM
тАО03-06-2004 12:45 AM
Re: Windows 2000 Server Event Log Warning ID 3588
Nice catch Brian. That looks exactly like it. McAfee has a nice server product now, ;ook into it
Hot Swap Hard Drives
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 06:08 AM
тАО03-08-2004 06:08 AM
Re: Windows 2000 Server Event Log Warning ID 3588
I did some more digging. I decided "source
cxbf" might refer to a driver. Sure enough there was a cxbf.sys in the system32 drivers directory. Ok now whose driver is it? I right clicked on the file entry and selected properties. Driver is from CommVault Galaxy backup software. It runs their "Image Option" feature. We are also
running Symantec V2i Protector for image backup of the system disk. I checked the times when the errors happen with the image backup schedule and they match. There must be a problem running disk image drivers from different companies at the same time.
I'll try CommVault and Symantec for suggestions. Thanks anyway for the quick replies. I'll also look into the cxbf.zip possibility too, you know how it goes, don't discount any solution too quickly.
Thanks again,
Dennis Herrick
dherrick@ade.com
cxbf" might refer to a driver. Sure enough there was a cxbf.sys in the system32 drivers directory. Ok now whose driver is it? I right clicked on the file entry and selected properties. Driver is from CommVault Galaxy backup software. It runs their "Image Option" feature. We are also
running Symantec V2i Protector for image backup of the system disk. I checked the times when the errors happen with the image backup schedule and they match. There must be a problem running disk image drivers from different companies at the same time.
I'll try CommVault and Symantec for suggestions. Thanks anyway for the quick replies. I'll also look into the cxbf.zip possibility too, you know how it goes, don't discount any solution too quickly.
Thanks again,
Dennis Herrick
dherrick@ade.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP