I would suspect the renaming to be the culprit here.  Google on how to fix SQL Server after a host rename... I am surprised it worked all after the rename;...

The first google hit on your message (No more buffers can be stolen) gives this link... follow it.

http://support.microsoft.com/kb/316749

depends on how they are "saved"... if in XML file, you can do a "comp"... although that won't tell you too much.  There are other tools out there that are...

Turn on Address Windowing Extensions (AWE) in OS and SQL Server

The complete process goes like this…

I know that log shipping defaults certain jobs to every minute; because when it fails, it send three messages to my application event log and to the SQL Server log. ...

good work!  thanks for the update and links.  they will come in handy.

Yes, thanks!  this works... just what I needed, too!

This is ABSOLUTELY the easiest way to do this....  I copied the script from the library here and while it stopped a lot of processes, it did NOT allow me...

any messages anywhere?  any logs?

Is IIS installed?

so, create a folder that includes everything in the path... in your original post you said it was the following:

'C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32\Backup\BACKUP_20061012_023024/backup.dat'

and in this post, you stop...

that's "the logs" not "three logs"... sorry.  proof read then hit send

Good question!

If the plan was written to purge logs older than 3 days, I look for three logs after the last three backups, and logs earlier than that are no...

by the way, it is much easier for people to read if you message actually says something about what you need "help" with... everyone here needs help.  thanks.

looks like a network drive issue.  that's the same error I was seeing yesterday trying to access a backup on a shared drive.