Active X AlertBrowser Slow to initiate

[GretchenSkellyZimmer]

Active X component is very slow to launch; in below image, the part that is circled takes about 7 seconds to execute.

After the Action Log becomes active, it works well.  Just takes too long to launch.  Any ideas?

Labview 2015 Pro, DSC Module, Windows Server 2012 OS

[Andr3s_Br3n3s]

Hi !

Did you try in another developer machine? Same behavior?

Let me check.

[GretchenSkellyZimmer]

At your suggestion, I tried it on another server.  The VI launches immediately!  Any clues as to why it comes up slowly on the this new server?  It is so slow that the title bar changes to the familiar "(Not Responding)".

Gretchen

[Andr3s_Br3n3s]

Main differences between both servers?  Can you go to task manager and see what are both running?

[GretchenSkellyZimmer]

Both look the same:        servers are dedicated to this one Labview project

[SamuRei]

Just to be clear, are both servers that we are discussing on the same or different machines?

Are these both being run from the same user account (or at least as an administrator)?

Assuming the VIs are the same PC, are they running from the same drive?

Best

[GretchenSkellyZimmer]

Hi, I appreciate your time in helping me out.

I have two distinct server machines!  One is the existing server/Labview system, put into service in 2015.

The 2nd one is a brand new Windows Server  2012R2 which is the development server.  I moved a copy of the Labview application from the existing to the new, and then started the Phase II part of the project.  The VIs that use the ActiveX objects are the same as on the existing server/system currently in use.  On the development system, the 'Action Logs' (the Active X objects) work once the VI completely launches.  But it just takes so long to come up.

This week, I have tried:

• building the application into an executable (which is how we use it anyway), but I get the same behavior.
• I have checked a Windows related config file, and a National Instruments config file for something like a 'ActiveX Enabled' setting.  But found none.

[GretchenSkellyZimmer]

realized I didn't answer all of your questions:

Yes, running from the same account on both servers, and yes I have admin rights.

All VIs are located on drive C

Gretchen

[GretchenSkellyZimmer]

One more additional bit of info:  I am using the add-on DSC Module, Alarms & Events display feature

[GretchenSkellyZimmer · Accepted solution]

I figured out what my problem was!  I am working with a DSC Alarm & Display ActiveX Object, and there is a 'process' associated with it.  When I right-clicked on the object and chose Alarm&EventDisplay -> ChoseProcess, it showed me that the process from the other server was still associated with the object.  So, the delay in activation was due to the fact that it was connecting to the other server over the network.