Get Started!

˂ Return to FAQ

Below is a list of possible errors reported in the Job Details page. Click the error response message or code below to skip down to its section where further explanation and possible resolutions are located.

If your specific error is not found or the resolutions are still not working as expected, please contact our Support Team for further assistance.

Job Error Responses:

 
 

Response error: 401

The 401 error response is usually associated to an Unauthorized response from the remote host. The following reasons may be the root cause for this error:

1

The User or Password associated to the record (or shadow account) is either incorrect or does not have the permissions to connect to the remote host. To troubleshoot, attempt to establish a Secure Connection using this record to the remote host. If that fails, then Edit the record, modify the User or Password and then try again. For Windows tasks, try using the format DOMAIN\user or user@domain.com for the User parameter in the record.

2

The user or shadow account used for this Task does not have the Windows permission to execute a remote PowerShell command. To troubleshoot, ensure this user or shadow account is a member of the local Windows group “Remote Management Users” on your remote host and then try again. Some scripts may require additional permissions, so adding this account to the “Administrators” group may also help to resolve the error.

3

Remote Windows task are sometimes executed using the Windows Remote Management protocol and this needs to be enabled on the host. To do so, run the following command on this Windows host: Winrm quickconfig . WinRM, by default, uses the ports 5985/5986 so these must be open between the XTAM host server and your endpoint.

 
To troubleshoot a 401 response error, consider trying the following:

1

From the XTAM host server itself, open a PowerShell session (run as administrator) and execute the following command. Replace the bolded values with those from your XTAM record.

Invoke-Command -ComputerName remote-host -Credential domain\user -ScriptBlock {dir \}

If the above command executes successfully, meaning PowerShell does not return any error messages, then it will display a list of directories in the root drive of the remote host.

If the above command does not execute successfully, then that may indicate an issue wth the network’s Windows Remote Management (WinRM) configuration. Try to understand and troubleshoot the error message that PowerShell returns. If you are stuck, consider trying the following:

2

From the XTAM host server itself, open a PowerShell session (run as administrator) and execute the following command. Replace the bolded values with those from your XTAM record.

Set-Item -Path WSMan:\localhost\Client\TrustedHosts -Value 'remote-host'

This command will add your remote-host computer to the trusted hosts list in the server’s WinRM configuration. After this command is executed successfully, try executing your record’s Task in XTAM again.

 
 

Response error: Cannot perform this operation at this time

When attempting to reset the password on an AS400 host, this message may appear if the Password policy does not allow for the password to be updated at this time. To troubleshoot, either wait until the policy on the AS400 host allows for the password to be updated or modify the policy to allow more frequent updates and then try again.

 
 

Response error: The user or administrator has not consented to use the application with ID

When attempting to reset the password on an Azure or Office 365 Administrative account, the operation fails because permissions have not been fully granted to the Application. To troubleshoot, login to your Azure Portal (as an Administrator), open our XTAM App you created earlier, click All Settings > Required Permissions > Grant Permissions and then Yes to confirm. Once complete, try the password reset again.

 
 

Response error: Verification Error: Exception calling “ChangePassword”

This can commonly be the error response when attempting to a change password in a Windows domain where the new password does not meet the requirements of your Local or Domain Security policy. For example, this could be the password age (resetting to frequently) or complexity (formula not strict enough). To troubleshoot, log in to this Remote host and attempt to manually change the password. If it fails to update manually, check the Password Policy on this Local computer or the Domain Controller to ensure the new password meets its minimum requirements.

Of particular importance, if your Password Policy has the policy Password must meet complexity requirements set to Enabled, then you must configure your XTAM formula to comply with this policy. This means that your formula must meet at least 3 out of the following 4 requirements:

  • Minimum Number of Upper Case Characters: 1 or greater
  • Minimum Number of Lower Case Characters: 1 or greater
  • Minimum Number of Numeric Characters: 1 or greater
  • Minimum Number of Special Characters: 1 or greater

 
 

Copyright © 2019 Xton Technologies, LLC. All rights reserved.