Explains how to fix a SQL WMI error and other issues with the display of SQL in the unitrends UI.
SQL server 2005 (other than Express) and SQL 2008 and higher
Symptoms / Description
When installing an agent, or, checking for SQL in the UI, a registered windows client does not list having a SQL component, though SQL is known to exist on that server.
By setting the debugging level in C:/PCBP/master.ini on the SQL server for the value "WBPS" to level 5, significant information about the search effort to locate a SQL database can be noted.
After re-saving the client in the Unitrends UI, or performing an inventory sync, the agent will re-scan the client and log it's progress.
WBPS.log files in C:/PCBP/logs.dir can now be viewed to have more information.
Errors similar to below are commonly seen and indicate a clear WMI failure:
May 24 15:33:53 : CSqlVssOdbc::QuerySQLInstancesMngt: Query StartupType of SQL Service May 24 15:33:53 : CSqlVssOdbc::ExecuteWMIQuery: Connecting to WMI namespace root\Microsoft\SqlServer\ComputerManagement13 May 24 15:33:53 : CSqlVssOdbc::ExecuteWMIQuery: Could not connect WMI namespace 'root\Microsoft\SqlServer\ComputerManagement13' failed 0x8004100e <Unknown error code>. May 24 15:33:53 : CSqlVssOdbc::QuerySQLInstancesMngt: Query StartupType of SQL Service . . . . May 24 15:33:53 : CSqlVssOdbc::ExecuteWMIQuery: Getting proxy blanket May 24 15:33:53 : CSqlVssOdbc::ExecuteWMIQuery: Executing query 'SELECT ServiceName, HostName, DisplayName, State, StartName from SqlService where SQLServiceType=1' May 24 15:33:53 : No more SQL Services.
Before beginning, ensure that the IP address of the server has been entered correctly by navigating to Configure > Protected Assets and selecting the server that is missing the SQL instances, then click on Edit.
CAUTION! The following process may cause damage to a SQL installation, especially assuming there's already a server configuration problem that causes WMI to fail or be improperly configured already.
Unitrends STRONGLY encourages customers and partners to engage Microsoft on this issue before proceeding. This is a Microsoft software failure and not a Unitrends issue.
The following instructions are provided as a reference for a Microsoft supported process that "may" resolve some issues with the SQL MOF configuration that can cause WMI to fail to list SQL as a service properly.
Open the command prompt as an administrator and run this command:
mofcomp "C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
If you get the “FILE NOT FOUND” message then you need to reinstall the WMI writer using these commands:
1. Launch the SQL Server Setup program (setup.exe) from SQL Server installation media.
2. After prerequisites and system verification, the Setup program will display the SQL Server Installation Center page.
3. Click Maintenance in the left-hand navigation area, and then click Repair to start the repair operation.
4. Setup support rule and file routines will run to ensure that your system has prerequisites installed and that the computer passes Setup validation rules. Click OK or Install to continue.
5. On the Select Instance page, select the instance to repair, and then click Next to continue.
6. The repair rules will run to validate the operation. To continue, click Next.
7. The Ready to Repair page indicates that the operation is ready to proceed. To continue, click Repair.
8. The Repair Progress page shows the status of the repair operation. The Complete page indicates that the operation is finished.
There are a few causes preventing SQL from Displaying in the UI properly. The base issue is that the installed Unitrends Agent was unable to detect SQL by querying WMI and VSS. The most common conditions are as follows, but this article is limited in resolution to resolving WMI issues:
the wrong agent is being used and a newer agent is required to reference newer SQL installations
SQL 2005 express or SQL 200 or older is used. Those are only supported by the legacy SQL agent.
SQL has an installation/configuration problem, typically a WMI problem created by a failed installation or upgrade process, or a VSS failure. (see notes above)
other applications that should not co-exist with SQL (WSUS or SCCM using the Windows Internal Database/WID cannot co-exist with a SQL installation for example).