Chapter 6
MtcDsl Messages
96
IOPn.MtcDsl Status Message Summary
The following table lists the HP NetServer AA server MtcDsl messages in the order that they
are documented.
Table 6-1 IOPn.MtcDsl Message Summary
Message
Page
IOPn.MtcDsl status: A packet with an invalid transport command was received (offendingValue).
page 98
IOPn.MtcDsl status: A provider has an invalid Registry entry (provName).
page 98
IOPn.MtcDsl status: A provider has attempted to register more than once (provName).
page 98
IOPn.MtcDsl status: A request contained an invalid provider ID (offendingValue).
page 99
IOPn.MtcDsl status: A request for provider provName used an invalid logical device ID.
page 99
IOPn.MtcDsl status: A request for provider provName used an invalid physical device ID.
page 100
IOPn.MtcDsl status: A tack timeout condition was not cleared properly.
page 100
IOPn.MtcDsl status: A tacked flush packet has an unknown flush type (offendingValue).
page 100
IOPn.MtcDsl status: An invalid client callback ID was encountered (offendingValue).
page 101
IOPn.MtcDsl status: An invalid component state was encountered (offendingValue).
page 101
IOPn.MtcDsl status: An invalid component type was encountered (offendingValue).
page 101
IOPn.MtcDsl status: An invalid DSL packet ID was encountered (offendingValue).
page 102
IOPn.MtcDsl status: An invalid IOP state was encountered (offendingValue).
page 102
IOPn.MtcDsl status: An invalid logical device operation type was encountered (offendingValue).
page 103
IOPn.MtcDsl status: An invalid packet descriptor was encountered.
page 103
IOPn.MtcDsl status: An invalid reset reason code was encountered (offendingValue).
page 103
IOPn.MtcDsl status: An invalid resync flush state was encountered (offendingValue).
page 104
IOPn.MtcDsl status: An invalid subprovider ID was encountered (offendingValue).
page 104
IOPn.MtcDsl status: An invalid transaction ID was encountered (offendingValue).
page 104
IOPn.MtcDsl status: Invalid device entries in the IOP’s configuration were pruned. This indicates an
improperly set up device configuration. This problem may have occurred due to hand modifications
of the Windows NT Registry. The problem may be fixed by re-running the HP NetServer AA
Configuration Utility.
page 105
Содержание NetServer AA 4000
Страница 1: ...HP NetServer AA Solution Messages HP Part Number 5969 5966 Printed in September 2000 ...
Страница 6: ...Contents vi ...
Страница 8: ...Tables viii ...
Страница 52: ...Chapter 1 Introduction 42 ...
Страница 70: ...Chapter 2 MIC BIOS Messages 60 ...
Страница 98: ...Chapter 4 MtcCEX Messages 88 ...
Страница 119: ...109 Chapter 6 MtcDsl Messages ...
Страница 120: ...Chapter 6 MtcDsl Messages 110 ...
Страница 154: ...Chapter 8 MtcEvtP Messages 144 ...
Страница 162: ...Chapter 9 MtcFLOP and MtcFLOR Messages 152 ...
Страница 166: ...Chapter 10 MtcIopDm Messages 156 ...
Страница 372: ...Chapter 16 MtcVidP Messages 362 ...
Страница 378: ...Chapter 17 MtcVnP Messages 368 ...