Error ID: 4387 during the reinstallation of MABS .

Sergiy Okhremchuk 0 Reputation points
2023-07-08T20:17:03.19+00:00

Hello.

MABS v4 was uninstalled :

User's image

During the reinstallation of a MABS (same installer version v4, SQL instance is form a firs installation) during the phase of selection of existing SQL instance - an Error ID: 4387 is thrown and installation aborted.

The error log file is in an attachment. DpmSetup.log

ALSO the

sql server configuration manager is not starting with error: Cannot connect to WMI provider..... invalid class 0x80041010

Management studio successfully connecting to an instance MSDPMINSTANCE in sql

Please let me know if someone has the same issue.

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,357 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Amardeep Saini 1,650 Reputation points Microsoft Employee
    2023-07-11T08:08:49.0666667+00:00

    Looking at the DPM Setup Logs it seems that the WMI Class for SQL is broken due to which you are getting Invalid Class error while querying to WMI.

    [8.7.2023 16:12:28] Information : [SQLSetupHelper.GetReportingNamespaceForInstanceName]. Reporting Namespace found. Reporting version : V16
    [8.7.2023 16:12:28] Information : [SQLSetupHelper.GetWMISqlServerNamespace]. SQL Namespace found. SQL Namespace : \\ISPAN-HV2\root\Microsoft\SqlServer\ComputerManagement16
    [8.7.2023 16:12:28] Information : Query WMI provider for SQL Server.
    [8.7.2023 16:12:28] Information : Querying WMI Namespace: \\ISPAN-HV2\root\Microsoft\SqlServer\ComputerManagement16 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$MSDPMINSTANCE' and PropertyName='Version'
    [8.7.2023 16:12:28] * Exception :  => System.Management.ManagementException: Invalid class 
       at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.InspectHelper.GetSqlServerVersion(String instanceName, String sqlServerMachineName, ConnectionOptions wmiConnectionOptions, String sqlNameSpace)
    [8.7.2023 16:12:28] * Exception : Expecting the following exception. Ignoring intentionally.  => System.Management.ManagementException: Invalid class 
       at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.InspectHelper.GetSqlServerVersion(String instanceName, String sqlServerMachineName, ConnectionOptions wmiConnectionOptions, String sqlNameSpace)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.InspectHelper.DetectSqlServer(String instanceName, String sqlServerMachineName, ConnectionOptions wmiConnectionOptions, String sqlNameSpace, String minSqlRequiredVersion)
    [8.7.2023 16:12:28] Information : SQL Server instance MSDPMINSTANCE is not present on this system.
    [8.7.2023 16:12:28] Information : Query WMI provider for SQL Server.
    [8.7.2023 16:12:28] Information : Querying WMI Namespace:  for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$MSDPMINSTANCE' and PropertyName='Version'
    [8.7.2023 16:12:28] * Exception :  => System.Management.ManagementException: Invalid class 
    
    

    Re-register the WMI classes by running the Mofcomp command on MABS Server should fix this issue:

    C:>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

    Note: The path for Mof file might be different on your MABS Server depending on the SQL version installed on the machine. So accordingly put the correct path in the command

    0 comments No comments

  2. Amardeep Saini 1,650 Reputation points Microsoft Employee
    2023-07-11T15:04:55.9533333+00:00

    Sergiy, seems we are failing with another exception for MABS Setup. Request you to please check below pre-req to install MABS.

    Azure Backup Server is designed to run on a dedicated, single-purpose server. You can't install Azure Backup Server on:

    • A computer running as a domain controller
    • A computer on which the Application Server role is installed
    • A computer that's a System Center Operations Manager management server
    • A computer on which Exchange Server is running
    • A computer that's a node of a cluster

    If all the conditions are met then I would suggest to re-install the OS on the machine and try the fresh install of MABS which should install SQL and MABS application without any issues.

    Request you to try it and update if it worked for you or not.


  3. Amardeep Saini 1,650 Reputation points Microsoft Employee
    2023-07-11T15:24:56.3566667+00:00

    In that case, I would advise to uninstall all SQL components from the server, restart the server, try running mofcomp again after reboot.

    Re-register the WMI classes by running the Mofcomp command on MABS Server should fix this issue:

    C:>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

    Try MABS installation again and see if that works.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.