|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Yesterday @ 7:53 AM
Points: 170,
Visits: 151
|
|
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!
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:14 AM
Points: 116,
Visits: 293
|
|
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...
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Yesterday @ 7:53 AM
Points: 170,
Visits: 151
|
|
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
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Saturday, April 20, 2013 2:48 PM
Points: 1,
Visits: 8
|
|
| 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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Yesterday @ 7:53 AM
Points: 170,
Visits: 151
|
|
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!
|
|
|
|