Consolidator inbound message troubleshooting (27395)
Steps to troubleshoot Consolidator inbound message issues have been added to the 20.2 version of the Infor Cloverleaf Consolidator Administration Guide and are provided here.
Review these situations and possible solutions to troubleshoot problems with Consolidator inbound messages.
Collect information
- Identify the sources that are exceeding the threshold.
- Collect this source information:
- Assigned agent server health ( and ).
- Thread status: Active/Inactive ( )
- Interface Status: Active/Inactive (
- Message type is configured.
- Go to the Source page and identify which interface is assigned.
) - Source processing status ( )
- Windows Service: Infor Cloverleaf Consolidator
- Server up/down?
- Windows services
- Service status: Running
- Check
Source configuration scenarios
- Paused thread (STOPPED status)
- Example reasons for pausing a thread: Result code load, changing source agent assignment.
- Behavior: New and enqueued messages are held until thread is started or set back to GO.
- No error message.
- Notification will be sent if messages queued reaches the threshold.
- Message type is not configured or is not selected.
- Example reason for message type not configured: It is part of source enrollment, only certain messages types may be allowed.
- Behavior: New and enqueued messages will error.
- Error found in Message Manager: Message Type - Event not configured - Source Interface not returned from the Source Interface Service. Source Mnemonic: UHOACER. Sending SourceId: 10056. Sending Application: CERNER. Sending Facility: UHMANN. Message Type: HL7ADT.
- Source Processing Status source is inactive.
- Example reason for setting a source to inactive: Source is no longer trusted to send in data.
- Behavior: New and enqueued messages will error.
- Error in Message Manager: Source Processing Status Inactive - Source Interface not returned from the Source Interface Service. Source Mnemonic: UHOACER. Sending SourceId: 10056. Sending Application: CERNER. Sending Facility: UHMANN. Message Type: HL7ADT.
- Interface is inactive.
- Example reason for inactivating an interface: A single Interface can be used to stop multiple sources from processing messages.
- Behavior: New and enqueued messages will error.
- Error in Message Manager: Interface Status Inactive - Source Interface not returned from the Source Interface Service. Source Mnemonic: UHOACER. Sending SourceId: 10056. Sending Application: CERNER. Sending Facility: UHMANN. Message Type: HL7ADT.
Server configuration scenarios
- Consolidator service is not running (not set to AUTO).
- Example reason why service may not be running: During maintenance or upgrade to server, the service was stopped manually.
- Behavior observed: All messages queues that are associated with a specific server are increasing.
- Check Windows service:
- Service status: Running
- Alternate Fix: Manually re-assign source thread to active agent (server) from
- Consolidator assigned agent (server) is offline.
- Consolidator service is running.
- Behavior Observed: All messages queues associated with a specific server/agent are increasing.
- Fix: Restart server.
- Alternate Fix: Manually re-assign source thread to active agent (server) from .
License scenario
- Confirm that the license is valid. The license is invalid if the registered patient count reaches the limitation of the license.
- Behavior: All messages queues in all processing queues
- Fix: Request a new license.