Help Center


Invalid Service Account, Account Name and/or Password is Invalid or Does Not Exist

You receive any of the following errors:

  • Invalid service account.
  • The account used to start the service on the target computer is not valid, doesn't exist, or the wrong password was supplied.
  • The account name is invalid or does not exist, or the password is invalid for the account name specified. 


  1. Check that the user account information for the background service (PDQDeploy and PDQInventory services, respectively) is correct.
  2. If using domain credentials for the background service, ensure you have access to a domain controller in which to authenticate the service credentials. In certain instances, intermittent network issues will result in the error: "The account name is invalid or does not exist, or the password is invalid for the account name specified".

NOTE: Though very rare, this behavior can also occur if the PDQ console NIC is connected to a different network type as determined by Microsoft’s Network Location Awareness (NLA). This can result in a different firewall profile being used that blocks traffic required for domain access. Please check to ensure the PDQ console NIC is of the domain network type and not private or public. 

See Also:
Background Service Error
The Service Did Not Start Due to A Logon Failure

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0


    I have been directed to this page as I am experiencing this error when trying issues a remote command to uninstall software. The account that I am trying to use is a local administrator account on the target machine and is the same account that I use to successfully scan the machine. I have tried this on a few different machines and am getting the same result.

    Any help would be much appreciated.



  • 1


    Can you submit the error to us using the Diagnose or More Info link?  That will have some additional context to tell us where the error is occurring.

  • 0

    Also refer to as that issue gives the same error message.

    One of our machines had lost the Group Policy setting for 'Log on as a Service'. Adding the domain admin account back into the local policies on the machine corrected the issue.

Article is closed for comments.