DataPlugin: DIAdem reverts to old DataPlugin after closing and reopening

[Chris_P_SD]

I have a Windows 7 x64 computer running DIAdem 2017 SP1 and for some reason it always loses the DataPlugin when I restart DIAdem.  I've tried importing the latest plugin multiple times, saved the DIAdem settings, and even deleted the plugin from the user directory.  I'm not sure where DIAdem is pulling the old plugin from, but somehow I can't get it to hold onto the new plugin.  Has anyone had this problem?

Thanks in advance.

[Sil.VI]

Hi Chris, 

I will be happy to help you. Is this happening only with a specific DataPlugin or any newly added plugin? Which is the plugin that you are trying to use specifically?

[Chris_P_SD]

Ok thanks!  It's just one DataPlugin.  It seems to be happening on two computers now; one computer running DIAdem 2017 SP1 and the other running DIAdem 2018.  After closing and reopening DIAdem, the DataPlugin in question changes type from VBS to VBCrypt.  It also reverts back to a version from 2016.  The plugin in question is called Achates_Power_XLSM.VBS (attached).

[Brad_Turpin]

Hi Chris,

Can you check if there is a start script configured for those 2 computers?  Go to the menu "Settings >> DIAdem Settings..." and select the "General" category at the top left of the "DIAdem Settings" dialog.  Is there anything in the "Start script" field?

The short answer is that I have not heard of this ever happening organically in DIAdem, which is why I suspect a custom script is running automatically every time DIAdem starts up.  If so, we can find that script and comment out the line to update the DataPlugin programmatically.

In DIAdem 2017 and prior versions, running a *.uri file registers the VBScript DataPlugin unencrypted, while in DIAdem 2018 and later, running a *.uri file always registers the VBScript DataPlugin encrypted.  You can import a *.uri DataPlugin in DIAdem 2018 using the DataPlugins dialog to register it unencrypted still.  I think this explains the VBS and VBCrypt difference you see between your 2017 and 2018 DIAdem versions.

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Chris_P_SD]

Hi Brad,

I don't see a start script.  Furthermore, this installation of DIAdem 2018 is only a few days old and hasn't really been configured.  It's almost like it's pulling in some sort of roaming user data, but not sure how...

Double clicking the .uri file applies the latest DataPlugin and it works great until DIAdem is exited and restarted...

[Chris_P_SD · Accepted solution]

There is a DataPlugin configured in TDM Server Manager with the same export date as the DataPlugin that keeps emerging in the new installations of DIAdem.  I removed the DataPlugin in the TDM Server and it seems to have cured the reappearance of the old plugin in at least one DIAdem.  Will keep an eye on it for a couple of days to verify that this was indeed the problem.

[usac]

That's a good hint. DataFinder connections offer the option to synchronize DataPlugins when connected, to ensure you load the data with exactly the same DataPlugin they were indexed with.

You can specify this during the export of the client configuration in the TDM Server.

You can also disable it in DIAdem for a specific DataFinder connection. Therefore go to Settings -> DataFinder Server... and edit the DataFinder you connect to. Unless you did not use the option "force synchronization" in the exported client configuration, you can disable synchronization there.