Issue resolved.

Downloading and installing Service Pack 2 for SQL Server 2005 seems to have cured it, although I still don't know what caused it in the first place.