I can't run the a4d.debug.dump license info when active 4D has timed out. The Active4D preferences from within 4D show the license file is deployment, and has time counting down from 168 hours?
We restarted the server and ran the same tests. The a4d.debug.dump license info shwos the same info as the A4D plugin from within 4D with one exception. dump license info shows Time Remaining: unlimited. Now the server is no longer timing out after the 8 hours. But it DID time out before, and the A4D plugin license info (from 4D) showed the license was deployment and active for the correct IP address - during the timed out server session. So how can we verify that the server is NOT running in demo mode when we start up the server? We can use the A4D plugin commands to get the license, but that has proven unreliable since a timed out server showed the A4D plugin license as active. Any input Aparajita? On 10/5/06, Steve Alex <[EMAIL PROTECTED]> wrote:
write a short script <% a4d.debug.dump license info %> See if it displays same info from the library. Should tell you where it finds the key and all.
Thanks, Michael Check _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
