Hi Damon

This might be the issue: The SQL Server Engine must be running with a
domain ID and that ID must have access to the share where the files are to
be stored. This might solve the issue you are having, but are you sure
that you want to use Log Shipping? MS Log Shipping has some limitations:
If there is a long running update transaction running, log shipping
continues to look like it is working, but it actually may be doing nothing.
When a BACKUP LOG runs, nothing beyond the oldest uncommitted update is
actually written to the transaction logs that are being shipped. The
receiving database could be hours or even days out of sync even if the logs
are shipped every ten minutes and reporting success. Database Mirroring in
SQL 2005 is everything that Log Shipping should have been.

Mark


------------------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.

==============================================================================

MS Sql Server LazyDBA home page