Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS - Database Transfer Wizard - @flags parameters is not valid Expand / Collapse
Author
Message
Posted Monday, February 4, 2013 1:43 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 11:47 AM
Points: 297, Visits: 193
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!
Post #1415483
Posted Thursday, February 7, 2013 7:20 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, June 28, 2014 2:49 PM
Points: 116, Visits: 346
Did you choose "detach/attach" or SMO? Couldn't you just schedule the package, or does the error come up during package creation?

Greetz
SQL Pizza



sometimes you dont see the pizza for the toppings...
seek and ya shall find...
Post #1417058
Posted Thursday, February 7, 2013 7:24 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 11:47 AM
Points: 297, Visits: 193
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
Post #1417062
Posted Friday, April 5, 2013 9:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 2:12 PM
Points: 1, 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.
Post #1439321
Posted Monday, April 8, 2013 6:25 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 11:47 AM
Points: 297, Visits: 193
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!
Post #1439783
Posted Tuesday, January 7, 2014 2:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 7, 2014 4:37 PM
Points: 1, Visits: 8
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
Post #1528675
Posted Tuesday, January 21, 2014 6:33 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 11:47 AM
Points: 297, Visits: 193
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.
Post #1533019
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse