NI Service Locator Not Running

[ttt1603]

Hello

This error "NI Service Locator Not Running" was found in NI MAX as well as in Help>Find Examples... and try to open any example.

After this LabVIEW was uninstalled & a fresh installation was done but still this problem was not solved.

Also NI Application Web Server was not found in services.

I attached the snapshot taken from MAX.

Also after installing the LabVIEW again, it was seen that RT PXI was unable to connect. The error is shown in Capture2 attached here.

Please suggest the appropriate solution for the problems mentioned above.

Thank you.

[Bob_Schor]

What version of LabVIEW are you running?  You said you "uninstalled" LabVIEW and re-installed it -- how did you do this?  [I do hope you were not running LabVIEW 2011 ...].  Also, what version of Windows?  [When you answer the Version question, specify if 32-bit or 64-bit, noting that the "safest" installation is 32-bit LabVIEW on 64-bit Windows 7, 8.1, or 10].

I have had this happen to me on several occasions (fortunately, none recently).  This typically happened on a PC with at least two earlier versions of LabVIEW installed.  In the Best Possible Scenario, this required going into Control Panel, Programs and Software, NI Software, and "Remove All".  Reboot, verify no NI Services are shown, install one step at a time (rebooting in between) checking NI Services at each step, and installing Device Drivers last.

When this didn't work, I reformatted the hard drives, reinstalled Windows, reinstalled my other programs, then reinstalled LabVIEW.  I've had to do this at least twice in ten years ...

Bob Schor

[StevenD]

Can you start the service manually? In Windows 10 and I believe through Windows 7 you can open the Windows services by typing "services.msc" into the run prompt. Scroll down to "NI Service Locator" and see if you can manually start it. You can also set it to try to run several times on boot if the first run fails in the properties window (shown below).

[ttt1603]

 Thank you Bob Schor for your responses.

Here are the answers to your questions-

LabVIEW version 2014.

Reinstalled the same, LabVIEW 2014.

For uninstall, as you had mentioned in second para of your reply, (Going into Control Panel.., NI software & Remove All). The same way. After uninstall, Registry was cleaned, temp files were cleaned & removed manually as well (The National Instruments Folder from Program Files/(x86) & from ProgramData (Hidden Folder) also).

This was done on Windows 7, 64-bit OS for LabVIEW 32-bit.

Reinstall was also done on same system without formatting the OS installing LabVIEW 2014, 32-bit.

And during installation normally all required toolkits & modules were selected and installed together. And at the end NI Device Drivers were installed. I have faced this for the 1st time, since 5 years of my working with LabVIEW (32-bit) in Windows 7 (64-bit) system. Have used LabVIEW 2011 to LabVIEW 2014 versions, install-uninstall-reinstall was done in the similar way mentioned above. But never faced this issue.

Hope you could suggest any useful steps for the solution, otherwise Formatting the Windows & reinstalling everything again will be the last priority.

Thank you.

[edjones93]

Hi,

The method Steven suggested are the best next steps, also setting the service to Automatic Delayed start will allow it to start later in the startup process of your machine, during this period services can timeout and never get started.

Additionally it would be helpful to provide us a System Information file as described in the below article to confirm the services installed and their default settings:

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Obtain...

Thanks,

Ed

[Bob_Schor]

I assume you are an Administrator on your machine, right?  You should not have to choose "Run as Administrator", but you should be logged on with an Administrator account.

For what it is worth, I just downloaded LabVIEW 2017 and it "sneered" at me about the NI Discovery Service not installing.  My plan is to reboot, and re-run the installation.  I'll right-click the installer and choose "Run as Admin", and hope it goes better.

If you do try a re-install of LabVIEW 2014, do it one step at a time with a reboot between steps.  I've not tried the "manual start/stop" of Services (for NI Services), but it couldn't hurt to try this.  For the record, I've managed LabVIEW 2014 installations without serious trouble -- I generally install LabVIEW (32-bit), LabVIEW RT, LabVIEW Vision, LabVIEW Report Generation Toolkit, NI-DAQmx (I can't remember when this was separate and when part of Drivers), and Drivers.

Bob Schor

[Bob_Schor]

Oh, goody -- re-running the 2017 Installation (as Admin) completed in about 1 minute (the first time, it must have done all the work, the only "glitch" was starting the Service).

BS

[edjones93]

Hi Bob,

Did you happen to restart the computer between installations? I understand LabVIEW 2017 requires the newer version of the .NET framework.

Just as an addition to the service issue, services can depend on one another, this is indeed the case for Device Loader. I have included the full list I have thus far found to require configuring to restart after every failure and delayed start to get reliable performance in some more complex Windows systems and group policies:

1. NI mDNS Responder Service

2. NI Network Discovery

3. NI PSP Service Locator

4. NI Service Locator

5. NI Device loader

6. NI LXI Discovery Service

7. NI Configuration Manager

I would configure all these to restart after failure and start automatically but delayed.

Best regards,

Ed

[Bob_Schor]

---

@edjones93 wrote:

Hi Bob,

Did you happen to restart the computer between installations? I understand LabVIEW 2017 requires the newer version of the .NET framework.

---

I didn't do a specific reboot -- I'm running the latest version of Windows 10, which includes the latest version of .NET.  As I noted, the second run of the LabVIEW 17 Setup utility (run "As Administrator") basically finished the installation (after the initial questions) in seconds (less than 15).  It probably only needed to start up the necessary Services.  

Here are my current NI Services:

• App Web Server
• Configuration Manager
• Device Loader
• LXI Discovery
• PXI Resource Manager
• DAQmx Remote Config
• RIO Server

Actually, I'm surprised that so few services are running.  In fact, when I check another Win 10 system (I think its the second release, whereas the laptop as the third), there are 18 NI Services listed.  Of course, this other system has multiple LabVIEW versions (the Laptop only has 2016 and 2017) on it, and has been connected to various pieces of hardware (including a PXI LabVIEW RT system).

For what it's worth, the 17-18 services is also what I see on my Win 7 multiple-LabVIEW PC.  Also, when I just installed LabVIEW 2017, I did not (re-)install Device Drivers -- I'm waiting for the full Kit to arrive ...

Bob Schor

[JÞB]

 There are patches to device drivers 17 that might fix the issue