Stream Connect message replication status stopped<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Validate connectivity and bootstrap consuming/producing on the MID host Validate ports are reachable:https://www.servicenow.com/docs/r/zurich/servicenow-platform/multi-instance-framework-hermes/producing-consuming-hermes.htmlRequired port rangesWork with your network administrator to ensure that the following port ranges are open before you begin exchanging messages using Hermes:Producer: 4000-4050Consumer1: 4100-4150Consumer2: 4200-4250 To confirm that the ports are accessible through the firewall, run the following command:openssl s_client -connect <instance_name>.service-now.com:<port> -servername <instance_name>.service-now.com Note: Perform the same for your external kafka broker configured for replication. Use native Apache kafka to test topics are able to be consumed and produced to using the configured kafka credentials:https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3097219 Validate the MID server user is able to read the required instance records to create the kafka connections and establish replication Determine if the MID server is unable to retrieve the records via the agent logs on the MID server for any errors related to RemoteGlideRecord. For example:{RemoteGlideRecord:1234] Can't read because table ACL denies it: sys_properties MIDRemoteGlideRecord.query failed with error: Method failed: (https://instance.service-now.com/kafka_connection.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 500 Internal Server Error with code: 500, retrying in 75 seconds The MID server user requires read access for the following tables:sys_properties — get instance_name kafka_connection — find connections assigned to this MID sys_kafka_topic_replication — find active topic replication channelssys_sc_message_replication — load config for each channel Read access to the relevant replication kafka tables should be available via the role "message_replication_user".ACL customizations may lead to the MID user being denied read access to these tables, validate any custom ACLs related to these tables. MID debug logging for message replication:Configuration parameter: mid.log.level = info,org.apache.kafka=debugProperty: glide.stream_connect.message_replication.debug = true