Unanswered: Log Shipping Restore Failures - OS error, the trail's gone dead
I've finally got to a point with our ten log shipping processes running in 15 minute cycles where the contention issues we were suffering from have stopped.
Every day a different restore job will fail causing the log shipping for that DB to go out of sync and fail. The SQL logs do not give any clues however on the servers application event viewer the initial faliures are registered always with the same two application error events for SQLServer in this order:
udopen: Operating system error 32(error not found) during the creation / opening of physical device d:\MSSQL\logs\DB_NAME_log.ldf
FCB::Open failed:Could not open device d:\MSSQL\logs\DB_NAME_log.ldf for virtual device number (VDN) 2.
Ok so it can't open the file which accounts for the restore failure. Does anyone know how I can carry on the trail from here?