Hi Alex, appreciate the write up, but I do share the popular doubts about the track record of the software (and the LeVar quote, and I speak as a...

Cheers guys, actually narrowed it down to a bunch of SPIDs (that's me being polite) doing a data migration project and using tons of exclusive latch locks, which I think...

george sibbald (5/31/2012)

---

right click the database and select properties - log shipping, check out how it has been configured.

It just sounds to me as if your log shipping configuration is...

george sibbald (5/31/2012)

---

the classic reason for logshipping failing in a clustered environment after a failover is the log backup directory not being defined as a share that both nodes of...

Greetings Greg, glad to see you're making progress on your issue. It's far above my mediocre scripting skills, otherwise it looks like a juicy one to sink teeth into.

I'm...

Hi Anthony, I'll use that as a final resort, but meanwhile would I be insuring myself against failover if I go ahead and rebuild shipping on the 10 dbs NOW?

Looks like we have a problem then because the only "plausible" error we found in the logs was,

"The server's configuration parameter "irpstacksize" is too small for the server to...

Shot in the dark here, but have you ensured you've got AWE enabled and the PAE switch on? I think at default SS2K only addresses 2gb of memory, and...

I've been having a lot of similar issues recently, and would like to know if this has worked for anyone on 2K.

Anyone?

I sit corrected on #2.

Fellas,

1) The link was not present on my screen, possibly the result of being stripped out of the page by corporate...

??

Not found, no.

This is for SS 2000, gentlemen!!