{"id":2877,"date":"2016-03-04T06:24:00","date_gmt":"2016-03-04T06:24:00","guid":{"rendered":"https:\/\/wiki.melberi.com\/uncategorized\/vcenter-migration-error-db-logs-hresult-0x2-level-16-state-1-named-pipes-provider-could-not-open-a-connection-to-sql-server"},"modified":"2017-10-24T10:01:38","modified_gmt":"2017-10-24T10:01:38","slug":"db-logs-hresult-0x2","status":"publish","type":"post","link":"https:\/\/www.melberi.com\/wiki\/vmware\/db-logs-hresult-0x2","title":{"rendered":"vCenter Migration error DB logs HResult 0x2 Level 16 State 1 Named Pipes Provider: Could not open a connection to SQL Server"},"content":{"rendered":"
\n
\n

vCenter Server 4.1 Data Migration tool error<\/b><\/h2>\n<\/div>\n

While trying to migrate my vCenter server 4 to 4.1 using the Data Migration Tool, following error occurred<\/p>\n

DB logs: HResult 0x2, Level 16, State 1
\nNamed Pipes Provider: Could not open a connection to SQL Server [2].
\n[ERROR] 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
\nthe default settings SQL Server does not allow remote connections..
\nSqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
\n[ERROR] Error: vCenter Server DB backup failed
\n[ERROR] Exiting…<\/b><\/p>\n

Resolution:<\/b><\/u><\/h4>\n

This issue can occur if the vCenter Server is mis configured.<\/p>\n

Troubleshoot this issue:<\/b><\/u><\/h3>\n

Note: To verify some of these settings, it is necessary to install Microsoft Studio Manager Express on the source server.You can download this utility from the Microsoft Download Center <\/a>
\n1. Check whether the SQL Server service itself is running on the existing vCenter Server.\u00a0<\/b>
\nHaving this service disabled or not running can cause this issue and prevent the script from running. To ensure that it is running:
\n1.\u00a0 Click Start > Run<\/b>, type services.msc<\/b> and click OK.<\/b>
\n2.\u00a0 Right-click SQL Server (SQLEXP_VIM)<\/b>, then click Start<\/b>.
\n2. Check whether the firewall is blocking the MSSQL server:<\/b>
\n\u00a0\u00a0 <\/b>Ensure there are no firewalls blocking access to the SQL Server instance on the vCenter Server. If you are unsure, disable these services during migration.
\n3. Check Named Pipes and TCP\/IP protocols are enabled on the server<\/b>.
\nTo ensure they are enabled:<\/p>\n