Troubleshooting the On-Need Assessments

  • Article
  • 10 minutes to read

Download the Assessment Troubleshooting Script

Delight download and run the Assessment Troubleshooting script to self-evaluate and troubleshoot the On-Need Assessments. Refer to the full troubleshooting guide below:

The below steps would walk you through from showtime to finish and make y'all verify the correctness of each requirements that are to be met in running the On-Need Assessments:

The most common issues we see users encounter are: (Guidance on how to resolve them is mentioned below in the article)

  1. When you run the assessment but see no data in Log Analytics -> Restart healthservice if information files are awaiting ingestion.

  2. Error message: "You dont have access to Azure Log Analytics" in Services Hub -> IT Health -> On-Demand Assessments.

Microsoft Monitoring Amanuensis (MMA) Installation bug

Sometimes when installing MMA Agent, it cannot successfully connect to the workspace when specifying the credentials (Id and Key) of the Azure Log Analytics (OMS) workspace. A workaround which sometimes works is to remove the WorkspaceId and the key and install MMA without specifying any workspace. Then, open the MMA control panel past going to Command Console, Security & Settings, Microsoft Monitoring Agent, Azure Log Analytics (OMS) tab and add the desired workspace by specifying its ID and Fundamental. Then click the Apply push and verify that the green checkmark appears.

Linking and Permissions

  1. Click this link to scout the video to pre-configure your On-Demand Assessments.
  2. Verify that you have the Azure Subscription Owner function on the Azure Subscription on the same email ID that yous use to login into Services Hub.
  3. Yous should be able to see the beneath page in Services Hub nether the Health tab then Assessments upon successful linking.
  4. Ostend that the Log Analytics workspace you accept access to is the one that is linked in Services Hub. If not, ask them to relink by clicking on profile at the elevation correct so click Edit Log Analytics Workspace and link the desired workspace.
  5. Confirm that you have added the desired cess from the itemize.
Assessments results dashboard Available On-Demand Assessments Active Directory Assessment description

Some of the almost frequent issues when a command such as AddExchangeAssessmentTask is invoked, are described next:

Windows Server 2008 R2 does non recognize Add-*AssessmentTask commandlets

It is recommended not to run assessments on a Windows Server 2008 machine. But when yous absolutely demand to, you need to do the post-obit:

  1. Install latest version of Powershell and .cyberspace 4.6.two on the Windows 2008 server. Most Windows 2008 Servers accept Powershell which uses .net 2.0 and that does not meet the requirements.
  2. Run Powershell in Ambassador style.
  3. Before invoking any Add-*AssessmentTask commandlets issue:
    Import-Module $env:ProgramFiles\'Microsoft Monitoring Agent\Agent\PowerShell\Microsoft.PowerShell.Oms.Assessments\Microsoft.PowerShell.Oms.Assessments.dll'

After this command is executed, yous should be able to invoke Add-*AssessmentTask commandlets.

On any platform, if the Add-*AssessmentTask commandlets are non recognized

  1. Verify that the OMS Assessments Powershell module has been downloaded. To do this, verify that $env:ProgramFiles\'Microsoft Monitoring Agent\Agent\PowerShell' has a subdirectory named Microsoft.PowerShell.Oms.Assessments and in that subdirectory at that place is a file named Microsoft.PowerShell.Oms.Assessments.dll, like shown in the screenshot below:
PowerShell Window demonstrating correct Working Directory and Subdirectory ii. If Microsoft.PowerShell.Oms.Assessments.dll is non in that location, then brand sure that your Log Analytics workspace is linked from Services Hub. 3. Verify that *$env:PsModulePath* contains $env:ProgramFiles\\'Microsoft Monitoring Agent\Agent\PowerShell'. 4. Verify that the installed version of PowerShell is at least 4.0 (Only blazon *$PsVersionTable* in the Powershell window) and that Powershell uses CLRVersion equal to or greater than 4.0. ### Troubleshooting Cess Installation Errors when executing an Add-*AssessmentTask cmdlet ###
  1. Read the log file.
  2. The log file location is displayed on the Powershell console window. It is just an informational bulletin -- in white. Meet this location in the sample screenshot below:
PowerShell Windows displaying file location

Note

If Add-AssessmentTask fails for some reason, look at the log file.

  1. The -ScheduledTaskUserName and -ScheduledTaskPassword may be invalid -- no such user exists or the password is invalid, or has expired.
PowerShell Windows displaying user error message

Requirements for successfully running the scheduled chore

Verify the user account Group Policies: Logon as Batch Job Permission

Annotation

At times, the cess may not get triggered from the Task Scheduler. This may happen if the user does not have running batch job permission. If that'due south the instance, this permission needs to be explicitly granted by going in here from gpedit.msc.*

Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment

  1. Right click on "Log on equally batch job" and select Properties.
  2. Click "Add User or Group" and include the relevant user.

Practice not forcefully unload the user registry at user logoff

On the data collection machine, modify the post-obit setting in the group policy editor (gpedit.msc) from "not configured" to "enabled"; go to Estimator Configuration, Administrative Templates, System, and and then User Profiles.

'Practise not forcefully unload the user registry at user logoff'

Disable the FIPS Policy

  1. In Control Panel, click Administrative Tools and and then double-click Local Security Policy.
  2. In Security Settings, aggrandize Local Policies and then click Security Options.
Local Security Policy window displaying Security Options folder 3. Under Policy in the right pane, double-click System cryptography; use FIPS compliant algorithms for encryption, hashing, signing, and and so click Disabled. ### Network Access: Do not allow storage of passwords and credentials ### 1. This mistake occurs with the bulletin, "A specified logon session does not exist. It may already accept been terminated." 2. To resolve this, get to SECPOL.MSC, Security Settings, Local Policies, so Security Options. three. Exercise not allow storage of passwords and credentials for network authentication. Local Group Policy Editory window 4. Prepare the policy to disabled.

Assessment has non been added to your workspace

If invoking the beginning-XXXAssessment results in this error: "There is no file XXXAssessment.execPkg associated to the current Log Analytics workspace ... " as in the screenshot below, the reason is that the specific assessment-type must be added to the Log Analytics workspace to which the Microsoft Monitoring Agent is currently connected. Add the assessment on the ServicesHub page. (Dropdown the Wellness tab and and then cull Assessments. At the end of the page, click on the desired cess that is listed under "Bachelor On-Demand Assessments" and and so on the modal dialog that appears for calculation the selected assessment, click "Add Assessment") Then wait at to the lowest degree 10 minutes before attempting to start the assessment. The delay is required to allow the MMA Agent to contact Log Analytics and download the Management Pack which contains the XXXAssessment.execPkg. PowerShell window with a no file associated error message

Cess Task Running Issues

Inactive / No Information found in Azure Log Analytics

Verify Log Analytics Agent connectivity

To ensure that the agent tin communicate with Azure Log Analytics, go to Control Panel, Security & Settings, and Microsoft Monitoring Agent. Under the Azure Log Analytics (OMS) tab, look for a greenish cheque mark.

Microsoft Monitoring Agent Properties window displaying green check mark

A greenish check marking icon confirms that the agent is able to communicate with the Azure service.

A xanthous warning icon means the amanuensis is having issues communication with Log Analytics.

Look at the Heartbeat letters from the AgentHealthAssessment solution

When you lot add the AgentHealthAssessment solution to your Log Analytics workspace through Azure Portal, y'all volition see useful information, including a list of computers with unresponsive agents and the last successful-heartbeat time for each of these unresponsive machines.

Log Analytics dashboard displaying heartbeat messages

If your car is listed there, ane common reason for this is that the Microsoft Monitoring Agent service (HealthService) has stopped. Use service control manager to restart the service.

If you have a firewall restriction in place, brand sure the below ports are opened up:

  • mms.microsoft.com, Log Analytics portal
  • workspaceId.ods.opinsights.azure.com, Data Collector API
  • *.ods.opinsights.azure.com, Amanuensis communication - configuring firewall settings
  • *.oms.opinsights.azure.com, Agent advice - configuring firewall settings
  • *.blob.core.windows.internet, Amanuensis communication - configuring firewall settings

This can easily exist verified past invoking the TestCloudConnection.exe tool which is in the Microsoft Monitoring Agent\Agent\ folder, as in this screenshot:

