05-04-2011 09:57 AM
My problem looks similar to that posted 11-01-2010 at 10:14 AM by Vagn
05-04-2011 09:58 AM
The difference in service name is the problem. Certain versions of the LV 2010 beta renamed this service to NISystemWebServer, while other services depend on niSvcLoc. My guess is at some point you had the LV 2010 beta installed on your system, and upgraded over it instead of uninstalling/reinstalling. We could verify this with a MAX Technical Support Report (Open MAX, go to File->Create Report..., and ensure Technical Support is selected).
Unfortunately the solution is to uninstall/reinstall all NI software, since many things have a dependency on the NISystemWebServer.
05-04-2011 10:22 AM
I did have 2010 beta installed but do not recall if I uninstalled it or upgraded. I will try uninstalling/reinstalling everything NI.
05-05-2011 07:54 AM
Uninstalling all NI software and reinstalling cured this problem, so it appears the difference in service name was the problem probably due to not uninstalling LV 2010 beta.
Thanks Justin.
05-20-2011 08:10 AM
Hi,
I have a very similar problem that is still not solved.
As SteveP I followed the steps in http://digital.ni.com/public.nsf/allkb/0819391CA91B3EB38625731D00024649 but I get "Error 1068: the dependency service or group failed to start." My NI System Web Server Properties are exactly as given by Justin_E on 05-04-201109:44 AM - also the Service name is niSvcLoc (and not NISystemWebServer) so that looks correct. Note: About a week ago I uninstalled all NI products using "MSI Blast" Tool and reinstalled them afterwards.
The reason why I checked the NI Device Loader and found that it is not running is the following: I have a PXI-6259 DAQ card and three PXI-4130 SMU cards in my PXI system. They are found in MAX and the Selftests in MAX. But when I add my PXI-8231 Ethernet card to the system the Selftest of the DAQ and SMU cards fail with Error -88705, saying that the device is not present or active.
05-23-2011 10:35 AM - edited 05-23-2011 10:36 AM
Did this setup work before you used MSI Blast? Are you using your ethernet controller to hook up to the network or are you attaching an external device? If it is an external device, is it possible there is some antivirus software that is causing the device loader to stop running? If you power down, remove the ethernet card, and power back up, do your other PXI modules pass self test in MAX again?
Jon
05-23-2011 11:52 AM
About two weeks ago the setup worked, but then MAX did not work correctly anymore and since nothing seemed to help I used MSI Blast and reinstalled my NI SW (as suggested by the local NI support). After that did not help I removed all PXI cards and plugged them in one after the other and found that the Ethernet card is the problem. The ethernet card will be used to connect an external device, but due to the current problem the LAN cable is not connected anywhere now and the problem still exists. Yes, the PXI modules pass self test after removal of the ethernet card.
Tobias
05-24-2011 01:59 PM
Tobias,
Can you confirm that the PXI-8231 is functioning correctly at all? If you just put the 8231 in your chassis, can you see it in device manager? Are you able to plug anything into it, or does the device loader stop working as soon as you put that card in?
Jon S
05-25-2011 02:16 AM
Yes the PXI-8231 card is working correctly:
- I tried it with two different PXI-8231 cards with the same result as described above.
- The Windows device manager shows one Network adapter when the PXI-8231 is not plugged in (which is the internal one of the controller) and two when the PXI-8231 card is added. The entry for the PXI-8231 is: "National Instruments GigE Vision Adapter #3". This does not look like a normal Ethernet card driver but I want to connect a camera to the PXI-8231 card and work with it with the NI Vision.
- I added the camera over a LAN cable to the PXI-8231 again today and saw a NI-IMAQdy Device in MAX and the camera is working correctly.
I then added my three SMU cards and they are visible in MAX and the Self test passes (which was not the case when I had the PXI-8231 plugged in without the camera added to it and which was the trigger why I checked the NI _Device Loader Service).
I then checked whether the NI _Device Loader Service is running as given in http://digital.ni.com/public.nsf/allkb/0819391CA91B3EB38625731D00024649 and saw that it is started!
So it looks like the NI _Device Loader Service cannot start when the PXI-8231 card is plugged in and wants to run with the GigE Vision Adapter driver, but no camera is connected to it.
Thanks for your help Jon, I'll check if my assumption above is correct in the coming days and will post again if the problem still exists.
Tobias
05-25-2011 05:19 PM
Thanks for the update. I'll pass this on to see if this is expected behavior. Please keep us updated on your progress.
Jon