You are making some incorrect assumptions. First, I did run a test
system,
but at a different ip. I expected a4d to time out in my test
system, as the
license file is tied to the production ip.
Actually, if it finds a deployment key file for another IP, it only
times out after 1 week. I suspect it couldn't find the key file and
thus was in trial mode, so it timed out after 8 hours.
Once I moved the system (yes, my
database does work correctly) into production, I noticed a4d timing
out
unexpectedly. This should not happen.
I suspect somehow another version of Active4D was being loaded.
Search the machine for all occurences of Active4D.4CX.
Replacing the old license file with
the new one seems to have solved the problem. I don't understand
why, as,
to my understanding of the license, it should never stop working as
long as
I am using the same version of a4d.
Is the license file with the plugin or in ~/Library/Preferences? It
used to be in Preferences, correct?
Regards,
Aparajita
Victory-Heart Productions
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
