Troubleshooting

The following logs can be used to troubleshoot issues with AMI integration:

• C:\inetpub\logs\LogFiles\W3SVC1 –

• C:\Responder\Logs

  • Miner.Responder.RxIF.AmiService.log – verify AMI service is processing events.

  • Miner.Responder.RxIF.AmiOutbound.log – verify event data from HTTP endpoint.

• C:\Responder\Logs

  • Miner.Responder.RxIF.ScadaService.log – verify SCADA service is processing events.

  • Miner.Responder.RxIF.ScadaOutbound.log – verify device status of devices from SCADA HTTP endpoint.

• Computer Management Event Viewer.

  • Application and Service Logs – Miner.

    • MSMQ Timeout errors.

    • Service Failure errors.

    • Other Miner errors.

The following tools can be used for troubleshooting or resetting queues:

• Fiddler – Fiddler can be used to capture traffic during high periods of AMI event traffic to HTTP endpoint. The data sent by GE can be examined XML tab of Inspectors to see full content of XML packets sent to SE.Responder.Integration.Cim/ReceiveEndDeviceEvents.svc.

• JMETER – JMETER can be used to send basic POWERUP/POWERDOWN or CONNECT/DISCONNECT commands internally to the HTTP endpoint. Use this tool to verify Responder is receiving and processing events.

• SQL Developer Tool:

  • RXINT_METER_EVENT table – verify events are entered into this table.

  • RXINT_METER_EVENT_HISTORY table – verify events are rolled into this table based on EventPersistDuration threshold.

• Delete Queues – C:\Program Files (x86)\Miner and Miner\Responder\Server\Tools

  • Use this tool to completely delete Responder Queues and rebuild. This is not recommended if there are any active calls or incidents in the system.

• Purge Queues - C:\Program Files (x86)\Miner and Miner\Responder\Server\Tools

  • Use this tool to purge messages in Queues. This can be used to remove messages that may be stale (red x).

• DeletePersistentCache.bat - C:\Program Files (x86)\Miner and Miner\Responder\Server\Tools

  • Use this tool to optimize performance and Responder caches feature class name/ID pairs should feature class names and/or IDs change (e.g., due to Replication).