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 delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Ideletethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?|||Try to restore over it with any old database backup and use overwrite
database while restoring.
Make sure you no longer need this database before performing above step.
Manu Jaidka
"togbabe" wrote:
> On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> > Hoping someone can help me with this. I have a SQL 2005 box which was
> > formerly in a '2005mirror.' The SQL server containing the
> > 'principal' is now dead (ceased to exist). That is not the problem.
> > The problem is that I now want todeletethemirroras it is no longer
> > needed. The status of themirroris 'Disconnected / In Recovery.'
> > Problem is that when I try todeleteit, I get the message "Database x
> > is enabled for Database Mirroring, Database Mirroring must be removed
> > before dropping the database. (Microsoft SQL Server, Error: 3743).
> > O.K., this is another fine mess you've gotten me into Olly.... Ho do Ideletethe 'mirroring relationship' if the server containing the
> > Principal has 'gone to a better life?' Until I work out how, I will
> > have to just ignore it and continue to put he server into production.
> > Not a great option. Thanks in advance.
> Here is what I have done with this. I know it is not nice but it has
> partially worked. I simply stopped SQL server, renamed the mdf file
> and restarted the server. This has worked. I actually thought I
> would have to still delete the artifact of the database in a 'suspect
> state.' But I didn't even have to do this. It was just gone. One
> problem - though - the event log still contains an error "FCB::Open
> failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
> for file number 1. OS error: 2(error not found)." Anybody have any
> ideas of how I can get rid of this?
>

Can't delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.
On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Ideletethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?
|||Try to restore over it with any old database backup and use overwrite
database while restoring.
Make sure you no longer need this database before performing above step.
Manu Jaidka
"togbabe" wrote:

> On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Here is what I have done with this. I know it is not nice but it has
> partially worked. I simply stopped SQL server, renamed the mdf file
> and restarted the server. This has worked. I actually thought I
> would have to still delete the artifact of the database in a 'suspect
> state.' But I didn't even have to do this. It was just gone. One
> problem - though - the event log still contains an error "FCB::Open
> failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
> for file number 1. OS error: 2(error not found)." Anybody have any
> ideas of how I can get rid of this?
>

Can't delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Idel
etethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?

Can't connect ODBC/SQLSrvr linked table from within COM+ component

I have an Access 2000 database containing an ODBC table linked to a SQL Serv
er 2000 database (using a system DSN).
No problem opening the table Using Access 2000 itself.
No problem even within a VB program (EXE) accessing that table using the fol
lowing code:
Set rs = New ADODB.Recordset
With rs
.ActiveConnection = cnSrc
.Source = "SELECT * FROM " _
& "[ODBC;" & tbODBC.Properties("Jet OLEDB:Link Provider String") & "]."
_
& tbODBC.Name & vbCrLf & "WHERE FALSE"
.CursorLocation = adUseServer
End With
On Error Resume Next
rs.Open ' <-- ERROR RAISES HERE
cnSrc is an ADO Connection with Access2000 DB
tbODBC is an ADOX Table object corresponding to the linked ODBC table
But if the same code is placed in a COM+ component (DLL ActiveX), once invok
ed by any client, when the final "rs.Open" is executed, the following error
raises:
"Connection to <sql server database name> failed"
Number = 0x80004005
SQLState = 3151
I've searched many places but with no results.
Some help will be appreciated.
Thanks in advance
RafThe Jet OLEDB provider does not support distributed transactions since it
does not implement the ITransactionJoin OLE-DB interface.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Raf" <anonymous@.discussions.microsoft.com> wrote in message
news:0377EFF9-6D50-447F-B38F-779100742A52@.microsoft.com...
>I have an Access 2000 database containing an ODBC table linked to a SQL
>Server 2000 database (using a system DSN).
> No problem opening the table Using Access 2000 itself.
> No problem even within a VB program (EXE) accessing that table using the
> following code:
> Set rs = New ADODB.Recordset
> With rs
> .ActiveConnection = cnSrc
> .Source = "SELECT * FROM " _
> & "[ODBC;" & tbODBC.Properties("Jet OLEDB:Link Prov
ider
> String") & "]." _
> & tbODBC.Name & vbCrLf & "WHERE FALSE"
> .CursorLocation = adUseServer
> End With
> On Error Resume Next
> rs.Open ' <-- ERROR RAISES HERE
> cnSrc is an ADO Connection with Access2000 DB
> tbODBC is an ADOX Table object corresponding to the linked ODBC table
> But if the same code is placed in a COM+ component (DLL ActiveX), once
> invoked by any client, when the final "rs.Open" is executed, the following
> error raises:
> "Connection to <sql server database name> failed"
> Number = 0x80004005
> SQLState = 3151
> I've searched many places but with no results.
> Some help will be appreciated.
> Thanks in advance
> Raf
>