>I belive that empty values cause the error.

That's what I thought as well. So, earlier on tonight, I replaced all empty values with DATETIME(). When I run the package again, it ended up in the same situation. Also, I have about 40 other tables that are being imported successfully before that happened. And, they have some datetime fields which have empty values. So, I suspect there is a bug in the OLE DB provider in regards to that. I found on the Internet that such as provider for another technology was creating the same problem for datetime field. Maybe I would have to check if the latest provider is installed on the server. Do you know anything in regards to that?