Lync Server 2010 and Advanced Database Option in Publishing Topology

I ran into an interesting scenario today when creating and publishing a new Topology. What was happening is that during the creation of the databases, I was seeing an error that appears in the log file here:

Running script: C:\Windows\system32\cscript.exe //Nologo “C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\DbSetup.wsf”  /dbexists  /sqlserver:SqlServerName.DomainName.com  /serveracct:DomainName\RTCHSUniversalServices  /adminacct:DomainName\RTCUniversalServerAdmins /roacct:DomainName\RTCUniversalReadOnlyAdmins /role:se /verbose

—————

Installed SQL Server 2005 Backward Compatibility version is 8.05.2312

Connecting to SQL Server on SQLServerName.DomainName.com

SqlMajorVersion : 10

SqlMinorVersion : 50

SqlBuildNo : 1600

SQL version is acceptable: 10.50.1600.1

Default database data file path is I:\Data

Default database log file path is L:\Tlogs

Database does not exist.

—————

Exit code: ERROR_NO_DATABASE_EXISTS (-23)

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\DbSetup.wsf” /sqlserver:SQLServerName.DomainName.com /serveracct:DomainName\RTCHSUniversalServices  /adminacct:DomainName\RTCUniversalServerAdmins /roacct:DomainName\RTCUniversalReadOnlyAdmins  /dbpath:”E:\CsData\BackendStore\(default)\dbpath” /logpath:”T:\CsData\BackendStore\(default)\logpath” /dyndbpath:”E:\CsData\BackendStore\(default)\dyndbpath” /dynlogpath:”I:\CsData\BackendStore\(default)\dynlogpath” /role:se /verbose

—————

Installed SQL Server 2005 Backward Compatibility version is 8.05.2312

Connecting to SQL Server on SQLServerName.DomainName.com

SqlMajorVersion : 10

SqlMinorVersion : 50

SqlBuildNo : 1600

SQL version is acceptable: 10.50.1600.1

Unable to access data drive as represented by \\SQLServerName.DomainName.com\E$\CsData\BackendStore\(default)\dbpath

—————

Exit code: ERROR_NO_DB_DRIVE_ACCESS (-42)

—————

The interesting part is that the script was trying to write to the E: for some reason. It clearly found that the data drive is the I: and that the transaction logs use the T: on the SQL server. 

What it came down to is that the SQL server is actually a SQL server cluster, and the E: is a local drive on the server. This started to make sense once I thought more about it. The Publish process uses the “Automatically determine the file location” option as the default and it can be seen by clicking on the Advanced button. The Publish process was looking at the SQL server and using the drives that its algorithm considered to be the best drives for optimal performance and didn’t understand that some drives are not actually available as they are local drives and not clustered drives. So, basically, the Publish process was ignoring the SQL default drives for the database and log files and was using its own decision making process to choose a drive.

Resolution?

Well, it was easy enough to fix by using the Advanced button and selecting the option for the SQL server that uses the default drives for the SQL installation.

Advertisements
This entry was posted in Office Communications Server. Bookmark the permalink.

5 Responses to Lync Server 2010 and Advanced Database Option in Publishing Topology

  1. UCCLYNC1991 says:

    Only two hits in Google, yours addressing the problem I had. Thanks for posting, it saved me troubleshooting time.

  2. Yongrak says:

    I had the same problem. thanks for your advise.
    wow, I do publish topoloby again. It works ! awesome..

  3. Had the same problem, but was not fixed by selecting the other option.
    Am now on my way, at least have this error fixed.
    FQDN I was using was pinging to my internal IP, not to localhost, which made the path it was looking for unreachable.

    Solvation: Check the paths that are used in the error file and check whether you can reach them via Explorer.

  4. Zeeshan says:

    Thanks alot brother it was really painfull for me to get rid of this error

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s