DataFinder Won't Start: Internal Error (70) NI PSP Service Locator Cannot Start Properly

Updated Oct 4, 2022

Reported In


  • DIAdem
  • DataFinder Server
  • FlexLogger

Issue Details

  • When I open the Services window and try to start the NI PSP Service Locator I get the following error: Error 1069: The service did not start due to logon failure. How can I resolve this?
  • FlexLogger keeps crashing and gives me the following error (shown below)
  • When I run my DAQmx .NET example, I get the following error (shown below). How do I fix it?
  • When I try to create a Search Area in the DIAdem Navigator panel by right-clicking and selecting Add Search Area nothing happens, and if I navigate to the Settings>>My DataFinder I see options are grayed out.
  • I just installed DIAdem and when I open it I get the following error: 
The DataFinder cannot start due to an internal error.
(70): The NI PSP Service Locator could not be started properly as Windows service. Please try to restart DataFinder after a short while or reboot your computer. For more information, please refer to the NI Knowledge Base entry with the document ID 7G67K96M.


Make sure NI PSP Service Locator is running successfully. The account being used to allow the service to run may be invalid. You should check with your IT department to get valid login information.
As a workaround, run the service locally. To do so, navigate to Windows Services, right click the NI PSP Service Locator and select Properties. Select the Log On tab and choose to use the Local System Account. This may require Admin rights from your IT department.

Additional Information

A service account is a user account that is created explicitly to provide a security context for services running on Windows Server operating systems. The security context determines the service's ability to access local and network resources. The Windows operating systems rely on services to run various features. These services can be configured through the applications, the Services snap-in, or Task Manager, or by using Windows PowerShell. You can see more here: Using the LocalSystem Account as a Service Logon Account