Can't configure log shipping

Question

Can't configure log shipping

Viewing 12 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic. Login to reply

fminns-1058143 Default port Points: 1404 More actions · Answer 1

Ok, so I have had a look and sure enough there is a table that has two columns set up as UNIQUEIDENTIFIER.

But a) the table is empty/

And b) the same table exists on the test server (direct restore of the live database) and on that server log shipping works.

So i'm still mighty confused!! 🙂

Farren

Andrew Gothard-467944 Hall of Fame Points: 3928 More actions · Answer 2

Andrew Gothard-467944

Hall of Fame

Points: 3928

November 26, 2009 at 7:50 am

#1084598

Aw. Sorry if I sent you off on a wild goose chase mate.

fminns-1058143 Default port Points: 1404 More actions · Answer 3

Not at all Andrew, it's all a learning exercise for me anyway 🙂

Any help is always appreciated.

Andrew Gothard-467944 Hall of Fame Points: 3928 More actions · Answer 4

How about putting Profiler on the target server to see if you can pin down more precisely where it's breaking?

JKG SSCommitted Points: 1563 More actions · Answer 5

Sorry - just re-read the error! Ignore that suggestion!

Del Lee SSCrazy Points: 2781 More actions · Answer 6

Any more suggestions on this? I am now seeing the exact same error in my environment.

Del Lee

fminns-1058143 Default port Points: 1404 More actions · Answer 7

Hi,

The problem our end was that we had SQL Standard installed, but log shipping only work on Enterprise.

Nopt sure if that's the same issue with you?

Farren

Del Lee SSCrazy Points: 2781 More actions · Answer 8

That's not correct. See the "Requirements" paragraph from the link below...

http://msdn.microsoft.com/en-us/library/ms188698(v=sql.90).aspx

Del Lee

fminns-1058143 Default port Points: 1404 More actions · Answer 9

Sorry, we were still using SQL 2000 at the time, and that had to be Enterprise if my memory serves me correctly.

fminns-1058143 Default port Points: 1404 More actions · Answer 10

Actually, just read back through the thread. I was thinking about a totally different log shipping issue we had at the end pf last year.

We never did get this issue sorted but mostly because it was no longer deemed necessary.

Apologies for the confusion.

Perry Whittle SSC Guru Points: 234013 More actions · Answer 11

To use log shipping in SQL Server 2000 did indeed require Enterprise edition, but that's not the issue here.

Del Lee (3/19/2012)
Any more suggestions on this? I am now seeing the exact same error in my environment.

Are you configuring LS via the gui or via a T-SQL script?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Del Lee SSCrazy Points: 2781 More actions · Answer 12

Are you configuring LS via the gui or via a T-SQL script?

It was a permissions issue setting up the Monitor, but now I'm facing another obstacle. I will start another thread after doing more investigation, if necessary. FWIW, I am setting it up via GUI.

Del Lee