Question

我在Windows Server 2008 R2企业中配置RM服务器时遇到以下错误：Object Already exists。请找到日志。

I, 2014/10/29, 08:18:40.108, Variable : Key = DefaultLogin, Value = GAP-RELEASE\BuildUser
I, 2014/10/29, 08:18:40.124, Variable : Key = DefaultAdmin, Value = GAP-RELEASE\BuildUser
I, 2014/10/29, 08:18:40.124, Variable : Key = DatabaseName, Value = ReleaseManagement
I, 2014/10/29, 08:18:40.124, Variable : Key = DefaultLocalService, Value = NT AUTHORITY\LOCAL SERVICE
I, 2014/10/29, 08:18:53.384, Database ReleaseManagement, version 12.0.30723.0 was installed successfully.
I, 2014/10/29, 08:18:53.399, Created Release Management database.
E, 2014/10/29, 08:18:53.462, Received Exception : System.Security.Cryptography.CryptographicException: Object already exists.

   at System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr)
   at System.Security.Cryptography.Utils._CreateCSP(CspParameters param, Boolean randomKeyContainer, SafeProvHandle& hProv)
   at System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer)
   at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle)
   at System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair()
   at Microsoft.TeamFoundation.Release.CommonConfiguration.Helpers.CryptoHelper.ConfigureServerCryptoKey(String serverName, String databaseName)
   at Microsoft.TeamFoundation.Release.Configuration.ConfigurationManager.Configure(ConfigurationUpdatePack updatePack, DelegateStatusUpdate statusListener)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
I, 2014/10/29, 08:18:53.462, Work completed for GetConfiguration() call : got out of turn error
E, 2014/10/29, 08:18:53.462, Object already exists.

Answer 1

我有同样的问题。很多人都转发到这个解决方案：http://blogs.objectsharp.com/post/2014/11/04/%E2%80%9CObject-already-exists%E2%80%9D-error-during-Release-Management-server-configuration.aspx

这对我没用，我终于让infra团队恢复了机器。这解决了我的问题。

在我的情况下，数据库服务器在另一台机器上，我保留了所有发布路径和模板。

我唯一需要重新配置的是IIS路径：http://localhost:1000/releasemanagement

Answer 2

使您的发布管理服务帐户成为发布管理服务器上的本地管理员。

更新：我最近在客户端遇到了这个问题。服务帐户是本地管理员，但该帐户没有机密钥匙文件夹（C：\ Users \ All Users \ Microsoft \ Crypto \ RSA \ MachineKeys）的必要权限。出于某种原因，我无法应用权限 - 即使使用完全特权帐户，我也收到了“拒绝访问”消息。

我最终解决了以下问题：

与服务用户
向服务用户授予完全读/写权限
将文件夹的所有权重置为SYSTEM帐户

版本管理服务器安装问题 - 对象已存在

2 个答案: