I'm having some trouble getting my LSCopy job of Log-Shipping on my SQL Server 2005 server, to work.

The LSBackup job is configured so the backup is made locally (D: drive)

The LSCopy job is configured to copy from the primary (\server_name\d$) and copies it locally to the secondary server.

The LSRestore is restores the local copy to the secondary database with NORECOVERY

The LSBackup job runs fine, copies the file to the location specified.

The LSCopy job fails. The error message states that it goes to the source for settings. Gets the settings (I assume) then begins the copying.

This errors saying:

Error: Not enough server storage is available to process this command.

What I'm not sure about is whether the destination folder needs to be a network share, or if just \server_name\d$ is accepted.

Any help will be really appreciated!

  • Does drive on which you are dumping log files on secondary server has enough space. Is your setting to remove old log file after certain time is working ?
    – Shanky
    May 7, 2015 at 16:34
  • Thanks for the comment, yes the drive does have enough space. This is the first time this drive has been configured for Log shipping so whether or not the remove is set correctly is irrelevant as there are no previous backups on the drive
    – Gareth
    May 7, 2015 at 16:41
  • Well than you have to add some disk space ?
    – Shanky
    May 7, 2015 at 16:42
  • No sorry that's not the answer. Thanks for the effort.
    – Gareth
    May 7, 2015 at 16:56
  • @Shanky it's not about space. See Spörri's answer about those error messages.
    – Marian
    May 8, 2015 at 9:03

1 Answer 1


The destination path for the LSCopy job has to be an UNC Path for all practical purposes, to make things simpler to debug I would reccomend not to use the default \d$ shares as you will have to change the permissions on them but connecting to \localhost\c$ is a network connection. Now the error

***Error: Not enough server storage is available to process this command.

Is an operating system error. but not an error from the SQL Server. You are probably starving the computer on memory or having some network issues, If on Windows Server 2003 a quick reboot of the secondary server will fix this temporary and then I would look into memory settings on the server

  • That's indeed the reason, see also Not enough - error codes. That specific message corresponds to: ERROR_NOT_ENOUGH_SERVER_MEMORY (Probably related to RPC calls over the network).
    – Marian
    May 8, 2015 at 7:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.