Article ID: 955920 - Last Review: December 20, 2008 - Revision: 4.0 FIX: Error message when you try to install SQL Server 2005: "[Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it"Bug #: 50003040 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. On This PageSYMPTOMSWhen you try to install Microsoft SQL Server 2005, you receive the following error message: SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it. To continue, correct the problem, and then run SQL Server Setup again. SQL_ERROR (-1) in OdbcStatement::execute_batch sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ... sqlstate=42000, level=16, state=1, native_error=15352, msg=[Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it. sqlstate=42000, level=16, state=1, native_error=15232, msg=[Microsoft][SQL Native Client][SQL Server]A certificate with name '##MS_AgentSigningCertificate##' already exists or this certificate already has been added to the database. sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server. sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process. sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating. PRINT 'Signing sps ...' if exists (select * from sys.certificates where name = '##MS_AgentSigningCertificate##') drop certificate [##MS_AgentSigningCertificate##] create certificate [##MS_AgentSigningCertificate##] encryption by password = 'Yukon90_' with subject = 'MS_AgentSigningCertificate' IF (@@error <> 0) RAISERROR('Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.', 20, 127) WITH LOG
RESOLUTIONCumulative update informationSQL Server 2005 Service Pack 2Important You must use this fix if you are running SQL Server 2005 Service Pack 2.The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 956854
(http://support.microsoft.com/kb/956854/LN/
)
Cumulative update package 10 for SQL Server 2005 Service Pack 2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:937137
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2005 Service Pack 3Important You must use this fix if you are running SQL Server 2005 Service Pack 3.The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 959195
(http://support.microsoft.com/kb/959195/LN/
)
Cumulative update package 1 for SQL Server 2005 Service Pack 3 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:960598
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Notes
WORKAROUNDTo work around this problem, use one of the following methods. Method 1If this problem occurs when you use the USESYSDB option to install SQL Server 2005, follow these steps:
Method 2
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 956854
(http://support.microsoft.com/kb/956854/LN/
)
Cumulative update package 10 for SQL Server 2005 Service Pack 2 REFERENCESFor more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137
(http://support.microsoft.com/kb/937137/LN/
)
List of the builds that are available after SQL Server 2005 Service Pack 2 was released For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:935897
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:http://go.microsoft.com/fwlink/?LinkId=71711
(http://go.microsoft.com/fwlink/?LinkId=71711)
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:822499
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates APPLIES TO
| Article Translations
|
Back to the top
