Cannot show the editor for this task. Specified cast is not valid

This error is pretty persistent. I re-installed VS 2005 and SQL Server 2005 but did not help. Every time I try to open a Script Task editor it gives me the same error regardless of the project or package. DO I NEED TO REBUILD MY SYSTEM ?

===================================

Cannot show the editor for this task. (Microsoft Visual Studio)

===================================

Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaIDE.get_ExtensibilityObject()
at Microsoft.SqlServer.VSAHosting.DesignTime.get_ExtensibilityObject()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskUI.Dispose()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskMainWnd.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Microsoft.DataTransformationServices.Design.DtrPackageDesigner.DoDefaultActionForTask(TaskHost task)

-

Any help is appreciated.

Gulden

.......

have you tried re-installing ssis?|||

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

|||

Last couple of days I have been re-installing VS 2005 and SQL Server 2005 from scratch. This is related to a system or temp file which was created by SSIS which does not go away when these apps uninstalled.

Would anybody know if I should go ahead and rebuild my system or are there any specific files or registry items involved that I should search for?

|||

When editing scripts, VB for applications flashes for a split second and goes away. When I am running the packages on the Debug mode, I get "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for inconvenience" right away. And does not iterate through any script after that. I wonder if I have too many script tasks in the package (about 90)

Something has seriously been corrupted concerning the Script editing that no installation can fix. It is so unexplainable to me.

Any advice ?

|||

Mistery solved!

Apparently they pushed a Macromedia package to hundreds of people's computers in my workplace re-registering at least 20 dlls including vbscript.dll.

|||I am still experiencing this problem and none of the suggestions seem to work. Any help would be appreciated.|||Did you get this problem resolved?

I have the same problem on a production package that I need to run once a week. Any help is appreciated.

Pade|||

I face the same error. It was working fine - until suddenly i started getting this message "Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)"

and it doesn't go away neither the script editor opens.

Anyone who has solved this issue ?

Thanks

Cannot show the editor for this task. Specified cast is not valid

This error is pretty persistent. I re-installed VS 2005 and SQL Server 2005 but did not help. Every time I try to open a Script Task editor it gives me the same error regardless of the project or package. DO I NEED TO REBUILD MY SYSTEM ?

===================================

Cannot show the editor for this task. (Microsoft Visual Studio)

===================================

Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaIDE.get_ExtensibilityObject()
at Microsoft.SqlServer.VSAHosting.DesignTime.get_ExtensibilityObject()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskUI.Dispose()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskMainWnd.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Microsoft.DataTransformationServices.Design.DtrPackageDesigner.DoDefaultActionForTask(TaskHost task)

-

Any help is appreciated.

Gulden

.......

have you tried re-installing ssis?|||

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

|||

Last couple of days I have been re-installing VS 2005 and SQL Server 2005 from scratch. This is related to a system or temp file which was created by SSIS which does not go away when these apps uninstalled.

Would anybody know if I should go ahead and rebuild my system or are there any specific files or registry items involved that I should search for?

|||

When editing scripts, VB for applications flashes for a split second and goes away. When I am running the packages on the Debug mode, I get "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for inconvenience" right away. And does not iterate through any script after that. I wonder if I have too many script tasks in the package (about 90)

Something has seriously been corrupted concerning the Script editing that no installation can fix. It is so unexplainable to me.

Any advice ?

|||

Mistery solved!

Apparently they pushed a Macromedia package to hundreds of people's computers in my workplace re-registering at least 20 dlls including vbscript.dll.

|||I am still experiencing this problem and none of the suggestions seem to work. Any help would be appreciated.|||Did you get this problem resolved?

I have the same problem on a production package that I need to run once a week. Any help is appreciated.

Pade|||

I face the same error. It was working fine - until suddenly i started getting this message "Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)"

and it doesn't go away neither the script editor opens.

Anyone who has solved this issue ?

Thanks

Cannot show the editor for this task. Specified cast is not valid

This error is pretty persistent. I re-installed VS 2005 and SQL Server 2005 but did not help. Every time I try to open a Script Task editor it gives me the same error regardless of the project or package. DO I NEED TO REBUILD MY SYSTEM ?

===================================

Cannot show the editor for this task. (Microsoft Visual Studio)

===================================

Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaIDE.get_ExtensibilityObject()
at Microsoft.SqlServer.VSAHosting.DesignTime.get_ExtensibilityObject()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskUI.Dispose()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskMainWnd.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Microsoft.DataTransformationServices.Design.DtrPackageDesigner.DoDefaultActionForTask(TaskHost task)

-

Any help is appreciated.

Gulden

.......

have you tried re-installing ssis?|||

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

|||

Last couple of days I have been re-installing VS 2005 and SQL Server 2005 from scratch. This is related to a system or temp file which was created by SSIS which does not go away when these apps uninstalled.

