Autostart 5.2 Process Proxy problem

Upgrade from CoStandBy server AAdvanced 5.1.x to Autostart 5.2 is not really supported although it seemingly works. Upgrade from AAM is, though.
I'm not saying that this is the cause of all your problems, but it may as well be. I'd suggest installing Autostart 5.2 fresh and going from there.

Thanks for the response. I probably didn't put my question very well. I have done a fresh install, on a test environment to try and cover any issues before we put it into production.

The test environment is identical to the production environment, except for using Autostart instead of CoStandby Server.

Since my post we have failed the system over manually (and once accidentally) several times. The Proccess Proxy (created by the SQL Server module) however in all instances simply reports that it is "starting" and any attempt to stop it gets the status line error of "Configuration not found". The indicater is a yellow colour.

Cheers,
Neil

Thanks for the clarification. I'd be honest and say that I haven't had a chance to test the SQL module with version 5.2 so it is possible that there may be problems with it. I wonder if you have any databases configured to be monitored in the MSSQL module config? These would be the ones that are checked by the proxy process. Maybe it gets confused if there is nothing configured for the proxy to check. Other than that, I'd take a look at the log files and exported domain info to see if the proxy process is set up correctly.
Also, is the MSSQL version you are using a supported one?

I checked the databases to be monitored and I have only selected Master at this stage. The SQL version is 2000 SP4. I had a look at the log files I could find and couldn't identify anything in particular, could you help me with how to export the domain info and what I am looking for.

Thanks again for your help.

A quick question before continuing - when you did these tests, were you logged in locally on the cluster node(s) or using Terminal Client? I'm asking because there are some known problems with MSSQL proxy process and remote connections.

You can export the cluster database using the export option in the console (one of the top row icons) after clicking on the domain name in the left pane. It will export database in the flat text file. However you do need some experience to be able to find your way around it. In the mean time I suggest you click on the proxy process in the console and check its configuration, for example is the proxy binary file configured and so on. It sounds a bit like the module data was not imported in the cluster database correctly.

The configuration in the console looks OK, but the thing that occurred to me is the variable FT_DIR may be incorrect. Is there any way of checking what is getting passed to the proxy, or will the export show me that.... In any case I will check the export today and let you know what I find.

Good point. Just check the system environment or the output of set command in cli if it points to the correct location.

I don't think it's environmental problem. I found it myself with 2 condition 1st one is IIS Module and second one is Oracle module. The cause of the problem is always mis-configuration (wrong parameter) for the module (for example Oracle Base path), once we trying to start process it keep starting with no end, event we reboot both node.

The question is how autostart handle the starting process (for example timeout) and how we can clear the wrong state of that process.

The work around for me is reconfigure AutoStart (that can be done during the implementation).

Regards,
Kawin