Troubleshooting
Problem
Guardium DC Controller not starting up with Guardium WinSTAP
Symptom
On the MS Window Server (DB Server) Guardium WinSTAT shows up and running but the Guardium DC Controller is not running.
On the Guardium Collector's GUI the corresponding S-TAP shows as down (not running).
Cause
This issue could be caused due to wrong configuration of the INSTANCE_NAME in file GUARD_TAP.INI
Environment
MS Windows Enterprise Server
MS SQL Server
Diagnosing The Problem
1- Review the INSTANCE_NAME configuration/value in the file GUARD_TAP.INI
C:\Windows\SysWOW64\guard_tap.ini
[DB_MSSQL1]
PORT_RANGE-START=1433
PORT_RANGE_END=1433
TAP_DB_PROCESS_NAMES=SQLSERVER.EXE
TAP_IDENTIFIER=NULL
NAMED_PIPE=SQL\QUERY, PIPE\SQLLOCAL
INSTANCE_NAME=MSSQLSERVER
DB_TYPE=MSSQL
NETWORKS=1.1.1.1/0.0.0.0
2- At the Windows DOS prompt, execute the following command
tasklist /svc | findstr sqlservr
Compare the instance name returned by the command with the INSTANCE_NAME configured in the INI file, if it is different you need to change to the valuer returned by the command.
If the command returns MSSQLSERVER, you are using the default MS instance name MSSQLSERVER, if it returns MSSQL$xxxxxx, you are uisng a named instance "xxxxxx". Configure "INSTANACE_NAME=xxxxxx" in the GUARD_TAP.INI file.
Resolving The Problem
If it returns MSSQLSERVER, you're using the default instance MSSQLSERVER.
Please set INSANCE_NAME=MSSQLSERVER in guard_tap.ini
If it returns MSSQL$xxxxx, you're using a named instance and the instance name
is xxxxx. Please set INSTANCE_NAME=xxxxx in guard_tap.ini.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22001530