Hi, When I click on the MSDB node, under Stored Packages (in Object Explorer | my local server's Integration Services), I get the following error message: Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client) I can, however successfully, enumerate File System packages. I am running... Microsoft SQL Server 2005 - 9.00.1187.07 (Intel X86) May 24 2005 18:22:46 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1) ...on Windows Server 2003 SP1 Does anyone know what is causing this, and how to fix it? Thanks, krog

Appears to be related to the following post: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=19019 ...so I need to install a certificate on my computer. Am now checking whether I can use the MakeCert utility to address this.

Did MakeCert resolve this - if so, would you please post the entire process - having same problem - thx

If you installed your SQL Server 2005 as an named instance with a default SQL Server 2000 on the machine, you might need to change the SSIS configuration file to point the MSDB to the right instance. After changing the configuration file, you need to restart the SSIS service.

To Add to RoroEdit the config file MsDtsSrvr.ini.xml in C:\Program Files\Microsoft SQL Server\90\DTS\Binn as follwos:=====================================<?xml version="1.0" encoding="utf-8"?><DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> <TopLevelFolders> <Folder xsi:type="SqlServerFolder"> <Name>MSDB</Name> <ServerName>SQL_2K5_SERVER_NAME</ServerName> </Folder> <Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>..\Packages</StorePath> </Folder> </TopLevelFolders> </DtsServiceConfiguration>===============================The original value for <ServerName> is just a dot (.)

Thanks a lot for your replies, people! I ran into the same problem and this thread helped me saved a bunch of time!! :)

Yep, agree to that, thanks for the post. Restarted SSIS and it worked a treat. Cheers - R.

What was resolution? Even I am also running into same problem as I have 2 SQL instances on same server

I had the issue with multiple instances as well, changing the "." in the ini.xml to the SERVER/INSTANCE revealed my SSIS packages, thanks a million... Gary

what kind of permissions do you need to do this, i am trying to make the edit in the ini file but it tells me i don't have sufficient permisissions, i am an administrator in the box.

Taking a punt, but its possible that the SSIS service may lock the file when running (not 100% sure). So stop the SSIS service then retry, R.

I had a series of SSIS packages running quite happily for months until I changed the windows local admin password then started to see this Encyrption not supported message when trying to open the MSDB in SSMS. The SQL Server, SQL Agent, and SQL IS services where all running under this local admin. I tried the suggested change to the MsDtsSrvr.ini.xml file mentioned previous but still no joy. In the end I simply changed the services to run under a different account (either domain or local system) and the problem was mysteriously resolved. Anyone got an ideas how I can get it workingusing theoriginal local admin account again? Thanks in anticipation...

Thanks Roro & ailuz, you can't know how much time and aggravation you have saved folks!

I have the same issue where I changed the local admin password and can no longer access MSDB. Did you ever find a solution. As soon as I change it back it works again.

Exactly on target for me. Thanks Roro and ailuz

Great and Thanks! It worked for me after changing the Servername with SQLSErver\2005instance and restarting the SSIS Service.