Diadem 11 crashed when using AOP5 plugin with no specific error

[shailesh.saraph]

We have a ASAM-ODS database and are running a Avalon v4.2e server. DIAdem data TDM file is uploaded using openMDM client.

We have installed AOP5 plugin on 2 systems running DIAdem 11 to access the data directly from the ASAM-ODS database. On one machine it is working fine.

On the second machine with the same parameters, when we try to connect, DIAdem hangs and then crashes with no specific error in the log file. DIAdem is not able to refresh the Navigator window and show the data stored in the ASAM-ODS server. The relevant errors are attached and also the log file of the plugin.

How do we debug and resolve the issue? Any pointers would be welcome. We are using aop5dataplugin2_0_1.exe downloaded from the NI site.

Regards,

Shailesh

[Brad_Turpin]

Hi Shailesh,

Is it possible that the computer this worked on has had a newer version of DIAdem or LabVIEW or DataFinder on it?  All three of those NI software packages share a layer called USI, which is what the DataPlugins "plug into".  The USI layer only upgrades, so even if you installed a DIAdem 2012 evaluation version and then uninstalled it, you would keep the USI version from DIAdem 2012, and your DIAdem 11.0 would use that newer USI version.  It is possible that the latest AOP5 DataPlugin is not compatible with 11.0, which was released nearly 5 years ago.  I can look into that and get back to you.

Alternatively, DIAdem 11.0 may be struggling to work with a USI version from LabVIEW 2012 or DIAdem 2012.  We do regression testing every release with multiple older DIAdem versions, but at some point the newer features don't work with the older software.

Brad

[AndreasK]

It looks like the retrieval of the model fails.

The logfile shows that you switched Model retrieval to ApplicationStructure.

Please set this to ApplicationStructureValue.

You also switched the Rerquest mode away from Extended query. Please set this back.

MDM should work with default settings.

please only change the logging setting but let the other values by default.

We never encountered problems with an MDM system and the default values of the AOP5 plugin.

Please retry with those settings.