I execute my package to transfer a full database SQL 2000 to SQL 2005, and the transfer fails with this error:TITLE: Microsoft.SqlServer.DtsTransferProvider------------------------------ ERROR : errorCode=-1071636471 description=An OLE DB error has occurred. Error code: 0x80004005.An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Arithmetic overflow error converting numeric to data type numeric.". helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}The question is: how can I trace back the interface id of the package that failed, to a meaningful name? Is there a way? How do I get an exact description of the object, I mean the field or stored procedure that failed?I had to copy the full database files over and re-attach the database at the target server, because I could not find any way to move the data.Please help.philip_38@hotmail.com

Federico Alves wrote: The question is: how can I trace back the interface id of the package that failed, to a meaningful name? Is there a way? How do I get an exact description of the object, I mean the field or stored procedure that failed?You can "save the import/export" as an SSIS package.If you then open that SSIS package in BIDS, you might be able to see "warnings" for conversion problems.HTH,Nitesh

I ran into this same error message: [Transfer SQL Server Objects Task] Error: Execution failed with the following error: "ERROR : errorCode=-1071636471 description=An OLE DB error has occurred. Error code: 0x80040E37. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E37 Description: "Invalid object name 'dbo.GPIPR703_INPOP10H'.". helpFile=dtsmsg.rll helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}". What is the problem here? Why won't Database Object Copy work?

I got the same error when trying to export a sql 2005 database to an access database. [Connection manager "DestinationConnectionOLEDB"] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Unspecified error". Is there a replacement for sql 200 dts that works?

I have since tried this with just about every combination there is - with and without indexes, create tables vs pre-creating tables, with and without triggers, with and without data. The weird thing is, if you specify tables with no data, the package seems to run (no errors) but it doesn't actually create the targets. Microsoft needs to fix this and fast. As you noted, there is no saving of a database export.

Hi NewSQL2005 User, i got the same problem - but also a solution :-) Try to set the button "CopySchema" to YES. Then it should work. regards David

Hi Where is this CopySchema button. Sorry if this is a really stupid question but this is the first time I am really working on SQL2005. Thanks Andre TITLE: ------------------------------ An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued and failed. ------------------------------ADDITIONAL INFORMATION: An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued and failed. ------------------------------BUTTONS: OK------------------------------

DTS is a crap, it always ends with this error, I tranfered one table by another and found out that DTS is not capable enough to copy one stupid dataview (40 rows). I give up DTS, I'll make my own application in C#, if you want it, send me a mail.

I've been using DTS since the beta of SQL Server 2000. Your aggravation with SSIS is most likely due to your inabilaty to investigate the problem, and approach it like an actual software developer would. Try understanding your problem more fully, do some research, and work through your issues before posting a message in poorly written english.

"DTS is a ***" just about sums up my opinion of it too.Slow to load in the IDE. Inconsistent behaviour. Throws a wobbly when dealing with excel. Meaningless error messages etc....What is the point of an error message that you then have to go and look up on google? Why not display a bunch of 1's and 0's or throw out a punchcard?I was getting the same error number which is how I found this post, but my problem is entirely different.Analogy of my personal experience of using SSIS:Imagine a car with the most wonderful engine ever devised. Then make the seats uncomfortable. Make the dashboard, difficult to understand with lots of colourful lights that you cannot make head nor tail of. Stick the rear view mirror on the wrong way round. Next attach some wheels with flat tyres and hang about 15 of those 'magic tree' air fresheners that make you want to puke when you go near it. etc...et le voil!MS seems to have missed something key here.Lots of MS shops will upgrade to 2005 (they can't or won't pay for Oracle at al.)This will happen anyway. SSIS will slowly dribble into offices around the world like a virus.People can still use DTS if they wish, but wouldn't it be better if they got on board with SSIS?So why doesn't MS offer more resource in terms of helping people to switch and get going with this? I am at the point where I'm going to recommend we purchase another ETL tool. One that works, that doesn't have meaningless errors. But in the meantime I'll have to agree with yer man there.

censorship? are we in china?they altered my post*** = cr@p

About the problem. I too ran into this issue and what I found was that a column in source database allowed NULL's and that corresponding column in my destination table did not. DTS (SSIS) is extremely picky about details like these and for a good reason. If that doesn't solve then verify that the datatypelengths (if applicable)are maching and of course the datatypes themselves need to mach. About the comment. I wouldn't say that DTS or SSIS is ***, in essence it's very useful and functional - like you stated - a superior engine with a pretty decent tailpipe and fuel filler door.It's getting the fuel filler door open,in just the right angleand getting the filler hose fit in etc. that is theproblem. And of course theerror messages truly are completely useless. I mean, who in their right mind thought that seeing 0x854F58 makes perfect sense: "Oh 0x854F58 - of course! Let me fix that!" But look at the positive side. Microsofts poor interface design allows third parties to step in and create an interface that is meaningful and useful. I do agree though, I too would prefer if the car thatI just bought can be driven without going back to school.

It worked fine for me once I told it to copy the schema. The whole database went across smoothly and quickly.

Hi, if you have that code I would really appreciate if you send it too me. You are SSIS packages are way to sensitive((

So... Is there a Copy Schema button? Where is it?

Hai. Myself Santhoshkumar. You are write that send the solution . Plz send it me.. Thanks. Bye. Regards, Santhosh kumar.A

LostFromTheStart wrote: So... Is there a Copy Schema button? Where is it? I had the same problem by using the 'Transfer the Database Objects'. Then, i use the Transfer SQL Server Object Control. You can find the copy schema option in the property window. Problem Resolved. I am also relative new to SSIS.It seems the transfer the database objects offering you much more options.

It is not a button. It is a grid item in the Objects panel of the edit dialog. You can use the associated right hand dropdown list to set it to either True or False.

Gracias, habiltando esa opcin funciona perfecto.

Thanks, fixed my problem 5 years later.