Yes you may be able to recover some of the transactions in the LDF file. What you need to do is perform a "Tail Log" backup. Refer to this KB...

Are you able to access the file via a shared folder? If so, then the regular datapump will work fine.

If not, and you definitely can't save the file locally (even...

One thing thats not clear here is what version of VMWare we're talking about. The flagship product VMWare ESX Server, does get down and dirty with the hardware and allows...

Were you able to setup a datapump to import the file?

Also, just to throw oil on the fire, the number of Parameter values depends on what delivery method and other options are selected.

Was this package running before your upgrade to SP2?

Seen a number of these type of errors occurring after SP2 was applied. File permissions don't seem to be the problem.

Are you...

That would be possible particularly in MSDE and SQL Express as they close the database when there a no active connections. In SQL Server if the database is set to...

The important part is not really how its done, just that each process is seperate and unrelated to the other processes that just happen to make up Log Shipping. This...

In the DTS package, after the ActiveScript task have a Text Source connection then have a SQL Server connection and put a datapump task between the two connections.

What account does the SQL Services run under? When you execute a DTS package manually it will use your login credentials. Executing from a stored procedure/schedule job/etc... it will run...

Not too sure of the specific coding, but I think the best bet would be to have an ActiveScript task that performs a HTTP GET and saves the file locally....

Log Shipping itself does not have automatic failover. You will need to "bolt on" something extra to have automatic failover. Even then it still miight not be automatic. What happens...

Have a look over at http://www.sqldts.com they'll have a few examples.

To execute a windows process on another server you'll need to use a tool like PSEXEC from Sysinternals.

A quick Google on the error code seems to indicate that this is a data truncation issue. If you're able to veiw the detail messages from the DTS package log...