This is most likely the effect of a well-known issue in SQL Server 2000 Editions.

There is a fix for this is SP1 and upwards.

Install the latest SP and it should...