A newly installed multi-process database application on Windows 2000 Server stops responding to queries. Before restarting the application, what is the safest way to terminate it so that all related child processes are closed cleanly?

Introduction / Context:
Complex server applications often spawn multiple helper or worker processes. When such an application freezes, terminating only the parent process can leave orphaned children holding locks, ports, or shared memory. Windows 2000 Task Manager and other tools provide different termination scopes; choosing the correct one avoids partial cleanup and inconsistent state.

Given Data / Assumptions:

• Application is multi-process (spawns child processes).
• Server OS: Windows 2000 Server.
• Symptom: application stops responding to queries.
• Goal: cleanly close all related processes before restart.

Concept / Approach:
Terminating the process tree ensures the parent and all child processes are closed in one action, freeing resources like file handles, sockets, and database locks. Killing only the top process may leave children running, causing port binding conflicts or data file contention when the application restarts. Ending Explorer.exe disrupts the shell but does not help service-style applications and may complicate recovery.

Step-by-Step Solution:
1) Identify the application's main executable (Application.exe) and confirm child processes exist.2) Use Task Manager or an administrative tool (e.g., tskill/pskill) to choose “End Process Tree.”3) Wait for handles to release; confirm that all child processes terminated.4) Restart the application service or executable and verify normal operation.

Verification / Alternative check:
Check that the application's TCP/UDP ports are free (e.g., with netstat) and that no child processes remain. Logs should show a clean restart without “address already in use” or “file locked” errors.

Why Other Options Are Wrong:

• End task / End process only: May leave child processes running and resources locked.
• End Explorer.exe too: Unnecessary; affects shell stability without addressing the hung service.
• None of the above: Incorrect because ending the process tree is the appropriate scope.

Common Pitfalls:
Force-killing database engines without checking for child workers; restarting immediately and encountering the same lock/port issues due to orphans.

Final Answer:
End the Application.exe process tree