Would anybody know if I should go ahead and rebuild my system or are there any specific files or registry items involved that I should search for?

|||

When editing scripts, VB for applications flashes for a split second and goes away. When I am running the packages on the Debug mode, I get "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for inconvenience" right away. And does not iterate through any script after that. I wonder if I have too many script tasks in the package (about 90)

Something has seriously been corrupted concerning the Script editing that no installation can fix. It is so unexplainable to me.

Any advice ?

|||

Mistery solved!

Apparently they pushed a Macromedia package to hundreds of people's computers in my workplace re-registering at least 20 dlls including vbscript.dll.

|||I am still experiencing this problem and none of the suggestions seem to work. Any help would be appreciated.|||Did you get this problem resolved?

I have the same problem on a production package that I need to run once a week. Any help is appreciated.

Pade
|||

I face the same error. It was working fine - until suddenly i started getting this message "Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)"

and it doesn't go away neither the script editor opens.

Anyone who has solved this issue ?

Thanks

Cannot show the editor for this task. Specified cast is not valid

This error is pretty persistent. I re-installed VS 2005 and SQL Server 2005 but did not help. Every time I try to open a Script Task editor it gives me the same error regardless of the project or package. DO I NEED TO REBUILD MY SYSTEM ?

===================================

Cannot show the editor for this task. (Microsoft Visual Studio)

===================================

Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaIDE.get_ExtensibilityObject()
at Microsoft.SqlServer.VSAHosting.DesignTime.get_ExtensibilityObject()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskUI.Dispose()
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTaskMainWnd.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Microsoft.DataTransformationServices.Design.DtrPackageDesigner.DoDefaultActionForTask(TaskHost task)

-

Any help is appreciated.

Gulden

.......

have you tried re-installing ssis?|||

I've re-installed SQL Server 2005 and Visual Studio 2005. Still cannot open the scripts.

|||

Last couple of days I have been re-installing VS 2005 and SQL Server 2005 from scratch. This is related to a system or temp file which was created by SSIS which does not go away when these apps uninstalled.

Would anybody know if I should go ahead and rebuild my system or are there any specific files or registry items involved that I should search for?

|||

When editing scripts, VB for applications flashes for a split second and goes away. When I am running the packages on the Debug mode, I get "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for inconvenience" right away. And does not iterate through any script after that. I wonder if I have too many script tasks in the package (about 90)

Something has seriously been corrupted concerning the Script editing that no installation can fix. It is so unexplainable to me.

Any advice ?

|||

Mistery solved!

Apparently they pushed a Macromedia package to hundreds of people's computers in my workplace re-registering at least 20 dlls including vbscript.dll.

|||I am still experiencing this problem and none of the suggestions seem to work. Any help would be appreciated.|||Did you get this problem resolved?

I have the same problem on a production package that I need to run once a week. Any help is appreciated.

Pade|||

I face the same error. It was working fine - until suddenly i started getting this message "Specified cast is not valid. (Microsoft.VisualBasic.Vsa.DT)"

and it doesn't go away neither the script editor opens.

Anyone who has solved this issue ?

Thanks

Cannot show editor for this task in SQL 2005 Management Studio

Hi,

I have setup a db backup maintenance plan with the SQL 2005 Mgmt Studio tool. When I double-clicked the 'Back up Database Task' object I got the following error message. My SQL 2005 client has been patched with SQL 2005 SP2. Does someone know about this problem? Thanks - Joe

Cannot show editor for this task.

Additional information:

Value of '4/17/2007 12:00:00 AM' is not valid for Value'. Value should be between 'MinDate' and 'MaxDate'. Parameter name: Value(System.Windows.Forms)

I haven't heard of this one before. Please file a defect report for this issue at http://connect.microsoft.com/sqlserver. Issues reported on the Connect site go directly into our internal issue tracking system so we don't lose any information. Be sure to note whether the maintenance plan existed before your updated to SP2 or if the plan is new.

Thanks,

Steve

|||I'm getting this as well. Did you get an idea when this might be fixed.|||I'm getting this also. Did you get an idea when this might be fixed.|||

hello I have got the same problem, but in spanish.

The mantenience plan was created before updating to SP2, and now I can't edit the BackUp task.

I tryed diferent MSSMS Clients with the same server, and it always fails, so I assume this is from the server.

Error: (spanish)

No se puede mostrar el editor para esta tarea.

Información adicional:

El valor de '02/05/2007 0:00:00' no es válido para 'Value'. 'Value' debería estar entre 'MinDate' y 'MaxDate'.

Nombre del parámetro: Value (System.Windows.Forms)

|||

Strangely on my side, the day after having this error, everything was ok.

Did not apply any new service pack or correction att all.

