topic Re: HP iLO Passthrough Service after Windows Server Service Pack 1 in Server Management - Remote Server Management

HP iLO Passthrough Service after Windows Server Service Pack 1

kent as — Wed, 20 Apr 2005 09:02:11 GMT

Hi,

Does anyone know how to fix this error?
After installing SP1, the HP iLO Passthrough Service no longer starts after reboot. The only way to make it work is to manual restart the HP iLO Passthrough Service after the server has rebooted. That's not a good solution for a Remote Desktop function.
Same problem no matter which firmware used, now running 1.75 on both DL380G3 and DL360G4.

Event Type: Error
Event Source: hplopts
Event Category: (1001)
Event ID: 4
Date: 2005-04-20
Time: 15:36:48
User: N/A
Computer: POPAPP2
Description:
Exception in Passthrough thread.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 54 65 72 6d 69 6e 61 6c Terminal
0008: 20 53 65 72 76 69 63 65 Service
0010: 73 20 69 73 20 6e 6f 74 s is not
0018: 20 72 75 6e 6e 69 6e 67 running
0020: 2e 20 3a 3a 20 20 20 20 . ::
0028: 61 74 20 53 79 73 74 65 at Syste
0030: 6d 2e 45 6e 76 69 72 6f m.Enviro
0038: 6e 6d 65 6e 74 2e 47 65 nment.Ge
0040: 74 53 74 61 63 6b 54 72 tStackTr
0048: 61 63 65 28 45 78 63 65 ace(Exce
0050: 70 74 69 6f 6e 20 65 29 ption e)
0058: 0d 0a 20 20 20 61 74 20 .. at
0060: 53 79 73 74 65 6d 2e 45 System.E
0068: 6e 76 69 72 6f 6e 6d 65 nvironme
0070: 6e 74 2e 47 65 74 53 74 nt.GetSt
0078: 61 63 6b 54 72 61 63 65 ackTrace
0080: 28 45 78 63 65 70 74 69 (Excepti
0088: 6f 6e 20 65 29 0d 0a 20 on e)..
0090: 20 20 61 74 20 53 79 73 at Sys
0098: 74 65 6d 2e 45 6e 76 69 tem.Envi
00a0: 72 6f 6e 6d 65 6e 74 2e ronment.
00a8: 67 65 74 5f 53 74 61 63 get_Stac
00b0: 6b 54 72 61 63 65 28 29 kTrace()
00b8: 0d 0a 20 20 20 61 74 20 .. at
00c0: 68 70 6c 6f 70 74 73 2e hplopts.
00c8: 50 61 73 73 74 68 72 75 Passthru
00d0: 2e 4c 6f 67 45 78 63 65 .LogExce
00d8: 70 74 69 6f 6e 28 45 78 ption(Ex
00e0: 63 65 70 74 69 6f 6e 20 ception
00e8: 65 2c 20 45 76 65 6e 74 e, Event
00f0: 4c 6f 67 45 6e 74 72 79 LogEntry
00f8: 54 79 70 65 20 74 79 70 Type typ
0100: 65 2c 20 53 74 72 69 6e e, Strin
0108: 67 20 65 78 63 65 70 74 g except
0110: 69 6f 6e 4d 65 73 73 61 ionMessa
0118: 67 65 2c 20 49 6e 74 33 ge, Int3
0120: 32 20 6d 73 67 4e 75 6d 2 msgNum
0128: 62 65 72 29 0d 0a 20 20 ber)..
0130: 20 61 74 20 68 70 6c 6f at hplo
0138: 70 74 73 2e 50 61 73 73 pts.Pass
0140: 74 68 72 75 2e 50 61 73 thru.Pas
0148: 73 74 68 72 75 54 68 72 sthruThr
0150: 65 61 64 28 29 ead()

Re: HP iLO Passthrough Service after Windows Server Service Pack 1

Derek_31 — Thu, 21 Apr 2005 19:12:21 GMT

I think the problem is that the iLO thread starts before the terminal server service starts. Maybe make the iLO service dependent on the TS service?

Re: HP iLO Passthrough Service after Windows Server Service Pack 1

kent as — Fri, 22 Apr 2005 09:20:01 GMT

Yes!
That did the trick, thank you.

Re: HP iLO Passthrough Service after Windows Server Service Pack 1

acartes — Tue, 26 Apr 2005 17:13:45 GMT

Good call. The passthrough service is dependent on the driver, and apparently the load timing is different with Windows 2003 SP1.

Manually creating the dependency is a good permanent workaround.

You can also start/stop the passthrough service to correct this on-the fly.

A future release of the pass-through service component will fix this problem, probably by adding the dependency.

Re: HP iLO Passthrough Service after Windows Server Service Pack 1

acartes — Thu, 28 Apr 2005 16:59:03 GMT

The HP iLO Terminal Services Pass Through service is is dependent on Terminal Services to start (no big surprise).

However, the dependency is not explicitly listed for the service (via registry entry), and sometimes it tries to start before Term Svcs and errors out, the error message (1001) actually states Terminal Services is not running.

You could add a registry addition:

HKLM\SYSTEM\CurrentControlSet\Services\hplopts /v DependOnService /t REG_MULTI_SZ /d "TermService"

to address this. You will have to evaluate the decision for your circumstance.

This change will be incorporated in the component installer package in a forthcoming release of the Terminal Services Passthrough component from HP. I'll update this message then.

An alternate workaround is to manually stop the pass-through service, and then start it. This will work for a single OS boot.