04-08-2015 09:58 AM
Good day,
I tried to install the NI Device USB-6525 when I noticed some problems with my Labview installation.
The first is that when I open NI MAX the program shows the message "NI Service Locator not running"
And the NI USB-6525 device is shown as available but I can't use or configure it.
Then I tried to solve this problem via updating Labview but the NI-Update Service says that there is a communication problem.
I also tried:
- restart the PC
- restarting NI Service Locator, NI System Web Server
- reinstall device driver
- testing another USB port
- repairing Labview, MAX, Update Service
The NI USB-6525 device functions properly on another PC with Labview 2014, MAX v14.0
System:
Win 7 32-bit
Labview 2014
MAX v14.5
04-08-2015 11:09 AM
If I understand your problem, perhaps this would solve it. A shot in the dark.
LabVIEW is always installed first then the driver set, which has the MAX software in it.
IF LabVIEW is installed but not the latest driver set immediately afterwards then things similar to your problem could happeneven if the drivers were already on the machine.
04-08-2015 11:13 AM
So, you mean to remove MAX and install it again or remove Labview completely and install everything again?
04-08-2015 11:24 AM
For reasons that I fail to understand, LabVIEW has become "fragile", lately, with installations to add features (or update Versions) sometimes causing essential NI Services (the NI Service Locator is a good example) to stop running. I usually encounter this 2-3 times a year, sometimes more often.
Something that often seems to work is to go into Windows, Control Panel, Programs, find the NI entry, and choose "Repair". Be sure to have all of your installation disks on hand, as it will ask for them. You also need to know on which disk what Module or Toolkit is located, which can be something of a pain now that NI does not seem to include a "Table of Contents" page in the Kit. However, if you open the DVD and look in the Distributions folder, you can often "guess" by looking at the Folder names. For example, LV_MASM is the Multi-Core Analysis and Sparse Matrix Toolkit (boy, I really picked an "intuitive" one, didn't I). And in case you can't figure it out, try the DVDs one at a time -- if you have the wrong one, NI will tell you ...
If you have multiple "editions" of LabVIEW (e.g. 2010, 2011, 2012) installed, you will probably need their DVDs as well.
Before I learned this trick, the only thing that (reliably) worked was a complete Uninstall/Reinstall cycle. However, since it was an installation that actually caused the problem, one other thing that I did was to do a Reboot between every Toolkit/Module install. At least the Repair pathway is faster and easier ...
Bob Schor
04-08-2015 11:37 AM
I already tried repairing Labview and MAX but that doesn't solve the problem.
I also have only installed Labview 2014, no older versions.
04-08-2015 11:45 AM
I would not do that just yet since you stated that you installed driver for your USB card (I presume afterwards) and then
this problem appears. Supposedly installing a driver has no effect whatsoever on the labVIEW installation or version.
ALso is your machine using security software? NI Update service triggered IT to come and see me about my machine once.
I turned it off and update manually.
Perhaps someone alse has better advice than mine,
(I currently do not use or have version 2014 anyway.) although in theory if you did do a clean wipe of everything and then installed
everything it should work.
But what Bob Schor has stated (LabVIEW seems to be getting more fragile lately) seems to be a fair opinion based on experience watching the forum questions that come up every now and then.
Someone else here will know more..
04-08-2015 03:28 PM
Here are some of my thought/suggestions:
Sorry to hear about the trouble you're experiencing. Hope this helps!
04-08-2015 04:27 PM
@leswile wrote:
I already tried repairing Labview and MAX but that doesn't solve the problem.
I also have only installed Labview 2014, no older versions.
I don't know what you mean by "repair LabVIEW and MAX". Here's explicitly what I mean --
That is the sequence of steps that (usually) fixed bad installations or "dying services" for me.
BS
10-06-2016 10:49 PM
Sorry, if I have LabVIEW 2015 what should I do?,because i tried to fix with your tips, but it didn´t fix the problem
10-08-2016 03:01 PM
@PipoPinto wrote:Sorry, if I have LabVIEW 2015 what should I do?,because i tried to fix with your tips, but it didn´t fix the problem
You are replying to a question asked (and probably answered) a year and a half ago. If you have a new question, post a New Message (specifically, do not Reply to this message).
In your New Message, give it a meaningful title. Then describe the problem. Tell us as much as you can about your installation (PC/Mac, which OS, which version of LabVIEW and how many bits, what hardware, has it worked previously or is this a new installation, etc.). We need to know your situation, which (by your own admission) is not the same as that of the Original Poster.
Bob Schor