Encryption not supported on SQL Server - Error Message
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
June 17th, 2005 9:30pm
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.
June 17th, 2005 9:48pm
Did MakeCert resolve this - if so, would you please post the entire process - having same problem - thx
September 29th, 2005 4:25pm
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.
November 24th, 2005 3:57am
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 (.)
December 9th, 2005 4:59am
Thanks a lot for your replies, people! I ran into the same problem and this thread helped me saved a bunch of time!! :)
December 16th, 2005 10:08pm
Yep, agree to that, thanks for the post. Restarted SSIS and it worked a treat. Cheers - R.
March 22nd, 2006 7:31am
What was resolution? Even I am also running into same problem as I have 2 SQL instances on same server
July 7th, 2006 11:39am
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
December 22nd, 2007 2:15am
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.
March 18th, 2008 5:48pm
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.
March 23rd, 2008 2:28am
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...
November 27th, 2008 1:23pm
Thanks Roro & ailuz, you can't know how much time and aggravation you have saved folks!
February 1st, 2010 9:41pm
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.
May 12th, 2010 12:48am
Exactly on target for me. Thanks Roro and ailuz
August 6th, 2010 8:07pm
Great and Thanks! It worked for me after changing the Servername with SQLSErver\2005instance and restarting the SSIS Service.
March 18th, 2011 6:55am