SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS - Database Transfer Wizard - @flags parameters is not valid


SSIS - Database Transfer Wizard - @flags parameters is not valid

Author
Message
nickm_GR
nickm_GR
SSChasing Mays
SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)

Group: General Forum Members
Points: 631 Visits: 233
I'm trying to use copy database wizard to make a copy of a SQL Server 2005 database (9.0.3042) on a SQL Server 2012 machine (11.0.2100). I'm using the "SQL Management Object method" so that the orginal database can remain online. When I get to the final step I recieve the following error:

- Start SQL Server Agent Job (Error)
Messages
* Create failed for JobStep 'CDW_KC4DATABASE_KCCDB_0_Step'. (Copy Database Wizard)
The @flags parameter is not valid for a job step of type 'SSIS'. (Microsoft SQL Server, Error: 14545)

I can't seem to find anything on the internet regarding "@flags parameter is not valid". Of course the two links provided in the error log that go to microsoft's site are totally useless. The full error message follows:

Performing operation

- Add log for package (Success)

- Add task for transferring database objects (Success)

- Create package (Success)

- Start SQL Server Agent Job (Error)
Messages
* Create failed for JobStep 'CDW_KC4DATABASE_KCCDB_0_Step'. (Copy Database Wizard)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.2500.0+((KJ_PCU_Main).110617-0038+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

The @flags parameter is not valid for a job step of type 'SSIS'. (Microsoft SQL Server, Error: 14545)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=14545&LinkId=20476


- Execute SQL Server Agent Job (Stopped)


Anyone have any insight?
Thanks!
Query Shepherd
Query Shepherd
Mr or Mrs. 500
Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)Mr or Mrs. 500 (536 reputation)

Group: General Forum Members
Points: 536 Visits: 454
Did you choose "detach/attach" or SMO? Couldn't you just schedule the package, or does the error come up during package creation?

Greetz
Query Shepherd
nickm_GR
nickm_GR
SSChasing Mays
SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)

Group: General Forum Members
Points: 631 Visits: 233
SMO; I want to allow the database to remain online.

I can't finish the wizard to actually create the package; I get the error on the last step.
Thanks
Nick
Joe Snyder
Joe Snyder
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 9
Just ran into this issue. I was using SSMS on my local machine, which has 2008R2, but the SQL Server itself is 2012. I logged into the server (RDP) and launched SSMS and followed the same steps; everything worked fine.
nickm_GR
nickm_GR
SSChasing Mays
SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)

Group: General Forum Members
Points: 631 Visits: 233
Joe, thanks for that insight. I bet that's what going on. I have both SMO 2008 R2 and SMO 2012 installed on my workstation. I can't remember exactly which one I was using, but I wouldn't be surprised if I was using the old one to try to manage a 2012 instance.

Maybe there should be a warning when you try to connect that says:
"hey dummy, do you know that you're trying to manage a 2012 instance with 2008 software? There will be problems".
;-)

I just ended up taking it offline; but maybe this post will help someone in the future. Thanks for leaving the reply!
kpwaran
kpwaran
SSC Journeyman
SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)

Group: General Forum Members
Points: 77 Visits: 85
I am getting "The destination must be a SQL Server 2005 instance" when I do Copy Database through Copy Database Wizard.(RDP and launched SSMS in the source server)

Source Server: Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86) (SP2) Enterprise Edition
Destination Server: Microsoft SQL Server 2012 (SP1) Enterprise Edition (64-bit)

Please help.

Thanks
nickm_GR
nickm_GR
SSChasing Mays
SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)

Group: General Forum Members
Points: 631 Visits: 233
Did you try it from the destination server? As mentioned above, this is probably related to using older management server software to perform the copy. Try it from the 2012 server, it seems logical that the 2012 management software should be backwards compatible with copying data from 2005; but 2005 might not be able to copy data to a 2012 instance.
Please post back if you find a solution; so far we're working in speculation only.
mishra.pk.bikram
mishra.pk.bikram
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 1
Hi,

I had also the same problem and its solved magically.

I simply closed all my instances of SSMS and Run the Copy database wizard once again.
The package created successfully, Job created successfully and job executed successfully.

Thanks
Bikram
neilryder
neilryder
SSC-Enthusiastic
SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)SSC-Enthusiastic (123 reputation)

Group: General Forum Members
Points: 123 Visits: 22
I am having the same / similar problem:

Trying to use copy database wizard to move a database from an SQL 2008 R2 installation on server 2008 R2 to an SQL 2014 installation on a server 2012 machine. I'm using Win authentication on the source machine (where the Copy database command is running) and SQL authentication with the sa login for the destination server.

Can anyone help?
nickm_GR
nickm_GR
SSChasing Mays
SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)SSChasing Mays (631 reputation)

Group: General Forum Members
Points: 631 Visits: 233
Make sure you're using SSMS from the 2014 install.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search