• The error was after a SQL2K upgrade to SP3.