Internal Error (70) NI PSP Service Locator Could Not Be Started Properly

Updated Nov 2, 2023

Reported In

Software

  • DIAdem
  • DataFinder Server
  • FlexLogger

Driver

  • NI-DAQmx

Issue Details

  • 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?
  • 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.
 
  
  • 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.

Solution

To avoid these errors and unexpected behaviors the NI PSP Service Locator needs to be running successfully, you can review the status of this and other services in the Windows Services application. 
 

If the NI PSP Service Locator is not running try to start it manually by right-clicking the service and then Start. If after trying to start the service you get errors such as Error 1069: The service did not start due to logon failure, it is possible that the account being used to allow the service to run is invalid. You should check with your IT department to get valid login information.
 

As a workaround,  you can run the service locally. To do so, right-click the NI PSP Service Locator and select Properties. Select the Log On tab and choose to use the Local System Account. This option has some potential risks associated and may require Admin rights. Evaluate this workaround with your IT department before completing the steps, for more information see the additional information section.
 
image.png

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 about this and its risks here: Using the LocalSystem Account as a Service Logon Account

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.