Issue Registering Renewed Maintenance License

We have created a special build which should show us what is going on.

The build creates the detailed log and it does not reset the license back to trial in case of license check failure.

Please check your email

Hi.

AETLE x64 v6.3.7.9 Windows Server 2012 R2

We had a number of issues occur over the past 12 hours centered around AETLE. During the night and early morning the Production Server ran low on resources and ended up stalling. After a reboot and some forensics we found that AETLE had an error related to memory and then the crash and then the AETL license reverted back to Trial. Which in itself has been problematic for us in the past.

After starting and stopping services as Admin, reapplying the license I gave up and reverted the server back to a special release you prepared or us called 113. I reapplied the license. but it does indicate it is expiring today.

The problem is that we made use of some of the new features in v6.3.7.9 The special release 113 reports that it is v6.3.7.8 but it may in fact be v6.3.7.7

We have many log files and screenshots but some of the details in the logs may be sensitive and not appropriate for the an open forum ticket.

As it stands at the moment, ETL is being processed but i suspect if we have another restart we will be confronted with the same issue. The bigger concern is what was the root cause for the crash. I suspect a memory leak. We can see that at about 10PM last night our time AETLCL had a resource issue and then after that there were numerous "Application Hang" events recorded all from AETL and they were 'PopUps' which possibly means that they were trying to show a dialog box. This is an unattended server and to jobs are being run as a service.

The only other contributing factor was that during the day prior to the crash I had enabled the ETL FTP Monitor which we have never used and we wanted to test it with a new trading partner who we need to exchange data with.

I suspect that this may have triggered the license flicking back to Trial as well as perhaps contributing to the a memory leak.

The issue is now also, that our AETLP desktop apps are v6.3.7.9 but the server is running on an earlier release and there are some features from v6.3.7.9 that may be in play when the server attempts to run the packages and Transformations.

Regards
Bruce

1 Execution agent and aetlcl used to be the same exe.
and this combination had a lot of problems
We do use a lot of third-party software some of it may leak memory.
So the decision was made to separate them
The agent starts the aetlcl , and it executes the package.
Once the execution is completed all memory goes back to the operating system.

2 It is possible to bring server to the halt by running too many aerlcl.exe

a) Create a package which never completes (because it is waiting for some dialogue box or something else)
b) Run it every minute.
c ) In 3 hours you will see 180 aetlcl.exe running in the process monitor.
d) It will consume all server resources and bring it to halt

Hi Bruce

I think we have reproduced the problem.
It does happen when you use both 32-bit version and 64-bit version of our software on the same server.
So if you register the software using 32-bit version and later run 64-bit version it will flip back to the trial license.

Hi Mike. Thanks for that.

In our case, I'm confident we only have x64 installed on server and so it was what was used for install and subsequent registration. I our case I may have also tracked something down. The other system dev/ops/admin (we are a small company), from what I understand may go onto the server and start the Desktop App. We communicate before hand to ensure there are no duplicate sessions. We use RDP to get to the server, and use the same service account created for it top get the desktop.

BUT..... In some instances I think they have thought that AETLE Designer had not started and then started it again, or found it in Task Manager, Killed it and then started it again. My guess is that they have thought it was locked up or non-responsive and killed the process when it has probably reset the software back to Trial Mode and before it has had a chance to get the correct expiry date. Thus, the next time the Agents check, they see it as a Trial License. To be honest, I am not sure why they have done this and I have explained the implications. I don' t really want anyone using the Desktop Designer on the server. But it is the only way we can test the Monitors without also having the Enterprise License for each of our workstations.

So far, we have not had a repeat. But we are monitoring closely

cheers

Found another issue which we had to address

One of our customers is using Amazon virtual server to run or server.
Some times after he reboots the server he has to enter the license details to make our software work again
This is because the rack has different processors.
When the computer rebooted Amazon may allocate a different processor model to the instance therefore our software assumes that it is a different computer now = User has to enter registration details again.

Life full of interesting surprises is it not?