VMware: vCenter Datamigration: Msg 3013, BACKUP DATABASE is terminating abnormally

One of my colleagues was migrating vCenter 4.0 database to vCenter 4.1 by using the Datamigration Tool located at the vCenter Installation CD. After running the Backup.bat script he received the following error:

DB logs: Msg. 3013, Level 16, State 1, Server <name> , Line 1 BACKUP DATABASE is terminating abnormally

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..

 

image

Resolution:

Note: To verify some of these settings, it is necessary to install Microsoft Studio Manager Express on the source server (the server you are migrating from). You can download this utility from the Microsoft Download Center.

  1. Ensure that the SQL Server service itself is running on the existing vCenter Server. Having this service disabled or not running can cause this issue and prevent the script from running. To ensure that it is running:

    1. Click Start > Run, type services.msc and click OK.

    2. Right-click SQL Server (SQLEXP_VIM), then click Start.

  2. Ensure that there are no firewalls blocking access to the SQL Server instance on the vCenter Server. If you are unsure, disable these services during migration, or make an exception on your firewall to allow this service to run. Ensure that TCP Port 1666 is allowed access to the service. Configuring specific firewalls is beyond the scope of this article. Consult your firewall vendor for more information.

  3. Ensure that Named Pipes and TCP/IP protocols are enabled on the server. To ensure they are enabled:

    1. Launch the SQL Server Configuration Manager utility and go to SQL Server 2005 Network Configuration.

    2. In the left-hand pane, highlight Protocols for SQLEXP_VIM.

    3. In the right-hand pane, right-click Named Pipes and select Enable, then right-click TCP/IP, and select Enable

    4. Click Properties.

    5. On the IP Address tab, ensure that Enable is set to Yes for each network adapter that is listed.

    6. Click OK to close the TCP/IP Properties dialog.

    7. In the left-hand pane, select SQL Server 2005 Services, right-click SQL Server (SQLEXP_VIM), then click Restart.

  4. Ensure there are no Invalid entries in the Named Pipes Protocol under SQL Server 2005 Network Configuration. To check if there are invalid entries:

    1. Launch the SQL Server Configuration Manager utility and navigate to SQL Server 2005 Network Configuration.
    2. Click Protocols for SQLEXP_VIM and then double-click Named Pipes in the right panel.
    3. On the Protocol tab, notice the value of the Pipe Name item. If the value contains an entry similar to \\.\pipe\MSSQL$SQLEXPRESS\sql\query , rename the entry to \\.\pipe\sql\query .
  5. Source: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has 15+ years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

9 thoughts on “VMware: vCenter Datamigration: Msg 3013, BACKUP DATABASE is terminating abnormally

Leave a Reply

Your email address will not be published. Required fields are marked *