欢迎进入网络技术社区论坛，与200万技术人员互动交流 >>进入 我的一位同事vCenter 4数据库迁移到vCenter 4.1采用datamigration工具位于vCenter安装光盘。运行他收到以下错误backup.bat脚本后： DB logs: Msg. 3013, Level 16, State 1, Server , Line 1 BACK
欢迎进入网络技术社区论坛，与200万技术人员互动交流 >>进入
我的一位同事vCenter 4数据库迁移到vCenter 4.1采用datamigration工具位于vCenter安装光盘。运行他收到以下错误backup.bat脚本后：
DB logs: Msg. 3013, Level 16, State 1, Server
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..
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.
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:
Click Start > Run, type services.msc and click OK.
Right-click SQL Server (SQLEXP_VIM), then click Start.
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.
Ensure that Named Pipes and TCP/IP protocols are enabled on the server. To ensure they are enabled:
Launch the SQL Server Configuration Manager utility and go to SQL Server 2005 Network Configuration.
In the left-hand pane, highlight Protocols for SQLEXP_VIM.
In the right-hand pane, right-click Named Pipes and select Enable, then right-click TCP/IP, and select Enable
Click Properties.
On the IP Address tab, ensure that Enable is set to Yes for each network adapter that is listed.
Click OK to close the TCP/IP Properties dialog.
In the left-hand pane, select SQL Server 2005 Services, right-click SQL Server (SQLEXP_VIM), then click Restart.
Ensure there are no Invalid entries in the Named Pipes Protocol under SQL Server 2005 Network Configuration. To check if there are invalid entries:
Launch the SQL Server Configuration Manager utility and navigate to SQL Server 2005 Network Configuration.
Click Protocols for SQLEXP_VIM and then double-click Named Pipes in the right panel.
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 .
