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.

Cant Connect to remote server, my app works in local only??

Hello,
i've developed a website using VB.NET, and SQL SERVER 2K, in my dev environment works properly (SQL Server and WEB SERVER are in the same machine).
When i put everything in the target machine, where the webserver is but not the sql, i get the following error:
Sql SErver does not exist or access denied

I've tried so many ways to do this, ODBC, ADO.NET, OLEDB....and everything ends in the same error.
Also if i try to connect with ODBC (from odbc manager) it seems to work (test connection succesfull), but in asp.net nothing works.
I've tried to access the server with:
INSTANCE_NAME
\SERVER_NAME\INSTANCE_NAME
IP,PORT

I think (they are checking this), that the auth mode is set to MIXED MODE.

Any idea to save my life?? ;)

Thanks pplYour reference to the server in your ADO connection string should be:

ipaddressofserver\instancename (i.e., 206.152.125.6\instance1 )

If you are using SQL Authenticiation, which you should, then you need to reference the {uid} and {password} properties.
I would be willing to bet that your SQL Installation is set the Mixed Mode.

HTH