This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
We've confirmed that all systems are back to normal with no customer impact as of 12/04, 07:30 UTC. Our logs show the incident started on 11/21, 19:34 UTC and that during the 13 days and 12 hours that it took to resolve the issue some of customers experienced exception while accessing the free assessments.
- Root Cause: The failure was due to an issue with one of our dependent service.
- Incident Timeline: 13 days & 12 hours- 11/21, 19:34 UTC through 12/04, 07:30 UTC
We are aware of issues within Log Analytics and are actively working on mitigation. Some customers may continue to experience exceptions while accessing the free assessments.
- Next Update: Before 12/04 11:30 UTC
We continue to investigate the issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience exceptions while accessing the free assessments.
- Next Update: Before 12/04 07:30 UTC
We are aware of issues within Log Analytics and are actively investigating. Customer will be facing exceptions while accessing the free assessments - Active Directory Health Check, SQL Health Check, AD Replication Status, System Center Operations Manager Health Check, through Microsoft Monitoring Agent and SCOM Agent.
'Microsoft.EnterpriseManagement.Mom.Modules.AdvisorAssessmentExecuter.ProbeAction.AdvisorAssessmentExecuterProbe' reported an exception System.Exception: [ADAssessment]Failed to run AdvisorAssessment.exe or generate output DataItem(s). ---> System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\\Program Files\\Microsoft Monitoring Agent\\Agent\\Health Service State\\Monitoring Host Temporary Files 1\\4\\3311548'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetDirectories(String path)
We are working hard to resolve this issue and apologize for any inconvenience.