Problems installing Team Foundation Server 2010
-
Friday, October 01, 2010 8:43 PMCan anyone help with this error, Trying to install TFS 2010 on a 64bit Windows 2008 R2 Server. All of the verifications passed but fails at the configuration services section of the advanced install. We have disabled fips and .net 3.5 and 4.0 is installed.
[Info @20:03:41.598] +-+-+-+-+-| AddServicingResources |+-+-+-+-+-[Error @20:03:41.599] TF255184: An error occurred during operation. Message=TF255136: The data for applying the service pack or critical update could not be added to the server..[Error @20:03:41.600]Exception Message: Exception has been thrown by the target of an invocation. (type TargetInvocationException)
Exception Stack Trace: at System.RuntimeMethodHandle._InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct& signature, RuntimeType declaringType)at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)at System.Security.Cryptography.MD5.Create(String algName)at Microsoft.TeamFoundation.Admin.ServicingData.AddServicingResources(TeamFoundationRequestContext requestContext, TeamFoundationServicingService servicingService)at Microsoft.TeamFoundation.Admin.ServicingData.TryAddData(OperationContext context, TeamFoundationRequestContext requestContext)
Inner Exception Details:
Exception Message: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. (type InvalidOperationException)
Exception Stack Trace: at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
[Error @20:03:41.600] TF255248: The process applying the configuration must be terminated due to an error.[Error @20:03:41.601] TF255247: An error occurred while applying the following configuration: Microsoft.TeamFoundation.Admin.ConfigurationApplyException: TF255136: The data for applying the service pack or critical update could not be added to the server. (Exception has been thrown by the target of an invocation.) ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()--- End of inner exception stack trace ---at System.RuntimeMethodHandle._InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct& signature, RuntimeType declaringType)at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)at System.Security.Cryptography.MD5.Create(String algName)at Microsoft.TeamFoundation.Admin.ServicingData.AddServicingResources(TeamFoundationRequestContext requestContext, TeamFoundationServicingService servicingService)at Microsoft.TeamFoundation.Admin.ServicingData.TryAddData(OperationContext context, TeamFoundationRequestContext requestContext)--- End of inner exception stack trace ---at Microsoft.TeamFoundation.Admin.ErrorList.HandleError(IResult result)at Microsoft.TeamFoundation.Admin.ErrorList.Add(IResult result)at Microsoft.TeamFoundation.Admin.ServicingData.TryAddData(OperationContext context, TeamFoundationRequestContext requestContext)at Microsoft.TeamFoundation.Admin.ATInstall.PostWebInstallStuff(OperationContext context)at Microsoft.TeamFoundation.Admin.ATInstall.PostWebUpdateStuff(OperationContext context)at Microsoft.TeamFoundation.Admin.ApplicationTier.Install(OperationContext context)at Microsoft.TeamFoundation.Admin.ApplicationTier.Apply(OperationContext context)at Microsoft.TeamFoundation.Admin.ConfigurationNode.ApplyIfReady(OperationContext context)at Microsoft.TeamFoundation.Admin.LogicalTier.Apply(OperationalMode mode).- Moved by Michal Malecki MSFT Saturday, October 02, 2010 7:36 PM (From:Visual Studio Source Control and SourceSafe)
All Replies
-
Saturday, October 02, 2010 7:35 PM
Hello,
I'm moving this question to TFS setup forum
Michal Malecki TFS Version Control- Proposed As Answer by Shashi Ramaka Thursday, March 10, 2011 10:32 PM
-
Monday, October 04, 2010 8:05 AMModerator
Hello MajorAKL,
Thanks for your post. Based on your issue, I have some thought.
As the error message describes, you can’t apply the data to the service pack or critical update could not be added to the server.
Do you run the Advanced Configuration wizard on a client or server operating system? If you run this wizard on a client operating system, you cannot configure integration with a team project portal or the reporting feature of the Team Foundation Server.
In addition, to use the Advanced Configuration wizard, you must be a member of the Administrators security group on the server. If you plan to configure reporting, you must also be a member of the Administrator security group on the server that is running the SQL Server Reporting Services. If you want to plan to configure SharePoint Products, you must be a member of the Farm Administrators group on the SharePoint Products administrations site.
Hopeful it helps you, if you still have some concerns, please feel free to let me know.
Best Regards,
Vicky Song
Please remember to mark the replies as answers if they help and unmark them if they provide no help
-
Monday, October 04, 2010 12:25 PM
I am using windows server 2008 r2 using advanced configuration option. i am a member of the administrators groups. It passes all of the verification tests but it fails in that one point. Also i am using a 64 bit server.- Proposed As Answer by billb08 - MSFTModerator Thursday, October 07, 2010 12:29 AM
-
Thursday, October 07, 2010 12:29 AMModerator
Hi
Issue is similar to KB 942664
Try the following steps:
To enable FIPS compliant algorithms, follow these steps: 1. In Control Panel, double-click Administrative Tools .
2. In Administrative Tools , double-click Local Security Policy .
3. In Local Security Policy , expand Local Policies , expand Security Options , and then double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing .
4. In the System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing Properties dialog box, click the Local Security Setting tab.
5. On the Local Security Setting tab, click Enabled , and then click OK .
6. Close Local Security Policy .- Proposed As Answer by stu4231 Friday, October 15, 2010 4:09 PM
-
Thursday, October 14, 2010 9:23 PM
The above solution worked for me with one correction
The Property "System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing" must be set to Disabled not Enabled as suggested above
- Proposed As Answer by stu4231 Friday, October 15, 2010 4:10 PM
-
Wednesday, October 20, 2010 10:05 PM
I have tried setting the local policy to enabled and disabled and still have not been able to Configure. Are there any other suggestions. xeon 5530; 32bit; WindowsServer2008 standard; Sqlserver2008 standard.
[Info @20:56:51.351] +-+-+-+-+-| AddServicingResources |+-+-+-+-+-
[Error @20:56:51.355] TF255184: An error occurred during operation. Message=TF255136: The data for applying the service pack or critical update could not be added to the server..
[Error @20:56:51.358]
Exception Message: Exception has been thrown by the target of an invocation. (type TargetInvocationException)
Exception Stack Trace: at System.RuntimeMethodHandle._InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct& signature, RuntimeType declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct signature, RuntimeType declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.MD5.Create()
at Microsoft.TeamFoundation.Admin.ServicingData.AddServicingResources(TeamFoundationRequestContext requestContext, TeamFoundationServicingService servicingService)
at Microsoft.TeamFoundation.Admin.ServicingData.TryAddData(OperationContext context, TeamFoundationRequestContext requestContext)
Inner Exception Details:
Exception Message: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. (type InvalidOperationException)
Exception Stack Trace: at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
[Error @20:56:51.358] TF255248: The process applying the configuration must be terminated due to an error.
[Error @20:56:51.360] TF255247: An error occurred while applying the following configuration: Microsoft.TeamFoundation.Admin.ConfigurationApplyException: TF255136: The data for applying the service pack or critical update could not be added to the server. (Exception has been thrown by the target of an invocation.) ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct& signature, RuntimeType declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(IRuntimeMethodInfo method, Object[] args, SignatureStruct signature, RuntimeType declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.MD5.Create()
at Microsoft.TeamFoundation.Admin.ServicingData.AddServicingResources(TeamFoundationRequestContext requestContext, TeamFoundationServicingService servicingService)
at Microsoft.TeamFoundation.Admin.ServicingData.TryAddData(OperationContext context, TeamFoundationRequestContext requestContext)
--- End of inner exception stack trace ---
at Microsoft.TeamFoundation.Admin.ErrorList.HandleError(IResult result)
at Microsoft.TeamFoundation.Admin.ErrorList.Add(IResult result)
at Microsoft.TeamFoundation.Admin.OperationResult.Add(IResult result)
at Microsoft.TeamFoundation.Admin.ServicingData.TryAddData(OperationContext context, TeamFoundationRequestContext requestContext)
at Microsoft.TeamFoundation.Admin.ATInstall.PostWebInstallStuff(OperationContext context)
at Microsoft.TeamFoundation.Admin.ATInstall.PostWebUpdateStuff(OperationContext context)
at Microsoft.TeamFoundation.Admin.ApplicationTier.Install(OperationContext context)
at Microsoft.TeamFoundation.Admin.ApplicationTier.Apply(OperationContext context)
at Microsoft.TeamFoundation.Admin.ConfigurationNode.ApplyIfReady(OperationContext context)
at Microsoft.TeamFoundation.Admin.LogicalTier.Apply(OperationalMode mode). -
Wednesday, October 20, 2010 10:45 PM
I resolved this problem by toggling the switch in the registry instead of the local security policy User Iterface.
Even after disabling property "System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing"
the registry value was still 1.
-
Monday, May 16, 2011 4:09 PM
To apply the local policy changes, you have to run GPUPDATE /FORCE at the command prompt. Then, try run setup again.
-
Monday, May 16, 2011 6:03 PM
On a machine running TFS 2010 SP1 x64, open inetmgr.msc to edit localhost/tfs/web Application config of machinekey component to the following values:
Validation: SHA1
Autogenerate,IsolateApps
Encryption: 3DES
Autogenerate,IsolateApps
Restart all the application pools manually. Restart all the Web Sites manually.
Setting encryption to 3DES allows you to work with TFS 2010 on FIPS ENABLED Windows systems.
Greetings!!!
Edwin Lewitzki

