Lync Server 2013 Publish Topology process fails with the error: “InstallDatabaseInternalFailure: An internal error has occurred while trying to create or update the database.”

Problem

You attempt to publish a new enterprise pool from Topology Builder but notice that it fails with the following:

Creating Database SQL-Server-FQDNInstance…

Completed with errors

Reviewing the logs show the following errors:

InstallDatabaseInternalFailure: An internal error has occurred while trying to create or update the database.

Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
▼ Details

└ Type: SqlException
└ ▼ Stack Trace

└     at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)

└ ▼ Additional Details

└     Error: The wait operation timed out
▼ Details

└ Type: Win32Exception
└ ▼ Stack Trace

└

Further reviewing the Create-BackendStore-… log in the folder:

C:Userstluk-adminAppDataLocalTemp2

Creating database rtcxds from scratch. Data File Path = C:CsDataBackendStore(default)DbPath, Log File Path= C:CsDataBackendStore(default)DbPath…
Clean installing database rtcxds.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Solution

Since Lync Server 2013 has just recently RTM-ed, there wasn’t a whole lot of resources other than this forum post:

http://social.technet.microsoft.com/Forums/en-US/lyncserverpreview/thread/90343e69-9f43-4f11-8763-b60c12ba0c21

Unfortunately, my issue wasn’t because SQL Agent wasn’t started nor was it disk space.  What my issue ended up to be was a transient issue.  The time I was publishing the topology also had a weekend backup job going on so I had intermittent issues with slow network speeds across servers.  I’m sure that not many people would run into the same issue as me but I think what’s important to know is to not let this error throw you off thinking that there is something wrong with your Lync topology.  Proceed with ensuring that network connectivity is in good health then try to deploy the pool again because the topology published properly on the second try.