Return
-
Title
In TPAM 2.5, the CLI command reports that "SQLSERVERAGENT is not Running"; should this agent be running? -
Description
When running the CLI commands to return status from TPAM 2.5 (such as "GetStatus -db") it is seen that the SQLSERVERAGENT is not running. Should this agent be running?
Example output from 'GetStatus -db' command:
The Current State of SQLSERVERAGENT is Stopped
-
Cause
In TPAM 2.5, the SQLSERVERAGENT is not used as it was in previous releases. This reporting of the SQLSERVERAGENT status is a remnant from previous versions. -
Resolution
In previous releases such as 2.3/2.4, this agent must be running for the appliance to perform many critical tasks.
TPAM 2.5 does report the status of the SQLSERVERAGENT; however this is a remnant of previous releases. This SQLSERVERAGENT is not used in TPAM 2.5 releases as it was used in previous versions.
The SQLSERVERAGENT being stopped in TPAM 2.5 has no impact on TPAM 2.5 operations.
-
Additional Information
From the TPAM 2.4 TPAM Configuration and Administration Guide: " Without the SQLServer Agent running, TPAM will not be able to perform certain critical tasks, such as: Backups; Background processing (For example, password changes, batch report production,…) Resolution: Reboot (Shutdown/Restart) TPAM.