DLL: "This limited time copy has expired"
Posted: Mon Mar 26, 2018 1:09 pm
Hi all,
I am trying to use the Vensim DLL to connect to 32bit Python (in Anaconda). I installed Vensim DSS Academic 32bit from an .exe downloaded just a few days ago directly from Ventana. I installed as administrator after uninstalling the previous version and running a cleaner program (BleachBit) and manually deleting the dll files in the /System32 and /SysWOW64 folders. But when I try to access my .vpm model through the DLL to run it, I get a message "This limited time copy has expired". My registration code is fresh and valid until September 2018. I have tried multiple times to reinstall Vensim both with and without admin permissions, and I have also tried various orders of opening Anaconda, Vensim, etc. I am a bit stumped to be honest. I also tried applying the recommendations I found through a forum search but they did not appear relevant (activating "academic use" on install) or did not have any effect (running Vensim next to the DLL as administrator).
Does anyone have recommendations on how to resolve this issue?
I am trying to use the Vensim DLL to connect to 32bit Python (in Anaconda). I installed Vensim DSS Academic 32bit from an .exe downloaded just a few days ago directly from Ventana. I installed as administrator after uninstalling the previous version and running a cleaner program (BleachBit) and manually deleting the dll files in the /System32 and /SysWOW64 folders. But when I try to access my .vpm model through the DLL to run it, I get a message "This limited time copy has expired". My registration code is fresh and valid until September 2018. I have tried multiple times to reinstall Vensim both with and without admin permissions, and I have also tried various orders of opening Anaconda, Vensim, etc. I am a bit stumped to be honest. I also tried applying the recommendations I found through a forum search but they did not appear relevant (activating "academic use" on install) or did not have any effect (running Vensim next to the DLL as administrator).
Does anyone have recommendations on how to resolve this issue?