Monday, March 19, 2012

Access - SQL Server 2005

I am trying to import a database from Access to SQL Server 2005 and it keeps failing. I don;t want to use anything but the simple screens Microsoft provides for Import/export. Any ideas on how I can make this happened?

- Prepare for Execute (Error)

Messages

Error 0xc0202009: {8A98B034-459D-4200-AD18-555244A05373}: SSIS Error Code DTS_E_OLEDBERROR. 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".
(SQL Server Import and Export Wizard)

Error 0xc020801c: Data Flow Task: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Source 64 - DP_ROUTE_DRIVER" (6918) failed the pre-execute phase and returned error code 0xC020801C.
(SQL Server Import and Export Wizard)

I am also having issues with this as well

Im thinking it might have something to do with the 0x80004005. error

i did some research and possibly the user for the SSIS package doesnt have rights to the registry? according to http://support.microsoft.com/default.aspx/kb/295297

maybe it has something to do with access to the registry key.?

but i cannot figure out what would need access...

Im using sa authentication for the SQL server..

I am also running vista business ultimate and SQL2005 and Visual Studio 2005

|||

What version of Access are you using? If you are using Access 2007 you will need to use the ACE provider instead of JET 4.0.

Thanks.

|||sorry for delay of response

I am using 2003 ...my issue might have been to do with a corruption or error in the package that the wizard uses to do the import as i tried recreating the process again and it worked fine.. then i changed the script that gets built and this seems to be where the error is

Its like you cant do a custom script (even if it is the same script the system creates) with it..

ill post again when i come back on this project (prob next week)

cheers

No comments:

Post a Comment