did you create SQL authenticated account or a windows account? It needs to be a windows account.

Post the login error message from the SQL error log with the state value.

file size is not necesarily representative of space used in database

run sp_spaceused to see how much actual data in database

then run dbcc checkdb to confirm database ok

pshaship (4/18/2010)

---

If you have that log backup on primary and secondary, check it out on the primary as well.

If its ok on the primary it was corrupted by the...

If you have that log backup on primary and secondary, check it out on the primary as well.

If its ok on the primary it was corrupted by the copy...

you will need to do a full restore with norecovery again but you wont have to reconfigure logshipping, Just temporarily disable the log shipping jobs, move log backups from BEFORE...

seems this is a known issue. reported in this MSDN connect issue

https://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=422562#tabs

This seems to suggest it is fixed in 2008R2 but does not say when it is fixed in vanilla...

the SQL errorlog should provide the answer.

Was agent showing as down in SSMS or in configuration manager?

Possibly Agent was up but not all the databases were recovered following restart, agent_XPs would show as disabled in this...

SSIS is not required. (you have at applied at least SP1 , yes?)

The double '\\' does not look right in your backup path. amend that to single '\'.

N'E:\\SQL Backup\\Production\\Production_backup_201004181602.bak'

check...

It does the same as any other full backup, it takes the active part of the transaction log so the database can be restored to a consistent point.

Trey Staker (4/17/2010)

---

Does anyone here support sybase? If I recall there was a sp_who there. Is sp_who2 a complete rewrite from sp_who? Is sp_who is sybase at...

If you do only have standard edition of SQL 2000 google for 'Installing Log Shipping for SQL 7.0' by Natasha Huggins. Works also on SQL2000.

Its from the BORK (Back Office...

Most, BUT NOT ALL, third party tools write to msdb the same way as SQL native.

You are definitely missing a log backup or the log is being truncated, possibly a...

so this is not logshipping wizard (sql 2000 yes) but in-house built.

Could be a truncation of the log which would be reported in errorlog

'with init' hasn't got lost has it?

this...

On the primary, have you moved any log backups prior to you full backup out of the way.

On the secondary remove any log backups prior to your full backup from...