Note: This applies to DocuShare 6.5.x, 6.6.x and 7.
DocuShare 6.5.x and above has a new built in feature that verifies that DocuShare has successfully shut down all of it subcomponents before trying to start DocuShare again. This feature should avoid needing to ever shut down the DocuShare subcomponents manually due to an improper/incomplete shut down of DocuShare.
1. Stop DocuShare.
2. Wait 10 minutes for DocuShare and all processes to shut down.
If all of the DocuShare processes do not shut down, it may be necessary to kill the DocuShare processes manually using the procedure listed below.
Warning: DO NOT kill the autonomyDISH.exe, autonomyFileSystemFetch.exe, autonomyIDOLServer.exe and content.exe processes. IDOL must be shut down properly, detailed instructions on how to do this are included in this solution.
To kill the DocuShare 6.5.x, 6.6.x.7.x processes on Windows (if necessary):
a. Press Ctrl+Alt+Del and click the Task Manager button. The Task Manager window displays.
b. Click the Processes Tab.
c. Make sure the checkbox for show processes for all users is checked.
d. Click the Image Name column header (grey bar), this will sort the processes by Image Name.
e. Search the Image Name column for the following processes. (This list does not include the Autonomy IDOL Processes - the list of processes below only includes the DocuShare processes)
WARNING: DO NOT forcibly end the process the autonomyDISH.exe, autonomyFileSystemFetch.exe, autonomyIDOLServer.exe or content.exe processes as it may result in corrupted indices.
· dsarchive.exe
· dsconvert.exe
· dssearch.exe
· dsserver.exe
· dssubscript.exe
· dstomcat.exe
· dsworkflow.exe
· java.exe
· rmiregistry.exe
· start_docushare.exe
· dsix.exe (6.5.3 and above)
Note: In DocuShare 6.5.3 the dssubscript.exe process is no longer listed separately, it is part of the dsserver.exe.
Note : You may not see all or any of the processes listed if DocuShare is successfully stopped or partially shut down.
f. Highlight each of the Image Names listed above (one at a time) and click the End Process button.
Note: You may see some Image Names showing up more than once. End Process on all of the process names that match the list above.
g. Verify that there are no longer any processes listed above showing up in the Image Name column. Then click X in the upper right hand corner of the window to close Task Manager.
To How to properly stop any of the IDOL processes (if necessary):
h. To stop the AutonomyDiSH.exe (dish), run idoltool in a command window from the docushare/bin directory:
>idoltool.bat –s stop dish or >./idoltool.sh –s stop dish
Aternatively, you can use the local browser to stop dish by running the following:
http://localhost:20002/action=stop (20002 is the default Service port for dish)
i. To stop AutonomyFileSystemFetch.exe (filesystemfetch):
>idoltool.bat –s stop filesystemfetch or >./idoltool.sh –s stop filesystemfetch
Alternatively, run the following on a local browser to stop filesystemfetch:
http://localhost:10223/action=stop (10223 is the default Service port for filesystemfetch)
j. To stop AutonomyIDOLServer.exe (IDOLServer or Proxy):
>idoltool.bat –s stop idol or >./idoltool.sh –s stop idol
Alternatively, you can use the local browser to stop IDOLServer by running:
http://localhost:9002/action=stop (9002 is the default Service port for IDOLServer)
Note: Stopping the AutonomyIDOLServer.exe will also stop content.exe. However, if the IDOL processes do not shut down immediately, you can stop the content using the following command.
To stop content.exe:
a. >idoltool.bat –s stop content or >./idoltool.sh –s stop content
Alternatively, you can use the local browser to stop content.exe by running
http://localhost:9012/action=stop
(9012 is the default Service port for content.exe).
Note: If content.exe is busy, it may not be able to stop right away.
Note: If your DocuShare installation runs more than one content then you will need to run this command on all the other contents until they have successfully shut down. Example: idoltool.bat stop content0.exe and idoltool.bat –s stop content1.exe.
b. Wait 15 minutes for the idoltool.sh stop command to complete or return.
Note: If the “idoltool.sh stop content0” still hangs, you have to keep performing the command until it shuts down.
Note: If content0 and content1 do not die, then you must repeat step a.
Solution Updated: May 19, 2020
Solution ID: 461