DIAdem unable to pull TDM Server license

[Chris_P_SD]

Ok so after rebooting the DataFinder computer, I remoted in to several different computers with DIAdem access while also remoted into the license server (running VLM 3.1) to verify licensing behavior.  For the computers I tested, the license server now seems to appropriately relinquish instances of TDM Server 2017 connections.  I will continue to monitor VLM for this issue...

[Brad_Turpin]

Hi Chris,

I need to amend something I incorrectly asserted yesterday.  The TDM Server only checks out a "concurrent connection" from the VLM at the moment that a client requests a connection to it, and the TDM Server SHOULD relinquish that license back to the VLM the moment the client disconnects.  The bug in the NILM version that ships with the TDM Server 2017 causes concurrent connections not to be relinquished correctly under certain conditions.  Theoretically, updating the NILM and rebooting the server computer should be enough to fix the issue.  For any new customers reading this thread, please upgrade to TDM Server 2017 SP1 and get the NILM update along with a few upgrades to the TDM Server.

My current understanding is that the 8 checked out licenses you saw in the VLM was a result of the TDM Server not relinquishing concurrent connections properly when the clients disconnected from it.  The 3 connections showing in the TDM Server dialog were accurate, but because of failed relinquishment back to the VLM there were no further concurrent connection licenses the VLM could issue.

Sorry for all this hassle,

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Chris_P_SD]

Hi Brad, yep that's my understanding as well.  Currently, the DataFinder computer reports four connections and so does VLM 3.1, so I think we are back in business.   One other point of clarification - what is meant by a "Hot Fix"?  I interpreted that as meaning the software patch resolves an issue without requiring a reboot (or cooling down/ interrupting a process).  I'm not a computer scientist, so my understanding may be incorrect.  In our particular case, it appears that a reboot was necessary for the NILM 4.0.2 patch to take full effect.  I'm pretty sure there was no prompt from the installer to reboot.

Thank you,

Chris

[Brad_Turpin]

Hi Chris,

I'm very glad to hear you're back in business!  I'm afraid I'm not sure what "hotfix" should mean in general computer science parlance.  It certainly sounds reasonable to assume that it means you don't need a reboot, like "hot swapping" peripherals.  However, in this particular case, the DIAdem/DataFinder R&D team specifically mentioned to me that a reboot was required.

The installer was named by the VLM/NILM team, so we (DIAdem/DataFinder) don't have any control over that.

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Chris_P_SD]

All,

I'm not sure whether it's best to create a new thread for this, or append to the existing thread, but it appears the same issue is back.  TDM Server reports 6 users while VLM 3.1 reports 8:

I refreshed VLM3.1 AND the computer running TDM Server 2017, but no changes in the reported number of users for each.  I should note that only seven licenses of DIAdem are "in use" in VLM 3.1.

[StefanR]

Are you using only one DataFinder?

(In case you are using a second DataFinder, this one could also have open connections)

Are you also using Analysis Server?

(Analysis Server 2017 use temporary connection to a DataFinder when performing a routing-query, it is planned for the upcoming version 2018 to no longer use-up temporary DataFinder connections)

[Chris_P_SD]

Apologies - I thought I had already responded to this and just saw that I hadn't posted it.

I am only running one DataFinder called  "TEST_DATA".

We are not using Analysis Server.

[c-RADAE]

Hi Chris,

Let's go ahead and get this post on a new thread because this one already is marked as having a solution. This should get more visibility on this issue. 

Regards,

Conrad

Applications Engineer

National Instruments

[Chris_P_SD]

Hi Conrad,

I'm afraid I don't know the best way to copy an existing post to a new thread.  I tried marking the post as new, but that didn't seem to create a new thread.  It seems the best way to do this would be to migrate the last few posts of the existing thread to a new thread, then leave a link at the bottom of the first thread that points to the new thread.  Not sure how to do that...

Thanks,

Chris

[c-RADAE]

Hi Chris,

I would just create a brand new post under DIAdem that has a link to this post and a short description of the current state. This newer post should get more traffic, but also allow everyone to see the issue details by looking at this post. 

Regards,

Conrad

Applications Engineer

National Instruments