ActiveX(18001) error mid test...sometimes. LabVIEW 2016

[AaronNagy]

I'm getting somewhat random ActiveX errors in my code it's overnight 18 hour runtime code so it's hard to be physically present when it errors...if it errors.

But we have another problem plaguing our system which is occasionally it can't connect to the license server properly and labview fails to startup this will last for ~1hour then start working again IT is trying to resolve. But the assumption has been that once LabVIEW is open we are fine is it possible that we are incorrect and this could cause this fault?

I'm running Teststand 2016 and calling LabVIEW 2016 and python code from it.

[Kyle97330]

It shouldn't be a license server issue if it's just 1 hour.

Per the VLM docs once you get a network license it should be good for up to 14 days if you get disconnected.  But if you want to totally eliminate that as a potential cause you could see if you can follow the guidelines to get a disconnected license (also on the linked page).  It would just mean that the license you use would be permanently in use from the server so it couldn't be shared in any way, but it could be that you're already the exclusive user on that machine and it wouldn't matter.