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 not 'cluster...

another problem we have had is logship.exe (think thats the name but anyway the executable) not being installed to exactly the same path on the two nodes.

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 the cluster...

I think we should clarify that you should not remove a service pack simply by replacing the resource database with a previous version of it. I'm sure there is more...

so far all my clusters have been active\passive so I would not like to venture an opinion, see if any one else jumps in.

starter for 10

http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx

are they there in the correct location? That error definitely says the system cannot find the file specified. If it was permissions you would get OS error 5, not 3.

How...

either F:\mssql\data does not exist or the database files are not in that location, therefore those databases are marked suspect and cannot be opened.

the database files are no longer in...

please post the part of the errorlog with the error messages

it could be security but take a look at the SQL errorlog first via notepad for any error messages

if you mean you want to apply SP4 that is already applied, SP4 is version 8.00.2039.

If you are going to patch SQL:

make sure you have backups of all databases...

The explanation reads : 'Differential backups require backup without recovery, which is not allowed for the master database'

that should read 'Differential backups require restore without recovery (of the full beforehand),...

In detail:

start up failover cluster manager, under services and applications right click the SQL cluster resource and select properties, in the summary pane double click the server name, the possible...

totally from memory as I dont have a machine here -

in cluster manager, click on the SQL network name, select the advanced tab, possible owners are listed in there,...

you don't HAVE to for the patch to work but its advisable that you do to avoid the risk of a failover happening whilst applying the patch, which you don't...