Carl

|||

Solved same way, yesterday I created again one of the tasks, and today I can edit all them.

Summary: Solution, wait until tomorrow.

|||

Hello everyone,

Thanks for reporting this issue. The problem is that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. While a solution is being worked out and will be available in a major release, a few work-arounds have been identified:

1. If no action is taken, on the day after the original expiration date, the "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.

2. If 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. Here are the steps to follow:

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.

Sorry for the inconvenience.

-Sirish

Cannot show editor for this task in SQL 2005 Management Studio

Hi,

I have setup a db backup maintenance plan with the SQL 2005 Mgmt Studio tool. When I double-clicked the 'Back up Database Task' object I got the following error message. My SQL 2005 client has been patched with SQL 2005 SP2. Does someone know about this problem? Thanks - Joe

Cannot show editor for this task.

Additional information:

Value of '4/17/2007 12:00:00 AM' is not valid for Value'. Value should be between 'MinDate' and 'MaxDate'. Parameter name: Value(System.Windows.Forms)

I haven't heard of this one before. Please file a defect report for this issue at http://connect.microsoft.com/sqlserver. Issues reported on the Connect site go directly into our internal issue tracking system so we don't lose any information. Be sure to note whether the maintenance plan existed before your updated to SP2 or if the plan is new.

Thanks,

Steve

|||I'm getting this as well. Did you get an idea when this might be fixed.|||I'm getting this also. Did you get an idea when this might be fixed.|||

hello I have got the same problem, but in spanish.

The mantenience plan was created before updating to SP2, and now I can't edit the BackUp task.

I tryed diferent MSSMS Clients with the same server, and it always fails, so I assume this is from the server.

Error: (spanish)

No se puede mostrar el editor para esta tarea.

Información adicional:

El valor de '02/05/2007 0:00:00' no es válido para 'Value'. 'Value' debería estar entre 'MinDate' y 'MaxDate'.

Nombre del parámetro: Value (System.Windows.Forms)

|||

Strangely on my side, the day after having this error, everything was ok.

Did not apply any new service pack or correction att all.

Carl

|||

Solved same way, yesterday I created again one of the tasks, and today I can edit all them.

Summary: Solution, wait until tomorrow.

|||

Hello everyone,

Thanks for reporting this issue. The problem is that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. While a solution is being worked out and will be available in a major release, a few work-arounds have been identified:

1. If no action is taken, on the day after the original expiration date, the "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.

2. If 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. Here are the steps to follow:

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.

Sorry for the inconvenience.

-Sirish

Cannot show editor for this task in SQL 2005 Management Studio

Hi,

I have setup a db backup maintenance plan with the SQL 2005 Mgmt Studio tool. When I double-clicked the 'Back up Database Task' object I got the following error message. My SQL 2005 client has been patched with SQL 2005 SP2. Does someone know about this problem? Thanks - Joe

Cannot show editor for this task.

Additional information:

Value of '4/17/2007 12:00:00 AM' is not valid for Value'. Value should be between 'MinDate' and 'MaxDate'. Parameter name: Value(System.Windows.Forms)

I haven't heard of this one before. Please file a defect report for this issue at http://connect.microsoft.com/sqlserver. Issues reported on the Connect site go directly into our internal issue tracking system so we don't lose any information. Be sure to note whether the maintenance plan existed before your updated to SP2 or if the plan is new.

Thanks,

Steve

|||I'm getting this as well. Did you get an idea when this might be fixed.|||I'm getting this also. Did you get an idea when this might be fixed.|||

hello I have got the same problem, but in spanish.

The mantenience plan was created before updating to SP2, and now I can't edit the BackUp task.

I tryed diferent MSSMS Clients with the same server, and it always fails, so I assume this is from the server.

Error: (spanish)

No se puede mostrar el editor para esta tarea.

Información adicional:

El valor de '02/05/2007 0:00:00' no es válido para 'Value'. 'Value' debería estar entre 'MinDate' y 'MaxDate'.

Nombre del parámetro: Value (System.Windows.Forms)

|||

Strangely on my side, the day after having this error, everything was ok.

Did not apply any new service pack or correction att all.

Carl

|||

Solved same way, yesterday I created again one of the tasks, and today I can edit all them.

Summary: Solution, wait until tomorrow.

|||

Hello everyone,

Thanks for reporting this issue. The problem is that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. While a solution is being worked out and will be available in a major release, a few work-arounds have been identified:

1. If no action is taken, on the day after the original expiration date, the "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.

2. If 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. Here are the steps to follow:

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.

Sorry for the inconvenience.

-Sirish

|||

You can select the backup mainplan in the designer and press F4 to open the properties of the maintenanceplan in the designer.In the properties you can change the expiry date, this allows you to open the plan again for edit.