AAM Agent 5.2 do not start on Windows 2003

That is strange...what this message means is that agent has problems reading from the configuration database that is supposed to be fresh during the install. Possible causes may be antivirus solutions that may try to access the database files. Autostart requires exclusive access to these db files at all times.
Do did try to reinstall? It is possible that something corrupted the db during the last install.

I have first install the full configuration on June.
It was OK.

Then, the agent start to stop itself with no reason or perhaps because of the network between the 2 nodes (geo-cluster).

The network equipment has been changed this summer and i'm comming back to repare.

So i decided to uninstall ant re-install.
I've done this 3 or 4 times this morning and each time i've had this error : the service is stopping while trying to start.

Just before, i was trying with AAM 5.2 SP3 and the log was less "verbose".
Now i'm with the AAM 5.2 (no SP).

The last uninstall, i've checked the "erase all information" case and i've done 2 ou 3 reboots.

This is a first node

It seems that there is a problem with the cluster replicated database. This is a new install? Is this a first node or is there already an existing one? We need these details before suggesting anything...

This is what i have done.

And this is why i do not understand why the db seems to be corrupted : it is a new and fresh db.

I've tried to place myself in fresh new installation condition.

but i will try without the anitvriusES : Mc Affy + Windows defender.

Oh, so it is not a completely fresh install?
Do you have a backup of your cluster domain? It seems that the cluster db got corrupted, but if you uninstall the cluster completely and delete the installation directory from the disk, and then reinstall, you should be fine. However you will lose your configuration so make sure that you have a domain export to import later on. Although I would not try to use the export of the domain which is already showing signs of corruption. You do have a valid backup, right?

Weird, maybe someone else has some suggestions....the error -7 means "No current record exists. The current record is NULL_DBA". You can find these details at www.raima.com.
But I still don't know what may be causing it.

Did not help.

I have steel the same problem.

I've uninstall once again AAM and restart the server.

The network icons on the tray were OK.

But when I install AAM, it takes several minutes before the icons come up : they comme up when i get the message that a service did not start.

Yes, try turning them off, those are prime suspects. And make sure they do not try to scan Autostart directory in the future.

The "Unknown Raima Database Error:-7" indicates that the AutoStart database is corrupt and usually this indicates it will not be able to start successfully. When you un-install AutoStart I would suggest that you also verify the Environmental variables are removed from the environment. Sometimes these variables are not properly removed by the Uninstall and could cause AutoStart confusion after the reboot. It is not until after the reboot that the AutoStart database gets created on the first node.

FTC_FT_DIR
FT_DBDIR
FT_DIR
FT_DOMAIN
FT_LNODE

I will try.

But after that, I will re-install Windows.

OK.

The problem came from the environement variables.

The service is now OK.

Thank you for your help.