Command Prompt for VS2015

Information from OnDemand assessment is no longer seen in Log Analytics, just it was seen in the past

Discover the scheduled task in the Task Scheduler and run the task manually from the Task Scheduler. Verify that an OmsAssessment.exe process is running. If no such process is running and so one possible reason is that the password specified at the fourth dimension the Add together-XXXAssessmentTask was run for this assessment is no longer valid (e.thou. has expired or has been inverse) If this is the case, you volition be able to see the mistake both on the History tab of the Job Scheduler, and also in the Chore Scheduler Event Log -- with EventId 101 (and 104) and ErrorValue: 2147943726 -- every bit shown on the next two screenshots:

Task Scheduler Launch Failure Task Scheduler Launch Failure Error Details

Restart healthservice if data files are pending ingestion

Please close all active PowerShell windows on the motorcar. At present, if you check the working directory of the Assessment and find the files with names like new.recommendations.*** (see screenshot beneath):

Open Command Prompt in Administrator mode and blazon in the below: cyberspace finish healthservice internet start healthservice

Afterward running the below command, the files would alter to be processed as shown below which means the files have been ingested successfully and information should be visible on Log Analytics in nigh thirty minutes.

Assessments folder with numbered folder highlighted Command Prompt dialog Assessments folder and targets

Cheque for any alien omsassessment.exe processes running

Open upwardly Chore Manager and look for a process named as omsassessment.exe. If found it indicates that the cess is nonetheless running.

If it has been quite long (for eg, if yous discover this process has been running for over a day), it is possible that the cess agent could non process data. And so please proceed to the side by side troubleshooting steps below.

Go through any errors in the prerequisite file

Go to the cess working directory and wait at the pre-requisites (processed.prerequisites) files to discover any errors mentioned for the assessment targets.

Assessments folder process.prerequisites

If any errors are plant, for instance WMI connectivity issues, the target names and the fault would exist mentioned in this file. Delight resolve this and and then trigger the assessment; from the Task Scheduler, expand Microsoft, Operations Direction Suite, AOI***** , so Assessments to right click on the desired assessment scheduled job and click run.

Go through error in the discovery log file

Go to the assessment working directory and go into the half dozen-8 digit numbered binder inside the directory. Look for a folder called as Logs within which you will find a file named as DiscoveryTrace*** .

Look for any errors or exceptions in this file and resolve them since they would be related to credential/permissions issue, WMI failure, network result etc.

Big file ingestion

If the below files processed.recommendations.*** size is greater than 250MB, the files might be hard to exist candy by the Log Analytics Amanuensis. If you lot come across this scenario and are not able to run into the data in Log Analytics please contact serviceshubteam@ppas.uservoice.com and permit us know near your effect.

Assessments folder displaying file size

Effort to reduce the number of targets per assessment schedule

If you are running the Windows Server, Windows Customer or SQL Assessment and have added more than 5 targets in a unmarried scheduled job, sometimes its possible that the assessment agent would not exist able to process so many targets in one go. If you run into this scenario, delight use the below cmdlet to remove any existing configuration:

Remove-WindowsClientAssessmentTask Remove-WindowsServerAssessmentTask Remove-SQLAssessmentTask

Now run the Add-AssessmentTasks over again with fewer targets. Yous can add together multiple such tasks and create batches of tasks with iii-5 targets per task which would result in a quicker evaluation of your entire surround.

Become through Scheduled Job dispatch and uploader log files

In the Assessments working directory, there is a \Logs\ folder which contains *Commandlet*.log and *Module*.log. The *Commandlet*.log file contains data about the scheduled job starting the Powershell commandlet and this can be used to find why the scheduled task did not kickoff. If this file is not produced when the ODA scheduled task is started, it usually indicates a password error.

The *Module*.log file contains data about the Health Service and its attempts to upload data to the Azure Log Analytics cloud.

The Applications and Services Logs\Operations Manager Upshot Log besides contains information which tin be used to troubleshoot various bug.

For general feedback on the Resource Centre or content, please submit your feedback to your Microsoft representative. For specific requests and content updates regarding the Services Hub, contact our Back up Team to submit a instance.