If you are on AA 8.8.1, alerts are not working and can not open the AA console.
it shows the error message as "An error occurred while connection to AFS server"
In AFS logs, the below error will be seen.
Unhandled Exception!
Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Load(TextReader textReader, LoadOptions options)
at Quest.AA.AFS.ASM.ADHealth.Analyzer.DANotificationProvider.GetNotificationDocument()
at Quest.AA.AFS.ASM.ADHealth.Analyzer.DANotificationProvider.GetNotifications(Boolean lockFile)
at Quest.AA.AFS.ASM.ADHealth.Analyzer.DANotificationProvider.AddSCOMNotification()
at Quest.AA.AFS.Loader.<>c.<<CreateDefaultScomNotification>b__37_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
This looks like SCOM notifications xml document has been corrupted somehow. Note here that even if you have not set any SCOM notifications there should be a default blank document containing no notification data, this file is created by the system if it does not exist.
In this case, as the error is an xml root node error it is likely that the start of the xml, or a node in the xml is improperly formed. This could happen when something, either AA or some user directly, edits the Notifications file and does not preserve the formatting correctly
To repair please try the following:
1) Go to ActiveAdministrator share. In there to DACache and in here find Notifications.xml
2) Copy Notifications.xml to another filename, ie. Original_Notifications.xml
3) Restart the AFS service. When it starts up it will register that the file is missing and rebuild a new one.
4) Compare the new and old Notifications xml files. If you had any notifications set it should be possible to see where the formatting became incorrect, correct it, and then restore the original file by removing the new Notification.xml and renaming the old file back.
