When configuring a newly installed Provisioning Services with a pre-created SQL database, errors during the configuration process and the ConfigWizard.log file contains entries similar to the following:

2010-11-09 10:33:10,337 [1] ERROR Mapi.CommandProcessor - Exception of type System.Data.SqlClient.SqlException caught, error=MODIFY FILE failed. Specified size is less than or equal to current size.
MODIFY FILE failed. Specified size is less than or equal to current size.
2010-11-09 10:33:10,337 [1] DEBUG Mapi.CommandProcessor - CreateFarm-leave
2010-11-09 10:33:10,352 [1] ERROR ConfigWizard - Creating Farm in Empty Database...FAILED.
2010-11-09 10:33:10,352 [1] ERROR ConfigWizard - A database error occurred.
2010-11-09 10:33:10,352 [1] ERROR ConfigWizard -   MODIFY FILE failed. Specified size is less than or equal to current size.
2010-11-09 10:33:10,352 [1] ERROR ConfigWizard - MODIFY FILE failed. Specified size is less than or equal to current size.

As a workaround, there are four options to resolve this issue.

Option-1

• dbcreator -  required for creating the database

• securityadmin -  required for creating the SQL logins for the stream and soap services

If the user does not have sufficient SQL privileges, a dialog prompts for a SQL Server user that has the appropriate permissions (dbcreator and securityadmin).

Option-2

Run DbScript.exe on the Provisioning Services server and use the output SQL script to create the database. The SQL script creates a 20-megabyte database, though the script can be manually edited to modify the size parameters.

DbScript.exe is located at C:\Program Files\Citrix\Provisioning Services.

When the database script is run, run the Configuration Wizard with a user account configured as the owner of the database with the View any definition permission (these settings are set by the database administrator when the empty database is created) and join the Provisioning Services server to the farm.
 

Option-3

1. Manually create the database and assign an initial size of 19-megabytes or smaller.

2. Run the Configuration Wizard with a user account configured as the owner of the database with the View any definition permission (these settings are set by the database administrator when the empty database is created).

Option-4

1. Create the database manually with the organization’s preferred size and parameters.

2. Run DbScript.exe on the Provisioning Services server.

3. Edit the output SQL script using a text editor and comment out all of the lines of commands above the following comment:

    /**** Only manually edit lines above this point and the last few lines, the rest is generated from the Design database ****/

4. Execute the script on the database created in step 1.

5. Run the Configuration Wizard with a user account configured as the owner of the database with the View any definition permission (these settings are set by the database administrator when the empty database is created) and join the Provisioning Services server to the farm.

Problem Cause

The Configuration Wizard tries to modify the pre-existing SQL database and specifies a file size that is smaller than the initial size of the database.