AppAssure Agent Not Detecting SQL Server or Cannot connect to SQL instance (4036214)

This article describes an issue with the AppAssure Agent on an SQL Server. It should be noted that this is not a product issue.

You may experience this issue because a 32-bit instance of SQL Server was installed on a 64-bit agent, which would subsequently mean that your settings were not all configured for a 64-bit machine. You may receive the following errors:

ERROR 2013-03-11T22:37:15 [15] – Replay.Common.Implementation.WmiApi.Wmi(RequestUri=https://SQL:8006/apprecovery/api/agent/metadata/fullMetadata ClientAddress=10.0.1.20:57581 Service=Replay.Agent.Management.Metadata.AgentMetadataManagement Method=GetCurrent) 

Unknown WMI error: System.IO.FileNotFoundException

 ERROR 2015-05-08T22:10:24 [22] - Replay.Common.Implementation.WmiApi.Wmi ()

Windows Registry Disclaimer:

Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.

1. You need to determine which SQL WMI namespace is used. To do this, complete the following steps.
   • Open the WMI Properties.
   • Open the Computer Management screen.
     • Select Computer
     • Right click Manage
   • Select the Service and Application tab and click WMI Control.
   • Right click Properties and select the Security tab.
   • Expand the Root folder and then expand the Microsoft and SqlServer folders.
   • Look for namespaces ComputerManagement10 and ComputerManagement11. Please note that these are hypothetical values used specifically for this article. Titling will be different within your environment.
   • Open the WMI Tester (wbemtest) and connect to the namespace ComputerManagement11 (root\microsoft\sqlserver\ComputerManagement11).
   • Run the query SELECT * FROM ServerNetworkProtocol WHERE InstanceName = ‘MSSQLSERVER’ AND Enabled = ‘True’
     • NOTE: ”MSSQLSERVER” is used as an example for this article. If you have a different instance name, please use it here.
   • The query should result in a WMI Loader Failure.
2. Open the Registry editor.
3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server.
4. Copy the information from the Installed Instances key and all branch MSSQLServer (from from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQLServer) to the following:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server
   • NOTE: To copy the branch, export and open the file in NotePad. From there, change the path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQLServer to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQLServer. At this point, you can export the changed branch back.
5. Restart the Core Service.
6. You should now be able to setup attachability settings within the Core.