### Human: Can you tell about Nutanix Database Service | Debugging Windows DB Server VM Provisioning Failures. ### Assistant: This article describes debugging Windows DB server VM provisioning failures.. Note: Nutanix Database Server (NDB) was formerly known as Era.

Scenario 1: Sysprep fails when antivirus software is installedSysprep of a VM could fail when antivirus software is installed in the system.

Operation logs /home/era/era_base/logs/drivers/sqlserver_database/create_dbserver/<operation_id>.log or /home/era/era_base/logs/drivers/sqlserver_database/provision/<operation_id>.log:

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

From sysprep logs /home/era/era_base/logs/drivers/sqlserver_database/create_dbserver/<operation_id>_syspre_logs/Panther/setupact.log or /home/era/era_base/logs/drivers/sqlserver_database/provision/<operation_id>_syspre_logs/Panther/setupact.log:

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

Scenario 2: Joining a workgroup/domain failsIf the software profile hostname is longer than 15 characters, joining a workgroup gets stuck.

This is identified by checking sysprep_task.log from the zip file generated by the sysprep failure. If the last line is workgroup join, the issue is identified. See sample output below:

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

Another situation where this issue can be seen is if there is a domain join failure. In this case, there is a file called sysprep_task_domain.log. The domain join failure would be present in this log file.

Below are some of the reasons for a domain join failure:

The custom domain OU path is incorrect.The credentials provided do not have the necessary permission to join the domain.The credentials are incorrect.Another VM with the same name exists in the domain already.

Scenario 3: Network connectivityWhen there is no network connectivity between the Era server/agent and the DB server VM, the WinRM connection from the Era server/agent would fail with the following message:

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

Scenario 4: Disabling WinRM as part of GPO policyWhen the DB server is added to the domain, and you have an active GPO policy that might disable any remote WinRM connection to the newly provisioned DB server, the provisioning would fail with WinRM connectivity failures.

Scenario 5: Missing virtIO installationWhen the software profile does not include VirtIO (a collection of drivers), the DB provisioning process cannot add NICs to the DB VMs. This will cause the provisioning process to fail. Here is the error message in the /home/era/era_base/logs/drivers/sqlserver_database/create_dbserver/<operation_id>.log:

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

Sample screenshot:



Scenario 6: Locked service accountWhen the Era worker service account is locked in the domain, DB provisioning fails with the following error message in /home/era/era_base/logs/drivers/sqlserver_database/create_dbserver/<operation_id>.log:

[2022-08-01 10:10:33,189] [140408303626048] [INFO    ]  [0000-NOPID],Got an successful status code

The domain user in the above operation log is the SQL Service Startup Account used when provisioning the DB Server:



Go to the Active Directory -> Users and Computers, and search for this account. You may see that this account is locked.

. Resolution 1: Sysprep fails when antivirus software is installedAntivirus software should be disabled on the software profiles prior to provisioning.

Disable or delete the antivirus software service (see the antivirus software's documentation on how to do this).Take a new software profile (see Creating a Software Profile in the NDB User Guide).Perform provision DB server operation (see SQL Server Database Provisioning in the NDB User Guide).

Resolution 2: Joining a workgroup/domain failsChange the hostname of the source VM to less than 15 characters, or engage Nutanix Support to skip joining a workgroup as part of the provision.

If the sysprep_task.log does not have more than 4-5 lines of output, this is a different issue with the same error message. In this case, engage Nutanix Support for assistance.

To resolve a domain join failure:

Correct the OU path.Give different credentialsDelete the entry of the same name or provision with a new name.

Resolution 3: Network connectivityEnsure that the Era server/agent can connect to the subnet where the VM is being deployed.

Resolution 4: Disabling WinRM as part of GPO policyEnable WinRM remote connection to the host via GPO.

Resolution 5: Missing virtIO installationInstall VirtIO in the gold image DB VM, then create a new software profile from it. For the VirtIO installation, refer to Nutanix VirtIO for Windows.

Resolution 6: Locked service accountUnlock the service account in the domain by ticking the checkbox.

. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.