you will have to try and find those missing log backups and manually copy them over and restore them. If you cannot find them or someone has truncated to log...

I think you are correct to change your stance Brad. Whilst it is true you can do harm if are not aware of the effect of what you are doing,...

having run the corrected SQL as noted above, you would then copy and paste the result set into another query window and execute it.

having of course determined it is going...

david

having googled this error message i think it is likely you already have sql native client installed and you need to remove it.

fix seems to be

copy install files to...

you only put a delay into the...

by good fortune I have just seen another post with a reference to a link about 17883 and related errors, I think you should read it

http://technet.microsoft.com/en-us/library/cc917684.aspx#_17883%20Detection

as mirroring is at the transaction level, whereas log shipping is at the transaction log level, mirroring would be the better bet. In this instance I would run mirroring in...

on this one MS would probably ask you apply SP4. the extra info it gives i think is in the form...

this will be a lot easier if you can name the server the same as the original, especially as you have replication.

build server with same name

install SQL exactly the same...

if you got the 17883s again thats an error, those are not normal messages on a restart. If your sysadmins cannot identify a HW\OS problem I would contact microsoft.

no you can use it to delete .bak files, just speccify the directory holding the backup and the backup file extension (usually bak)

easiest way is to use the backup task to backup to...

well thats the reason you were having connection problems.

Not a lot you can do now just keep an eye on it see if it becomes a recurring problem.

there are a number of such scripts in the scripts section of this site. If the database is any size they are likely to take a while to run.

Heres one...

you have the infamous 17883 Messages in there which suggest the server was stressed. these could have the effect of making SQL unresponsive.

Did you only have those two occurrences or...