can't execute tasks after moving .dtsx to new server

Hello.

I have two servers, A for dev and B for production.

On server A I developed a project containing a SSIS package using SQL Server business intelligence development studio. The package runs fine from the BIDS and also when I save it to SQLServer itself and run it as a scheduled job using the SQLServer Agent.

All ready to roll out to Server B I thought, so I then saved the .dtsx file to a shared network drive.

On Server B, I created a empty project with the same name as it had on Server A. I then imported the .dtsx file into the project using project > add existing item.

The package appeared to import ok but I now cannot execute any of the data flow tasks in isolation. If I right click on them, there is no option to 'execute task' as there should be, it is not greyed out, it's not there at all.

Also, if I attempt to debug the whole package I get a message saying 'This document is opened by another project'.

Can anyone help with this as my deployment to live isn't going very well to say the least!

Both server A + B are 32-bit 2005 std edition SP1 on W2003 Server std edition SP1.

Thanks.

bobbins wrote:

Hello.

I have two servers, A for dev and B for production.

On server A I developed a project containing a SSIS package using SQL Server business intelligence development studio. The package runs fine from the BIDS and also when I save it to SQLServer itself and run it as a scheduled job using the SQLServer Agent.

All ready to roll out to Server B I thought, so I then saved the .dtsx file to a shared network drive.

On Server B, I created a empty project with the same name as it had on Server A. I then imported the .dtsx file into the project using project > add existing item.

The package appeared to import ok but I now cannot execute any of the data flow tasks in isolation. If I right click on them, there is no option to 'execute task' as there should be, it is not greyed out, it's not there at all.

Also, if I attempt to debug the whole package I get a message saying 'This document is opened by another project'.

Can anyone help with this as my deployment to live isn't going very well to say the least!

Both server A + B are 32-bit 2005 std edition SP1 on W2003 Server std edition SP1.

Thanks.

The easiest way to redeploy SSIS Packages to a different server is to use the Deployment Utility: http://msdn2.microsoft.com/en-us/library/ms141190.aspx|||

Hi bobbins,

Thoughts / suggestions:

The 'document is opened by another project' error is interesting. First, make sure Business Intelligence Development Studio(BIDS) is shut down on your first server. Instead of creating a new empty project and importing the package, try copying the entire project folder to your shared drive and opening it from the BIDS on your second server. This sounds more like a file locking issue to me.

Hope this helps,

Andy

|||

Thanks for the replies.

I copied the entire project folder to the new server and it is ok. The only issue that arises is that some of the connection managers lose their login information, these are ADO.NET ODBC connections to an Ingres database, so I suspect this is just normal behaviour anyway.

Thanks again.

Can't debug Script tasks

After upgrading to CTP16 (Sept.), I can't seem to debug my script tasks. Everytime I run the package with a breakpoint in script task I get following error: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience. "

If I remove the breakpoint the scrip task runs successfully. So my question is how do I debug a script task with CTP 16?
As per my knowledge, there was no debugging support for script component.
So, you are left with few options like MessageBox.Show or rowcount etc.

Don't know if debugging support is there in sept/nov versions.

hth,
Nitesh|||No he said script task not script component and the script task does indeed support debugging.

As for the problem, do you get any error information in the error pane or progress pane. Do you get a minidump in 90\shared\ErrorDumps?

Thanks,
Matt|||Thank you for you reply Matt. No. I do not get any error info in error pane, output windows, or errordumps folder. I just get a dialog box with the error message listed above.

My Script task is set to Precompile and all the other properties are deafulted. I was under the impression that I would only get the error when there was syntax or logic problem, however, that's not true since I can take the breakpoint out and the script runs successfully.|||

If you set precompile to false then open and save the script does that make the breakpoints work or do you still get the same problem?

Thanks,
Matt

|||I have tried setting the precompile to false and it does break. However, it's not consistant. I guess CTP16 still has debugger issues hope they fix it in sql 2005 rel.