The description for Event ID 9001 from source TFS Services cannot be found.
I ran into this issue after updating a patch related to TFS. The Team Foundation Administration console reported errors on all the * URL: <<Error retrieving the details>>. I suspected that there should be some connectivity issues related to database, thus my next target was to dig in further for details both in event viewer and the IIS logs. I could see that there were errors being logged in event viewer continuously with the details as seen below:
The description for Event ID 9001 from source TFS Services cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 2/21/2011 8:58:55 AM
Machine: VM2-TFS
Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129427358458749059
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
Process Name: w3wp
Process Id: 3680
Thread Id: 1976
Account name: [DOMAIN\USERNAME]Detailed Message: Application Request Processing Started
Server Version = Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Service Account = PREPRO\administrator
Machine Name = VM2-TFSException Message: TF246017: Team Foundation Server could not connect to the database. Verify that the server that is hosting the database is operational, and that network problems are not blocking communication with the server. (type DatabaseConnectionException)
Exception Stack Trace: at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.TranslateException(Int32 errorNumber, SqlException sqlException, SqlError sqlError)
at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.TranslateException(SqlException sqlException)
at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.MapException(SqlException ex, QueryExecutionState queryState)
at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.Execute(ExecuteType executeType, CommandBehavior behavior)
at Microsoft.TeamFoundation.Framework.Server.ExtendedAttributeComponent.ReadDatabaseAttribute(String attributeName)
at Microsoft.TeamFoundation.Framework.Server.DatabaseConnectionValidator.ValidateDatabaseInstanceStamp(String configConnectionString, Guid configInstanceId)
at Microsoft.TeamFoundation.Framework.Server.DatabaseConnectionValidator.ValidateApplicationConfiguration(String configConnectionString, Guid configInstanceId, List`1 sqlInstances, String analysisInstance, String analysisDatabaseName, Boolean ignoreAnalysisDatasourceUpdateErrors, Boolean autoFixConfiguration, Boolean fullValidation, DatabaseVerificationDatabaseTypes continueOnMissingDatabaseTypes)
at Microsoft.TeamFoundation.Framework.Server.ApplicationServiceHost..ctor(Guid instanceId, String connectionString, String physicalDirectory, String plugInDirectory, String virtualDirectory, Boolean failOnInvalidConfiguration)
at Microsoft.TeamFoundation.Framework.Server.TeamFoundationApplication.AttemptStart()
After digging further to the worker process logs, I tried looking further into IIS website configuration settings. Ultimately it turned out to be the Application pool configuration – which had got messed up. After running the patch, it had somehow modified the app pool configuration to point to ASP.NET 2.0 instead of ASP.NET 4.0. Reverting back to 4.0 did the trick – of course after an iisreset.
