We need more info in order to help. What is the main problem, how to make the process run correctly or how to get it offline? If it is a process, what did you use for existence monitor? Is it a script or something else?

Thank you for your reply.

the main problem is this processer Did not work.i can not delete it now.

In the above Pictures.

WCM can normal startup and shutdown,but the tomac6.exe Did not work.

TRSSERVER is a *.bat,can normal startup,but can not stop.did not work too. now,it can not be delete.

i use "notepad.exe" to test,can normal startup,but No process and Interface Appear.Even if i select the Allow access to the Windows desktop.

You are missing the stop operation (at least for tomcat). In that case when you shutdown the process, nothing gets executed and Autostart keeps waiting for the existence monitor to exit with an errorcode (which will never happen). Depending on the existence monitor used you can either manually do whatever it takes to make it exist with an errorcode or edit the appropriate existence monitor in $FT_DIR/StateMon/E_*.* and just enter exit (1); in the first line. All this assuming that you are using a script for the existence monitor at all.

Or alternatively, open the ftcli command line interface for autostart and force the status of the process to offline:

ftcli> ForceProcState [Proc_ID] offline

I think the command is correct as I am talking from the top of my head, but this should get you going. Once executed the process should go to offline state.

Let me know if you managed to do it.

in autostart 5.3sp3,the  Executable (default)'s stop operation Default is No command,but now 5.4 is none.i already select the "No command".

i found Even if let it none,it also can stop Normal.

Now the question is Even if it can start or stop properly,In fact, no process in the “Task manager”.

about how to delete it,could you please say in more detail.

ant "ftcli> ForceProcState [Proc_ID] offline" ,what is the proc_ID?

many thanks.

Perhaps the autostart5.4's processes module have  some problem .

i test in 5.3sp3,have No problem.

Hi,

Help extract

----------------------------

If the interactive process is brought online in the same session in which the first interactive AutoStart process was configured, then the process will not start until the user logs off and logs in back to the node, even though the console would show the process status to be online.

----------------------------

thanks.

What does it mean "You must log off."

Hi,

Start button --- Log Off button click

Hi,

The specification has been greatly changed from 5.3SP3.

For example, "Allow Access to the windows desktop" is enable.
You must log off.

I submitted the request of the specification change and fixed it.

In my environment, there is not a problem for a stop and start of the process.

hi,

So what use is it?

It could be that it terminates the process ID and it is not working correctly. Most of my experience is UNIX related and we have always used the appropriate perl script to start or stop the process. However I would advise to try and stay away from the "latest and greatest" version. For example Autostart 5.3SP5 has serious problems on Windows 2008, and who knows what is lurking in 5.4 which is very new. I suggest you start with 5.3SP4 and make sure the problems are present or not present there.

Regarding the Proc_ID, it is just the name of the process as configured in Autostart.

hi:

when i reboot the system Many times,it go to offline,can be delete now.

thanks.

but,I have a new problems.i created a EMC Mirroring for Windows data sourec Including the MSSQL data.

when the initial attach and synchronization is complete,i Detached it,and Attached it to target node.

But the MSSQLSERVER Services can not start at the target node.

the SQL install path is the same.the system data files is install to the mirrow driver.

and then i Detach it ,Attached again to the target nod,
the Icon turn to Blue Continued for a long time,
I found the CHKDSK is Running.I don't know how long this will last and Why should verify.

Hello,

Wanted to respond to this part of the post below.  There seem to be two parts to this.

when the initial attach and synchronization is complete,i Detached it,and Attached it to target node.

But the MSSQLSERVER Services can not start at the target node.

the SQL install path is the same.the system data files is install to the mirrow driver.

This could have several causes, depending on the setup and exactly how you tested this.  Did you set this up as a Resource Group?  or just the Data Source by itself?  Where the MSSQL Services/processes all stopped on the initial node before relocation.

and then i Detach it ,Attached again to the target nod,
the Icon turn to Blue Continued for a long time,
I found the CHKDSK is Running.I don't know how long this will last and Why should verify.

For this part again it depends on exactly what you did with the Resource Group and what the states of the MSSQL Services/processes were.

Generally, a chkdsk will be run if the Operating System has set the dirty bit on the disk.  As part of the default for the Mirror Data Source we do check if the dirty bit was set by the OS, and run a chkdsk on attach if it was (you can turn this off).  The setting of the dirty bit is an OS function outside of AutoStart.  There could be a number of reasons for this.  For example, this could be a timing issue.  Sometimes it is necessary to set delays between the offlining of Services/processes and the detach of the Data Source to be sure that the OS has flushed all data to the disk.  That's just one example.

Hope this helps out.

Best Regards,

Daniel Vongehr

EMC Technical Support

Hi,

As far as we have seen with AutoStart 5.3.4 and 5.3.5, the standard process offline/termination is working correctly.

If you are experiencing an issue with this, I'd advise a Support case be opened so we can investigate the symptom with you directly.

It is avisable that you obtain the latest cumulative Hot Fixes for 5.3.4 and 5.3.5. There are some fixes around processes that use "Allow Access to the Windows Desktop". Also there are many other fixes in these cumulative Hot Fixes that hopefully will address your concerns about 5.3.5.

Please contact EMC Technical Support to obtain the latest cumulative Hot Fixes.

Also please let us know if there are issues that you have seen with 5.3.4 and 5.3.5 that are not addressed with these cumulative Hot Fixes.

Note: For the most part all of the contents of the cumulative Hot Fixes from 5.3.4/5.3.5 were included in the release version of 5.4.

Hope this helps out.

Best Regards,

Daniel Vongehr

EMC Technical Support

I do not understand  Why after the synchronization.target node Need to running CHKDSK, and Inconsistent data files, my partition is 200G,How long does it take?

many thanks.