Lync Server 2010 Install-CsDatabase command returns the error - Failed to create database

Article translations Article translations
Article ID: 2502792 - View products that this article applies to.
Expand all | Collapse all

Symptoms

Using the Lync Sever 2010 Topology Builder Publish Topology..., Install Database... or the Install-CsDatabase -ConfigureDatabases PowerShell cmdlet to create the Lync Sever 2010 Enterprise Edition (EE) back end databases, logs error information to the following location that is similar to the information listed below:

<local drive>:\Users\Administrator.contoso\AppData\Local\Temp\2\Create-ApplicationStore-server01.contoso.com-yyyy_mm_dd][hh_mm_ss].log - log file

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\RgsConfigDbSetup.wsf" /sqlserver:server01.contoso.com /serveracct:CONTOSO\RTCComponentUniversalServices
/adminacct:CONTOSO\RTCUniversalServerAdmins /roacct:CONTOSO\RTCUniversalReadOnlyAdmins /dbpath:"C:\CsData
\ApplicationStore\(default)\dbpath" /logpath:"C:\CsData\ApplicationStore\(default)\logpath" /verbose

---------------

Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on server01.contoso.com
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 4000
SQL version is acceptable: 10.0.4000.0
Database doesn't exist.
(Database rgsconfig doesn't exist.)
Creating database rgsconfig
DbFile : PhysicalName = c:\csdata\applicationstore\(default)\dbpath\rgsconfig.mdf
LogFile: PhysicalName = c:\csdata\applicationstore\(default)\logpath\rgsconfig.ldf
Failed to create database rgsconfig
Error (name: Error description: number: -2147219701 message: )
---------------
Exit code: ERROR_CREATE_DB (-4)
---------------

Note An error similar to the one listed above can be logged while using thefollowing features of the Lync Server 2010 Deployment Wizard: Install or Update Lync Server 2010 System, deploying the Lync Server 2010 Monitoring Service or the Lync Server 2010 Archiving Service

Cause

The SQL Server Instance that is designated as the Lync Server 2010 EE SQL Server file store, the Lync Server 2010 Monitoring Server SQL Server file store, or the Lync Server 2010 Archiving Server SQL Server file store is using a non default model database initial size and auto growth configuration. 

Note The SQL Server model database is a SQL Server system database. Its purpose is to provide the SQL Server instance with a method to define SQL Server database sizing configurations. During the installation of the SQL Server instance, the model database is installed with a default minimal file size and minimal increments of unrestricted growth. The SQL Server instance database administrator can update the file size and growth properties of the model database to meet their specific requirements for database creation.

If a SQL Server instance's model database has been configured to create new SQL Server databases that are larger than the default size of any of the Lync Sever 2010 EE back end databases, the Lync Server 2010 Monitoring Server databases, or the Lync Server 2010 Archiving Server database then the Install-CsDatabase -ConfigreDatabases PowerShell cmdlet will fail and log the error that is similar to the one listed in the the Symptoms section of this article.

Listed below are the default sizes in megabytes of the Lync Sever 2010 EE back end databases, the Lync Sever 2010 Monitoring Server databases, and the Lync Sever 2010 Archiving Server database when they are created using the Install-CsDatabase -ConfiguredDatabases Lync server PowerShell cmdlet.

Note The mdf file extension represents the database data file and the ldf file extension represents the database transaction log file

rtc.mdf - size = 256 filegrowth = 256
rtc.ldf - size = 128 filegrowth = 128

rtcdyn.mdf - size = 256 filegrowth = 256
rtcdyn.ldf - size = 256 filegrowth = 256

rtcab.mdf - size = 128 filegrowth = 128
rtcab.ldf - size = 128 filegrowth = 128

rtcab1.mdf - size = 128 filegrowth = 128
rtcab1.ldf - size = 128 filegrowth = 128

rgsdyn.mdf - size = 32 filegrowth = 32
rgsdyn.mdf - size = 32 filegrowth = 16

cpsdyn.mdf - size = 32 filegrowth = 32
cpsdyn.ldf - size = 32 filegrowth = 16

rgsconfig.mdf - size = 32 filegrowth = 32
rgsconfig.ldf - size = 32 filegrowth = 16

xds.mdf - size = 8 filegrowth = 8
xds.ldf - size = 8 filegrowth = 8

lcscdr.mdf - size = 128 filegrowth = 128
lcscdr.ldf - size = 1024 filegrowth = 128

lcslog.mdf - size = 128 filegrowth = 128
lcslog.ldf - size = 1024 filegrowth = 128

qoemetrics.mdf - size = 128 filegrowth = 128
qoemetrics.ldf - size = 1024 filegrowth = 128


Note The issue that is described in the Symptoms section of this KB article can also occur during application of the cumulative updates for the Lync Server databases


Resolution

The following steps will have to be performed by a SQL Server administrator that is a member of the sysadmin SQL Server role

  1. Open the Microsoft SQL Server Management Studio console and connect to the SQL Server instance that is designated as the Lync Server 2010 EE SQL Server file store, the Lync Server 2010 Monitoring Server SQL Server file store, or the Lync Server 2010 Archiving Server SQL Server file store 
  2. Use the object viewer pane to expand the System Databases node
  3. Locate the model database and right-click on it to access its properties dialog
  4. Use the Select a Group pane to choose the File option
  5. Check if the Initial Size settings of the Logical Name object modeldev are larger than the database data file size values or the Auto Growth settings of modeldev are larger than the database data filegrowth values that are listed in the Cause section of the article
  6. Check if the Initial Size settings of the Logical Name object modellog are larger than the database transaction log file size values or the Auto Growth settings of modellog are larger than the database transaction log filegrowth values that are listed in the Cause section of the article

    If steps 5 or 6 listed above render results that show that the SQL Server instance's model database is creating databases that are larger than the default size and filegrowth values for the Lync Sever 2010 Enterprise Edition (EE) back end databases that are listed in the Cause section of this article then continue with the remaining steps in this article.
  7. Click on the Cancel button to close the Databases Properties - model dialog
  8. Use the object viewer pane of the Microsoft SQL Server Management Studio console to expand the System Databases node
  9. Right click on the model database and then choose Task, Shrink and Database from the pop-up menu
  10. Click on the OK button of the Shrink Database-model dialog to complete the operation
  11. Right click on the model database in the object viewer pane to access its properties dialog
  12. Use the Select a Group pane to choose the File option
  13. Confirm that the the Initial Size of the modeldev and modellog Logical Name objects have been shrunk to a value that is smaller than those of the database data files and database transaction log files that are listed in the Cause section of this article
  14. The SQL Server instance's modeldev and modellog database file Auto Growth values may need to be reset to their default values
  15. Click on the Auto Growth ellipse (...) button for the modeldev and modellog Logical Name objects and check Enable Auto Growth, choose the In Percent option, and set the In Percent value to the number 10
  16. Click on the OK button of the Database Properties - model dialog
Upon completing the install of the Lync Sever 2010 EE back end databases, the Lync Sever 2010 Monitoring Server databases, or the Lync Sever 2010 Archiving Server database the SQL Server instance's model database initial size and auto growth configuration can be set back to the non default values if needed.

More information

Model Database
http://technet.microsoft.com/en-us/library/ms186388.aspx
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2502792 - Last Review: July 12, 2013 - Revision: 8.2
Applies to
  • Microsoft Lync Server 2010 Enterprise Edition
Keywords: 
kbsurveynew kbtshoot kbexpertiseinter KB2502792

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com