After numerous growing pains of getting Vista upgraded from XP Pro SP2, I've finally arrived at the last hurdle. Installing SQL 2005 Server (this is a development machine). I have installed SQL 2005 Server, plus CTP SP2, and, whenever I start an SQL script that uses linked servers, I get MSDTC on 'XXXXXX' is unavailable. And yet, MSDTC is running, I've applied all of the new security stuff for MSDTC to allow network connections. But no joy. Anyone with any problems regarding this? Anyone happily running SQL 2005 Server (Standard) on Vista? BTW, the serverthat SQL says is unavailable is the machine I'm runningon! Love being on the bleeding edge... :D\n\nHere's the actual message:\n\nDropping foreign keys from [dbo].[D_CALL_LOG]\nDropping constraints from [dbo].[D_CALL_LOG]\nDropping index [IX_D_CALL_LOG] from [dbo].[D_CALL_LOG]\nRebuilding [dbo].[D_CALL_LOG]\nMsg 15477, Level 0, State 1, Server RMPSWS, Procedure sp_rename, Line 465\nCaution: Changing any part of an object name could break scripts and stored\nprocedures.\nCreating index [IX_D_CALL_LOG] on [dbo].[D_CALL_LOG]\nCreating primary key [PK_D_CALL_LOG] on [dbo].[D_CALL_LOG]\nAdding foreign keys to [dbo].[D_CALL_LOG]\nCreating [dbo].[D_LOC_INST_LIST]\nMsg 8501, Level 16, State 3, Server RMPSWS, Line 11\nMSDTC on server 'RMPSWS' is unavailable.