Our PRODUCTION clustered SQL Server 2005 SSIS is on a Windows Server 2003 box and has SP4 applied. But quite a while ago (years), we stopped being able to see the packages in MSDB via EM as we should. BUT they did show up when setting up the package as a job, so were hoping some service pack along the way would fix this. Recently (before adding SP4), we have stopped being able to deploy to the server and have had to deploy as a file instead. Reinstalling SSIS is probably in the future as the likely only fix, but when we do a reinstall, will we loose all the packages deployed to the server? They are stored in MSDB but if that is the corruption, restore it will also recreate the problem, correct? We have a temp fix of running jobs from the files, but we prefer to load them to the msdb. Anyone else done this or found another way to fix? Thanks for your input, Linda

Could you double check your DCOM permission setting is correct for SSIS service? There are some known issues for it: http://support.microsoft.com/kb/2000474

The above didn't fix our issue. Reinstalling did. We had to reinstall for another reason and it happens, it fixed this issue.