Event ID 5 - iSCSI error on HP Server connected to HP MSA2012i

[pjscott13]

Hi There,

I have recently configured a MSA 2012i device for our network and have run into a couple of errors in the event logs of the servers that connect to this device. These errors in the event logs though do not seems to be actually causing any issues as everything works as it should.

The first error goes along the lines as this:

Event Type: Error
Event Source: iScsiPrt
Event Category: None
Event ID: 5
Date: 12/12/2009
Time: 22:02:08
User: N/A
Computer: SERVERNAME
Description:
Failed to setup initiator portal. Error status is given in the dump data.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 00 00 04 00 01 00 5e 00 ......^.
0008: 00 00 00 00 05 00 00 c0 .......À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 07 02 00 c0 ...À



I generally receive the above error upon starting the server up. The next error that I receive which is slightly more annoying, as this causes a pop up message on the server at startup saying "One or more services failed to start". By the time I get into the event log to see which service failed to start and then check if the service has actually started, the Service has actually started on it's own without my intervention.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: 12/12/2009
Time: 22:03:56
User: N/A
Computer: SERVERNAME
Description:
The CAPI Proxy service hung on starting.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Is there anyone else experiencing this issues? Or does anyone know how I can avoid receiving these alerts?

 

[jtoelle]

Did you ever get this resolved?

http://howtodrawanimals.net

http://howtodrawcoolcars.com

http://drawingforkids.net

 

[pjscott13]

Nope... never got this resolved. I have to admit though, that the Service failed to start message doesn't occur as often now... but the first message is still there.