All I can say is SQL Server is f'ing retarded. It just shouldn't be this hard to find and/or decipher this error. Retarded I say.