November 18, 2010 at 7:43 am
We have two 2003 Server clusters with SQL Server 2005. I've noticed for some time that with both clusters, the scheduled SQL backups work fine when the cluster is on the primary node but fail when the cluster is on the secondary node (I can run them manually without issue). I found an error ("Unable to read local eventlog (reason: The parameter is incorrect).") a known issue with SQL Server 2005 - 9.00.1399.06 and that it is fixed in SP2. Even move to SP3 as it has been stable in the Data Center since January.
I downloaded SQL Server 2005 SP3 and tried to apply it to one of the clusters and it failed. A look at the install log revealed the message, “The product instance MSSQLSERVER been patched with more recent updates.” Apparently, some portion of SQL thinks it has been updated and now will not allow the update to proceed, even though @@version still says it is 9.00.1399.06 .
December 27, 2010 at 10:09 am
Can you check both of the nodes individually for the versions applied? It sounds as though someone might have applied a patch to one of the nodes and not the other.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply