Welcome to SqlServer-QA.net Sign in | Join | Help

SQL Server Storage Engine & Tools (SSQA.net)

SQL Server Tools includes storage engine that includes a complete set of graphical tools and command prompt utilities that allow users, programmers, and administrators. SSMS, SSRS, SSIS & SSAS are most commonly used tools.
SQL 2005 Database Maintenance plan error: Value of 'DD/MM/YYYYHH:MM:SS' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'

Here is another common error you will get to see with Database Maintenance plan in SQL Server 2005, though most of it has been resolved with Service Pack 2 and hotfix but still you need to take care few things.

Error: Value of 'DD/MM/YYYYHH:MM:SS' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate' Parameter name: Value (System.Windows.Forms)

Initially this was reported to the connect site for a bug fix for a tracking. The actual problem of this casewas that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. By default as per the plan if no action is taken, on the day after the original expiration date for that backup set then "backup set will expire" option will be reset to a date that is 14 days from the current date and the task will be editable as usual. In order to change this you have to edit the relevant maintenance plan task, it may be easy if you have recreated this package afresh. But in case of imported/migrated from previous version of SQL Server then the editing the task is required on the day it was set to expire, then one of the following two solutions can be used:

Solution A: The new task can be created in place of the existing task.

Solution B: The Backup Database task can be made editable by changing the “Backup set will expire” property in BIDS and importing the package back to the Maintenance Plan designer.

Edit your Maintenance Plan in the Server Business Intelligence Development Studio (BIDS)

·         Find SQL Server Business Intelligence Development Studio on the Start menu under Microsoft SQL Server 2005.

·         From the File menu, create a New Project of type “Integration Services Project”.

·         To import your Maintenance Plan into your new project, in the Solution Explorer window, right click on the ‘SSIS Packages’ folder and choose the ‘Add Existing Package’ option.

·         In the “Add Copy of Existing Package” dialog

o   Set the Package Location to SQL Server

o   Provide authentication for your server.

o   In the Package Path field , click the browse button to display the packages on your server.

o   Navigate to ‘SSIS Package’, then ‘Maintenance Plans’.

o   Select your Maintenance Plan and click OK. You see the Maintenance Plan that you just imported under the ‘SSIS Packages’ folder.

·         Right-Click the Backup Database Task and select Properties.

·         In the list of properties, navigate to the “ExpireDate” option and change the date to be at least one day ahead of the current date.

·         Save the Package.

·         In the Solution Explorer window, click on the name of the package. In the Properties panel, locate the Full Path to the package’s .dtsx file. Select the path and copy it to the clipboard.

·         Exit the Business Intelligence Development Studio.

Re-import the Edited Package

·         In Management Studio, click the Connect button and choose “Integration Services…” and connect to your server.

·         Under Stored Packages open “MSDB”.

·         Right click on the “Maintenance Plans” folder and select “Import Package”.

o   Select “File System”.

o   In the Package Path text box, paste in the previously copied .dtsx file path.

o   Click in the Package Name text box to set the name, and click OK.

·         When prompted to overwrite the existing package, say “Yes”.

 

Given these updates, the Backup Database Task should be editable from the Maintenance Plan designer.

Posted: Sunday, September 09, 2007 1:52 AM by SQL Master

Comments

Other SQL Server Blogs around the Web said:

Here is another common error you will get to see with Database Maintenance plan in SQL Server 2005, though

# September 10, 2007 8:09 AM

SSQA.net - SqlServer-QA.net said:

Here is another common error you will get to see with Database Maintenance plan in SQL Server 2005, though

# September 10, 2007 8:21 AM
Anonymous comments are disabled