We help IT Professionals succeed at work.

Error While Data Transfer

Hi All , I'm using Sql Server Import and Export Wizard. When it starts copying data after some time it fails and in report I found the error like :

Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Success)
- Setting Destination Connection (Success)
- Validating (Success)
- Prepare for Execute (Success)
- Pre-execute (Success)
- Executing (Success)
- Copying to [dailypaisaa].[dailypaisaus].[Pay1] (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Communication link failure".
An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "TCP Provider: An existing connection was forcibly closed by the remote host.".
(SQL Server Import and Export Wizard)
Error 0xc0209029: Data Flow Task: The "input "Destination Input" (74)" failed because error code 0xC020907B occurred, and the error row disposition on "input "Destination Input" (74)" specifies failure on error. An error occurred on the specified object of the specified component.
 (SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task: The ProcessInput method on component "Destination - Pay1" (61) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
 (SQL Server Import and Export Wizard)
Error 0xc0047021: Data Flow Task: Thread "WorkThread0" has exited with error code 0xC0209029.
(SQL Server Import and Export Wizard)
- Post-execute (Error)
Messages
Information 0x402090df: Data Flow Task: The final commit for the data insertion has started.
(SQL Server Import and Export Wizard)
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Communication link failure".
(SQL Server Import and Export Wizard)
Information 0x402090e0: Data Flow Task: The final commit for the data insertion has ended.
(SQL Server Import and Export Wizard)
Error 0xc0047018: Data Flow Task: component "Destination - Pay1" (61) failed the post-execute phase and returned error code 0xC0202009.
(SQL Server Import and Export Wizard)
- Cleanup (Success)
Messages
Information 0x4004300b: Data Flow Task: "component "Destination - Pay1" (61)" wrote 22598 rows.
(SQL Server Import and Export Wizard)

What does this error means.
How could I resolve this.
Actually I've to Export some of table to my Server. Is there any other way to transfer data.
Comment
Watch Question

Varghese JacobAssistant Project Manager

Commented:
What is your source data? Are you able to connect to the source data using OLEDB driver?

Author

Commented:
YES

Commented:
If you are trying to do this from destination server, try doing the same thing from source server by selecting the same source and destination as earlier.

Author

Commented:
Yes, I tried that but  still I could not copy any of the table from Destination Server to My Local Server (Machine).  One more thing.  3  days before I truncated all  log files and shrink my database.  Even I create another database on same server and tried  to copy some table from  my local machine to that database but still  the same  problem is there.  What  could be the best solution.  I googled many sites but there was no use of it.
The error you need to focus on is here:
An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "Communication link failure".
An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80004005  Description: "TCP Provider: An existing connection was forcibly closed by the remote host.".
Here's the first link from Google:
http://www.sqlservercurry.com/2009/07/resolving-error-existing-connection-was.html
But basically your connection is broken, either because the remote SQL Server has a good reason to close the connection, or because there is some kind of network failure in between.
I would start by examining the logs on the remote SQL Server around the time that the link was broken.
 

Author

Commented:
Thanx for your valuable reply.  I will try and post u back.
Steve WalesSenior Database Administrator

Commented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.