Search the VMware Knowledge Base (KB)
View by Article ID

vCenter Server 4.1 Data Migration Tool fails with the error: HResult 0x2, Level 16, State 1 (1024490)

  • 19 Ratings

Symptoms

  • The vCenter Server 4.1 Data Migration Tool fails
  • If you run the Data Migration Tool for vCenter Server 4.1 from the command-line, you see an error similar to:
DB logs: HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2].
 
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..
 
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
 
Error: vCenter Server DB backup failed
Exiting...
  • The Data Migration Tool continually reports the error and does not copy the existing configuration.

Resolution

This issue can occur for several reasons.  Follow the steps below to troubleshoot the issue:
  
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 .

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 19 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 19 Ratings
Actions
KB: