Troubleshooting MS SQL Windows

This section helps you troubleshoot the common problems that you might encounter when using certificate server functionalities. This guide will give more troubleshooting processes on server addition, deletion, import, export, push, bind, rollback and other actions associated with MS SQL Windows.

Issues in Communicating to MS SQL

Error Message Possible Cause Possible Solution
Communication to <hostname> has failed

Gateway agent not reachable.

Device not reachable from the gateway agent

Ensure gateway is configured properly and the APIs are accessible from AppViewX.

Ensure device and gateway agent are in the same domain and device is accessible from gateway agent.

Communication to <hostname> has failed Hostname or Credentials configured is wrong Ensure hostname and the device credentials configured while device addition is valid.
Device version fetch has failed. MSSQLSERVER service instance is down Restart the MSSQLSERVER instance
Device version fetch has failed. Command not supported by MS SQL version Execute the version command SQLCMD -Q 'SELECT @@VERSION;' -t 3 in the CLI of the device to check if it returns version response

Issues in Config Fetch

Error Message Possible Cause Possible Solution
Communication to <hostname> has failed

Gateway agent not reachable.

Device not reachable from the gateway agent

Ensure gateway is configured properly and the APIs are accessible from AppViewX.

Ensure device and gateway agent are in the same domain and device is accessible from gateway agent.

PTPLD178 has 0 instances.

No installed MS SQL instances.

Installed instances are not up and running.

Execute (get-itemproperty 'HKLM:\\SOFTWARE\\Microsoft\\Microsoft SQL Server').InstalledInstances in the device as a powershell script and check if it returns the MS SQL instances

Issue in Discovery

Error Message Possible Cause Possible Solution
Received failed response from batch No valid certificates in store that are binded to the MS SQL instances. Ensure the certificates are binded to a MS SQL instance.

Issue in CSR generation

Error Message Possible Cause Possible Solution
CSR Submission Failed User may have restricted access to the path configured for the “CSR FileName” and “Key File name” Kindly ensure the user configured for device addition has read/write access to the path configured.

Issue in Push and Rollback

Error Message Possible Cause Possible Solution
Error while pushing certificate in Device : <device name>.PrivateKey not available. Private key is not available to parse certs. Kindly ensure to push certs with private key.If privatekey is available in device please select privateKeyInDevice option.
Error: “/LOCAL_MACHINE/CertificateAuthority” does not exist CertificateAuthority Store is removed from the Store Create a CertificateAuthority store.