When I open the Agilent IO Libraries suite (16.3)
"The Agilent IO control could not start because there was a problem communicating with the agilent io libraries service.
Status Summary:
0= Agilent IO LibrariesSerivice status
0= NkoSever status
0= Nkosever working
Restary your computer and if the problem persists,
contact Agilent Technologies."
And ask me to reboot my bench PC and Labtop. Sooooooo I tried re-boot my PC, but this also doesn't work.
Anybody have an idea what's wrong, and how to fix it?
Thx.
Edited by: yo_0321 on May 1, 2013 10:12 AM
"The Agilent IO control could not start because there was a problem communicating with the agilent io libraries service.
Status Summary:
0= Agilent IO LibrariesSerivice status
0= NkoSever status
0= Nkosever working
Restary your computer and if the problem persists,
contact Agilent Technologies."
And ask me to reboot my bench PC and Labtop. Sooooooo I tried re-boot my PC, but this also doesn't work.
Anybody have an idea what's wrong, and how to fix it?
Thx.
Edited by: yo_0321 on May 1, 2013 10:12 AM
Attachments
The message you received indicates that our main service "Agilent IO Libraries Service" did not start. This spawns the NKOServer process used by Agilent Connection Expert. Often this service can get delayed from starting by another process. Common examples include Windows Updates, Anti-Virus products, or other CPU-intensive bootup processes.
Can you run "services.msc" and see if you can manually start/restart the "Agilent IO Libraries Service"?
To further diagnose the issue, I will need logs. I have attached the log utility in this thread. I have sent you a personal message with instructions to grab these logs so we can take care of this issue offline.
Connectivity
Attachments
if so, which one and what is the sw rev?
I've already used the "service.msc" change the "Agilent IO Libraries Service" as start and change it as auto, but which fixed this problem only at one time. After I reboot my PC, It also fails to start with the same problem. Is it caused by my annoying Anti-Virus products? How could I repair it?
Thx again☺
As suspected the service is getting delayed from starting considering a force start starts the service. If it takes longer than 3 minutes then our icon application will throw that error automatically, or if you open Agilent Connection Expert. The log grabber utility will help me diagnose the problem.
I would recommend that you disable/uninstall your antivirus products. Then check for any other CPU intensive bootup applications. You could also try selective startup booting with msconfig.exe. The log grabber utility will help me narrow down the problem.
Connectivity
Attachments
In the logs I saw that the service successfully started on 4/13/2013 but did not after 5/1/2013. Have you installed any applications between these dates?
I have a few suggestions:
1. The logs did not indicate any application crash. It indicated that the service did not start at all. I suspect the service is getting delayed/blocked from starting. I suspect two applications that have caused customer problems like this in the past. They are 360.cn(virus)and VAIO Care Performance package(CPU intensive). It may be neccessary to use msconfig.exe to selectively eliminate startup processes that could be interferring.
2. I would imagine you could force start the service by bringing up cmd.exe and running the command:
*net start AgilentIOLibrariesService*
3. The logs indicated that you are running version 16.2. I would first upgrade to IO Library Suite 16.3 update 1 from www.agilent.com/find/iosuite that introduced a few bug fixes for Win 7 machines.
Connectivity
Edited by: connectivity on May 6, 2013 9:41 AM