Home > Event Id > Event Id 129 Hpcisss2

Event Id 129 Hpcisss2


You can try this tool http://www8.hp.com/us/en/products/server-software/product-detail.html?oid=489496(HP Websim) and look at the stats for each hard disk. 0 Message Author Comment by:cisgoro76 ID: 409516042015-08-28 hello, i have not used tgis tool I received the spare drive a couple of hours later and after installing the drive it rebuilt itself overnight. x 76 Anonymous I got this error in my event viewer every 30 seconds. I have seen software be the issue more often than not. 9 times out of 10 the event 129 error can be resolved with updated network drivers and/or disk timeout values. Source

I checked around the net, there was not much resolution. This did not resolve the issue. Same thing on our server, we had 9000+Hard read errors on a 500GB Disk. The disk timeout value is a tunable parameter in the registry at: HKLM\System\CurrentControlSet\Services\Disk\TimeOutValue. https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/Event-ID-129-source-HpCISSs2/td-p/4588518

Event Id 129 Reset To Device Device Raidport0 Was Issued

Can this number be written in (3^x) - 1 format? The port driver does most of the request processing. After replacing the drive, the warnings disappeared. This is something Windows 7 users have struggled with.

This is not a problem that we are familiar with. For example, ATAPORT.SYS is the port driver for ATA devices, and STORPORT.SYS is the port driver for SCSI devices. When I don't have users logged into the server like now at 2:44am I do not see the event being posted on event viewer. Hpcisss3 Event 129 That is when the STORPORT driver logs the Event ID 129 error.

They have the diagnostics utilites to test the hardware.If HP feels that issue is related to microsoft , we will troubleshoot further.some referenceshttp://www.eventid.net/display.asp?eventid=129&eventno=9180&source=HpCISSs2&phase=1http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1260796982765+28353475&threadId=1298378 Marked as answer by Bruce-Liu Friday, December 18, The following information is part of the event: \Device\RaidPort0. No issues found. SCOPE Any HP ProLiant Gen8-series servers or any HP ProLiant server running Windows Server 2008 R2 with the Service Pack for ProLiant (SPP) Version 2014.09.0 (including HP Insight Management WBEM Providers

When the request is completed, it is removed from this queue. Reset To Device Device Raidport0 Was Issued Server 2008 The problem has been with every OS update, -> Win7, Win8.x, Win10, I get hard disk freezes after the OS "upgrade." In Win7 and Win8.x, the MCP79 chipset was listed as Did HP really say there was nothing wrong with the array? This SRB is sent to the port driver as part of the I/O request packet (IRP).

Hpcisss2 Error Event Id 129

So, it confims that this is due to hardware error on the Cache board and HP is going to replace it for me. http://www.eventid.net/display-eventid-129-source-HpCISSs2-eventno-9180-phase-1.htm To search for additional advisories related to Windows Server 2008 R2, use the following search string: +Advisory +ProLiant -"Software and Drivers" +Windows Server 2008 R2 Hardware Platforms Affected: HP ProLiant BL2x220c Event Id 129 Reset To Device Device Raidport0 Was Issued I get this all the time when I forget to disable the Backup Integration Service for my FreeBSD VMs. Event Id 5008 Hpcisss3 After we upgraded our ProLiant Servers to the latest HP Service Pack for ProLiant Servers, (dated April 2015), we started gettingthese warning messages in the system log.

The port driver calls the HwStorStartIo() function to send requests to the miniport, and the miniport will send the requests to the HBA so they can be sent over the physical this contact form x 63 Private comment: Subscribers only. Kelvin Wong Search Search Tagsactive directory adodb adsi citrix cmd datastore dcom dfs dfsr diskpart dns esxi esxtop explorer gerald weinberg gmail hardware heartbleed hotfix HPBlade hp proliant hpsim hta iis I really feel like calling them back and tell them what the issue really was. 0 LVL 7 Overall: Level 7 Server Hardware 1 MS Server OS 1 Windows Server Kb932755

TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. I had the same problem on my server like yours. As requests are completed the queue timer is refreshed with the timeout value of the SRB at the head of the list. http://smartnewsolutions.com/event-id/event-id-1309-source-asp-net-2-0-event-code-3005.html Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form NAVIGATION TIP : For hints on navigating HP.com to locate the latest drivers, patches, and other support software

Event ID: 129 Source: HpCISSs2 Source: HpCISSs2 Type: Warning Description:Reset to device, \Device\RaidPort0, was issued. Reset To Device Device Raidport0 Was Issued. Hp Server When you update with HPSUM (from 2014.09) HPSUM looks whether you are using (=active) CISSS2 or CISSS3 (ControlPanel/Syste/DeviceManager/SCSIController/Driver/Details) and upgrades ONLY that driver !!Here at my plant after upgrading to the Anything else I may look into to find why 2 servers no errors and 3 with? 0 Kudos Reply Suzanne Harris Occasional Visitor Options Mark as New Bookmark Subscribe Subscribe to

If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate?

Next I fired up HP Websim to check on the hardware status and looks green. Other product and company names mentioned herein may be trademarks of their respective owners. This is the second time that disk has failed, first time hard fail, with a light, and this time not easy to find. Reset To Device Device "raidport2" Was Issued I logged into my server and checked the event log, I noticed Event ID 129 with the following description: Event Type: Warning Event Source: HpCISSs2 Event Category: None Event ID: 129

But he has replaced the Disk for me, and it will hopefully arrive tomorrow. Maybe this is a hardware issue on the HBA?? Let’s discuss the Windows I/O stack architecture to answer this. Check This Out The volume manager then translates the volume offset to a block number on the disk and passes the request to the disk driver.

While the log says the source is "HpCISSs2" it is actually occuring when the storport driver (which sits above the HpCISSs2 driver in the driver stack) sends down a reset to If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity Backup UPS - email alert 3 107 2016-11-01 FUN QUESTION. A quick check of the eventlog show a lot of warning event 129 from HpCISSs2 source. The active node in the cluster is posting Event ID 129 with Event Source ql2300.

That's the only Source with which I'm experiencing this error at the moment. Where can I find Boeing 777 safety records? I have a very nice 2009 vintage Dell XPS-1340 with GeForce 9400M G motherboard and Nvidia graphics. Therefore, removing/disabling the McAfee Antivirus software resolves the LUN resets leading to the HpCisss2 Event ID 129 errors logged in the Windows OS System Event Log.

Just upgraded that and hopefully those errors will go away. 0 Kudos Reply jwo Visitor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend I had to practically argue with HP support to have them send me a spare drive. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name x 1 Anonymous Hard drive failure was causing this warning for me.

Was your last reboot 3 weeks ago? So, as long as requests complete the timer will never go to zero. This is a File server running Windows 2003 R2 SP2. However, the fact that the server reported unresponsive when event 129 (even though its only warning) was firing does relate it to the server hang.

Thanks in advance hardware-raid share|improve this question asked Mar 11 '14 at 19:04 user211377 164 Were you ever able to find a resolution for this? The forum post you point to was for a VSS problem on Server 2008 and does not involve Server 2012. The disk driver imbeds the CDB into a structure called the SCSI_REQUEST_BLOCK (SRB). After theupdate, thefirmware is on 6.62 and the driver is

Some vendors will tune this value to best match their hardware, we do not advise changing this value without guidance from your storage vendor. Building scatter gather arrays for data buffers. You may be able to use the /AUXSOURCE = flag to retrieve this description; The following information is part of the event: \Device\RaidPort0."Pl help Monday, December 14, 2009 12:00 PM Reply