Post reply

SSIS error object does not exist while it SURE does

  • September 14, 2006 at 8:39 am

    #114792

    Moving from sql 2005 to sql 2000.Using transfer sql objects

    gone through all correction and when it comes to importing even tables this error pops up...

    Error: 0xC002F325 at Transfer SQL Server Objects Task, Transfer SQL Server Objects Task: 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.aac

    Your ideas are very welcome on this

  • September 15, 2006 at 3:01 pm

    #660833

    Don't use the native client - use the sql server OLEDB provider instead.  Also make sure you have SP1 and the post SP1 rollups for SQL 2005.  I think it shows as build 2139.

    Joshua Perry
    http://www.greenarrow.net

  • November 18, 2008 at 4:53 pm

    #900218

    Hi Joshua

    When you use Transfer SQL Objects, I only have the option to use SMO objects - I can't choose to use an OLEDB connection manager

    regards

    Jenny

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply