07-11-2011 05:09 PM
yezaiha,
Check out the System Event error log and let me know if anything stands out as important and post that here.
Kind Regards,
Allie F
09-03-2011 09:00 AM
Justin,
Can you repost your fixed version of the NI mDNS Responder service? I apprear to be running into the same problems as the other folks on this thread.
Thanks!
09-06-2011 09:39 AM
Hi 2and4, please try installing System Configuration 5.0 first, which contains the fixes made to mDNSResponder for this issue:
http://joule.ni.com/nidu/cds/view/p/id/2613/lang/en
09-09-2011 12:29 AM
I installed the new NI System Configuration. It didn't solve the mDNSResponder Service problem (i.e. I couldn't start the service).
My problems started when I tried to build my first Web Service and found out that I couldn't start the NI Application Web Server. I've tried several things to solve this including restoring MAX to a default state (what I would do if MAX's database gets corrupted). No luck so far.
In case it helps here are a list of services I'm unable to start:
LXI Discovery Service
mDNS Responder Service
RIO Server (not using RIO)
NI Application Web Server (don't think I need this one because I'm using Win7 Ultimate 64-bit)
NI Application Web Server (64-bit)
NI Device Loader
NI Network Discovery
NI PXI Resource Manager Service
NI TSU Clock Service
NILM License Manager
09-09-2011 09:00 AM
Did you by any chance ever install any NI beta software on this machine. I have seen a few instances where some one installed a beta version of LabVIEW onto a system and then tried to update to the released software. Unfortunately, NI doesn't support upgrades over betas, so it can leave a system in a bad state where the NI services can't start.
09-09-2011 09:04 AM
Also, do you see a service called "NI System Web Server"? If you double click on it, it's service name should be "niSvcLoc". All of the services you listed below depend on it, so if it isn't installed correctly or running nothing else will work.
If it is missing, not running, or has a different name please let us know.
09-13-2011 10:21 AM
I'm having a similar problem with mDNS Responder, although I have a different error message:
"The NI Device Loader service depends on the National Instruments mDNS Responder Service service which failed to start because of the following error:
After starting, the service hung in a start-pending state."
I have checked the status of NI System Web Server. It has started.
LXI Discovery Service, RIO Server and NI Network Discovery are not running as expected in addition to NI Device Loader.
MAX 5.0.0f1
Mike
09-13-2011 11:04 AM
I had LV2009Beta on here and/or LV2010Beta. I definitely did NOT have LV2011Beta.
Nonetheless everything seemed to be fine until around the time I upgraded LV2010 to SP1. Before then I could connect DAQmx devices and they would appear within MAX. Not anymore. I'll make sure to uninstall any Beta installations before installing the actual versions from now on.
09-13-2011 11:10 AM
I do have the "NI System Web Server" service. It seems to be running fine although when I double-click it I don't see "niSvcLoc" mentioned anywhere. Also, according to the Dependencies tab in the Properties dialog box for this service, it does not depend on any other services, AND no other services depend on it.
09-13-2011 11:24 AM
Hi Mike,
Can you send over the Application and System Event Viewer logs from your machine? I'd like to see if there are any messages posted there from our service.
Please attach those .evt/.evtx files here, or upload them to ftp://ftp.ni.com/incoming and let me know what the filenames are.