This might be a unique situation but, we did found the cause to our situation with regards to this error.

Our SQL sever 2005 environment is running in a active/passive cluster...