Thursday, January 6, 2011

Error Microsoft Lync Server 2010 publishing topology with Event ID: 17836 error on SQL / Backend Server

Ran into an interesting problem while publishing a Microsoft Lync Server 2010 topology earlier this week that had very little to Lync but rather the network. The following are the errors:

You’ve completed filling in the required information for your new Lync Server 2010 topology and initiate the Publish Topology option:

image

The following errors are shown in the Publishing in progress window:

Ensure that <yourSQLserverName is a valid SQL instance.

Exception of type ‘Microsoft.Rtc.Management.Deployment.DeploymentException’ was thrown.

Exception of type ‘Microsoft.Rtc.Management.Deployment.DeploymentException’ was thrown.

Exception of type ‘Microsoft.Rtc.Management.Deployment.DeploymentException’ was thrown.

Exception of type ‘Microsoft.Rtc.Management.Deployment.DeploymentException’ was thrown.

Exception of type ‘Microsoft.Rtc.Management.Deployment.DeploymentException’ was thrown.

image

Shortly after these error messages are shown, you will find the following window presented:

image

Viewing the logs will show you something like this:

Error: Error connecting to "sql02.domain.com\Lync2010" while installing "CentralMgmtStore". Verify that the SQL instance is running, connections are not being blocked by a firewall, and that you have SQL administrator permissions. For details, see the following log file: "C:\Users\tluk\AppData\Local\Temp\Create-CentralMgmtStore-sql02.domain.com_Lync2010-[2011_01_05][18_39_34].log"

Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

image

Opening up the SQL logs will show you the following errors:

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /dbexists /sqlserver:sql02.domain.com\Lync2010 /publisheracct:domain\RTCUniversalServerAdmins /replicatoracct:domain\RTCUniversalConfigReplicator /consumeracct:domain\RTCUniversalReadOnlyAdmins /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on sql02.domain.com\Lync2010
Error connecting (
name: Error
description:
number: -2147221504
message:
)
Attempting to start SQL Server and connect...
Error starting SQL Server on sql02.domain.com\Lync2010
Error (
name: Error
description:
number: -2147023840
message:
)
Ensure that sql02.domain.com\Lync2010 is a valid SQL instance.
---------------
Exit code: ERROR_START_SQLSERVICE (-1)
When running /dbexists, non-zero exit codes are not necessarily errors
---------------
Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:sql02.domain.com\Lync2010 /publisheracct:domain\RTCUniversalServerAdmins /replicatoracct:domain\RTCUniversalConfigReplicator /consumeracct:domain\RTCUniversalReadOnlyAdmins /dbpath:D:\CsData\CentralMgmtStore\Lync2010\dbpath /logpath:E:\CsData\CentralMgmtStore\Lync2010\logpath /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on sql02.domain.com\Lync2010
Error connecting (
name: Error
description:
number: -2147221504
message:
)
Attempting to start SQL Server and connect...
Error starting SQL Server on sql02.domain.com\Lync2010
Error (
name: Error
description:
number: -2147023840
message:
)
Ensure that sql02.domain.com\Lync2010 is a valid SQL instance.
---------------
Exit code: ERROR_START_SQLSERVICE (-1)
---------------

image

So here I am wondering what went wrong since this isn’t the first time I’ve installed Lync and I’ve never ran into this issue before. A quick search on the internet had people saying changing the FQDN to just the NetBIOS name fixed this issue so I gave that a go but still had the exact same failure.

Resolution

What ended up being the problem was actually the network and what tipped me off was the Event ID: 17836 error on SQL / Backend Server’s Application logs:

Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.25.1.40]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

http://social.technet.microsoft.com/Forums/en-US/ocsplanningdeployment/thread/7f178c93-50b9-4ff9-aa40-0e5dfb0fa2f5/

image

The front-end server and the backend server were actually on different subnets that traversed through quite a few routers so what I ended up doing was relocate the SQL server so that it was on the same subnet as the front-end server and the error quickly went away.  I’ll also most likely have to revisit this issue with one of our networking engineers to do some traces on both ends to determine what the root cause is.

No comments: