Re : labview runtime - slow pc start up

[Maqsood]

I have LabView 2012 installed and i am using this from a third party developer to run another .exe program. 
We use the program to predict scaling tendency of water....generates graphs and dosing calculations etc for our products.
The program does not call on any  .net framework
The 3rd party program is stand alone and does not call on any other.
The problem i have is that i am getting a delayed pc start up of ~20 mins, howevwer, i can bypass this if i switch OFF the wifi key before the windows logo starts. If i switch off the wifi the pc starts up within a few minutes.

If i uninstall NI runtime the problem goes away and computer starts up fine. Which is why i think it is Labview related? Is Labview trying to make some kind of connection at pc start up ?

[ramses64]

Hi,

did you tried to read the Event logs of windows (in W7, system and security => show event logs).
You may see timeout of NI program which tries to connect to internet...
I hope this will help you.

Best Regards,

[Eden_S]

Hi Masqood,

Which version of LabVIEW RTE are you using? Is it x64 or x32? What OS are you running?

V-F gives the best first step though, please check the event logs and get back.

Best regards,

[Maqsood]

Hi,

i have checked the event log and can not see any time out for NI etc.

I am using Labview RTE x32

I have noticed that when i use a ethernet cable connection everything is fine...my pc starts up OK. But when i use wifi i get the delay?

regards

Max

[Eden_S]

Hi Max,

That is very strange, I'd like to find out exactly what processes are slowing down your start-up so much, for this I think we'll need to go back to the Windows Event Viewer. Could you please try the following steps and let me know what you find?

- Open Event Viewer (Control Panel -> Admin. Tools -> Event Viewier)

- Expand Applications and Services Logs -> Microsoft -> Windows -> Diagnostics / Performance -> Operational.

- Here you should see a log of recorded Windows events. Please sort by "Task Category" to look at "Boot Performance Monitoring".

- All of the events are dated, so look for ones that occurred only when your start-up was slow.

- You should be looking for errors/criticals, but it might be worth checking some warnings too.

- When you select an event, you will see some information below. Look for events with a long 'total time' - as you said start up was taking anywhere up to 20 mins (!!) you should see at least some events with VERY long durations.

Please could you record any that you feel seem unreasonably long (generally, any one event that takes longer than around 10 seconds should be worth noting).

Please let me know if you find anything abnormal.

Best regards,

[Maqsood]

Thanks Eden for the detailed step guide.

I found many critical errors in the Boot Perf Monitoring.

One was for yesterday: (copied below):

Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational
Source:        Microsoft-Windows-Diagnostics-Performance
Date:          06/11/2012 11:34:11
Event ID:      100
Task Category: Boot Performance Monitoring
Level:         Critical
Keywords:      Event Log
User:          LOCAL SERVICE
Windows has started up:
     Boot Duration  : 168532ms
     IsDegradation  : false
     Incident Time (UTC) : ‎2012‎-‎11‎-‎06T11:29:44.624800200Z

[Eden_S]

Hi Max,

Thanks for the response. Was this when you had the slow boot? Because the log there indicates a boot time of 160s, which isn't that long. 

If you look at the event ID, this is listed as 100 which is a boot log. This doesn't tell us much about the services that could be slowing down the boot, just general information. Are there any that stand out that have ID 101? These are executables that load on start-up. Failing that, what about ID 103 or 106?

Thanks,

[Maqsood]

All the ID100 are either "critical" or "errors"

ID101 are "warning" or "errors"....the last one was 3/10/2012

Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational

Source:        Microsoft-Windows-Diagnostics-Performance

Date:          03/10/2012 13:42:30

Event ID:      101

Task Category: Boot Performance Monitoring

Level:         Error

Keywords:      Event Log

User:          LOCAL SERVICE

Computer:      genesys-nb04.Genesys.local

Description:

This application took longer than usual to start up, resulting in a performance degradation in the system startup process:

     File Name                       :               SavService.exe

     Friendly Name                             :               Performs virus scanning and disinfection functions

     Version                           :               10.0.6.6995

     Total Time                      :               33068ms

     Degradation Time       :               27268ms

     Incident Time (UTC)   :               ‎2012‎-‎10‎-‎03T12:38:18.624800200Z

some other with ID101 are:

outlook.exe

iexplorer.exe

svchost.exe

msiexec.exe

savadminservice.exe

searchprotocolhost.exe

[Maqsood]

forgot about the other IDs...

All ID103 are warnings

There is one ID106:

Log Name:      Microsoft-Windows-Diagnostics-Performance/Operational

Source:        Microsoft-Windows-Diagnostics-Performance

Date:          03/10/2012 15:47:55

Event ID:      106

Task Category: Boot Performance Monitoring

Level:         Error

Keywords:      Event Log

User:          LOCAL SERVICE

Computer:      genesys-nb04.Genesys.local

Description:

Background optimizations (prefetching) took longer to complete, resulting in a performance degradation in the system start up process:

     Name                               :               BackgroundPrefetchTime

     Total Time                      :               65131ms

     Degradation Time       :               39915ms

     Incident Time (UTC)   :               ‎2012‎-‎10‎-‎03T14:45:02.624800200Z

[Eden_S]

Hi Max,

Thanks for the info. 

Checking the incident time, most of these events came from October, was the slow start-up issue occurring when these events did? It may be that there is nothing out of the ordinary for the times where the computer took so long, in which case we will look at other ways to troubleshoot the issue.

Thanks,