We have GOT to solve this. The license file has timed out AGAIN on a
production server. We do not know this happens until a user tells us.
We are now writing an On Server Start that checks at the start using
the plugin commands. But I have to ask, why is this necessary? Even
if it DOES find that it is in Demo mode, what then? It certainly
SHOULDN'T be in demo mode - we have a license and it works _most_ of
the time.
I agree, it shouldn't be in demo mode.
Is it possible this has to do with 2004 and starting from a Mac
StartupItem as registered from 4D Server? Maybe it does not have some
permissions when started as a service? Now that I think about it,
that must be part of the issue. When it times out, we restart the 4D
Server, it seems to register correctly - we do not restart it from the
service (i.e. SystemStarter).
Are you saying it _always_ ends up in demo mode when started as a
StartupItem and _always_ ends up in deployment mode when restarted
normally? If so, that would definitely seem to be the trigger for
this problem. If not, something else is going on.
What other plugins do you use?
I would also like to request the ability (if it is not there already)
to change the demo-license-timeout result screen.
If the license times out, the call to A4D Execute 4D Request returns
-2 as the status (page 67 of the manual).
Regards,
Aparajita
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/
