ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Cannot publish changes to domain list. XML Parse errors in BrightmailLog.log

book

Article ID: 213638

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

Attempting to modify the domains list in Protocols > Domains results in an error indicating that the change has been saved but could not be published:

Control Center error:

Configuration saved successfully but could not publish configuration to the following hosts - smg.lab.bcp. Please check control center logs for details.

 

BrightmailLog.log

Apr 13 2021 11:30:19 [PublishingThread-74] [PublisherJob] ERROR - can't publish configuration to host: smg.lab.bcp
com.symantec.smg.controlcenter.BrightmailException: Cannot parse invalid XML. ; nested exception is:
             org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 3; The element type "domain" must be terminated by the matching end-tag "</domain>".
             at com.symantec.smg.controlcenter.internal.xml.Parser.parse(Parser.java:458)
             at com.symantec.smg.controlcenter.internal.xml.Parser.parse(Parser.java:406)
             at com.symantec.smg.controlcenter.agent.AgentResponseHandler.<init>(AgentResponseHandler.java:403)
             at com.symantec.smg.controlcenter.agent.AgentCommandImpl.getResponse(AgentCommandImpl.java:115)
             at com.symantec.smg.controlcenter.agent.ReloadComponentDataCommand.getResponse(ReloadComponentDataCommand.java:48)
             at com.symantec.smg.controlcenter.agent.RequestResponseHandler.createResponse(RequestResponseHandler.java:85)
             at com.symantec.smg.controlcenter.agent.AgentEvent.processRequestResponse(AgentEvent.java:1264)
             at com.symantec.smg.controlcenter.agent.AgentEvent.reloadComponentData(AgentEvent.java:228)
             at com.symantec.smg.controlcenter.host.ComponentHelper.reloadComponentData(ComponentHelper.java:201)
             at com.symantec.smg.controlcenter.host.mta.MtaComponent.reloadComponentData(MtaComponent.java:163)
             at com.symantec.smg.controlcenter.host.publishing.KickManager.kick(KickManager.java:312)
             at com.symantec.smg.controlcenter.host.publishing.PublisherJob.run(PublisherJob.java:97)
             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
              at java.util.concurrent.FutureTask.run(FutureTask.java:266)
             at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
             at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
             at java.lang.Thread.run(Thread.java:748)

 

Cause

This is due to a duplicate domain entry in the Protocols > Domains table. Under normal circumstances, a duplicate domain cannot be created but if a duplicate in some way gets into the SMG configuration via a domain import it will prevent the domains table from being properly formatted and exported to the scanners

Environment

Release : 10.7.4

Component :

Resolution

Deleting one of the duplicate domain entries will resolve the XML parse error and allow the domains table to be published to the scanners.

Attachments