![](/images/new-backgrounds/1187338/187338413x1.webp)
6 |
Table 6-10. Exception Log Event Codes - Continued
Log Event |
|
|
Code |
| Possible Cause and Resolution |
Event ª1cº | 2c | ªBadremoteapplicationrequest;discardedrequestº |
ChannelAPI |
| Mailbox traffic of unexpected type arrived from the remote ServiceRequest |
events |
| Processor. Entry 3 identifies the aborted channel number. Entry 4identifies |
(Continued) |
| the traffic type. |
| 2d | ªBadlocalapplicationrequest;discardedrequestº |
|
| A segment selector that the Channel API does not support was used in |
|
| specifying the COMMREQ Status Word reference address. Entry 3 contains |
|
| the offending segment selector code value. Entry 4 contains the |
|
| COMMREQ command value of the command using the offending segment |
|
| selector. |
| 2f | ªBadlocalapplicationrequest;discardedrequestº |
|
| Could not write the CRS word of a Channel COMMREQ command. Entry 3 |
|
| identifies the channel number. You should check your application to make |
|
| sure it is using a legal CRS word pointer in its Channel command for the |
|
| indicatedchannel. |
| 30 | |
|
| Internal error: An unexpected state was encountered in a Channel Machine. |
| 31 | (Not reported to PLC Fault Table) |
|
| Internal Error: An attempt to allocate a new action class failed. |
TCP/IP Ethernet Communications User's Manual ± January 1996 |
|