We had a similar issue with SQL 2005 linked to an Oracle database. We found that the SQL server registry settings referring to our Oracle db referenced the wrong...