Here is another installment of list of fixes for a common Installation error. Again, while attempting the fix/ workaround mentioned in the list make sure you go thru the list and try to match the exact error you are facing as captured in the installation log file (as applicable).

Exception / Log snippet

Solution

Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center

In IIS configuration, the .asmx mappings don't haveGET, POST ] by default.
Resolution
In IIS configuration, for .asmx mappings add [ GET, POST ] manually. Then "retry" the install and it completes successfully.

More about Isapi configuration:

"Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this
error, see the Microsoft Help and Support Center."

Log snippet:
Invalid file name for file monitoring:
'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config'. Common reasons for failure include:
- The filename is not a valid Win32 file name.
- The filename is not an absolute path.
- The filename contains wildcard characters.
- The file specified is a directory.
- Access denied.
at System.Web.DirMonCompletion..ctor(DirectoryMonitor dirMon, String dir, Boolean
watchSubtree, UInt32 notifyFilter)
at System.Web.DirectoryMonitor.StartMonitoring()
at System.Web.DirectoryMonitor.StartMonitoringFile(String file,
FileChangeEventHandler callback, String alias)
at System.Web.FileChangesMonitor.StartMonitoringFile(String alias,
FileChangeEventHandler callback)
at
System.Web.Configuration.WebConfigurationHost.

StartMonitoringStreamForChanges(String streamName, StreamChangeCallback callback)
at System.Configuration.BaseConfigurationRecord.MonitorStream(String configKey,
String configSource, String streamname)
at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()
: An error occurred loading a configuration file: Invalid file name for file
monitoring: 'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config'. Common reasons
for failure include:
- The filename is not a valid Win32 file name.
- The filename is not an absolute path.
- The filename contains wildcard characters.
- The file specified is a directory.
- Access denied.
(C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config\machine.config)
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at
System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaE
rrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
at System.Web.Configuration.RuntimeConfig.get_HealthMonitoring()
at System.Web.Configuration.HealthMonitoringSectionHelper..ctor()
at System.Web.Management.HealthMonitoringManager..ctor()
at System.Web.Management.HealthMonitoringManager.Manager()
at System.Web.Management.WebBaseEvent.RaiseRuntimeError(Exception e, Object source)
at System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow, Boolean localExecute)
at System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr, HttpContext context, Exception e)-->
--.
ErrorCallingServerStatus
02/08/07 09:53:46 DDSet_Status: Process returned 2325
02/08/07 09:53:46 DDSet_Status: Found the matching error code for return value '2325' and it is: '28925'
02/08/07 09:53:46 DDSet_Error: 2325
MSI (s) (0C!2C) [10:15:13:366]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support
Center.

Disable the “Maximum used memory” property for “TFS**” application
pool. (Please see the note section, if there are no App Pools related to TFS present)
Steps:
1) Open IIS manager (inetmgr)
2) Browse to Application pools.
3) Select the AppPool property, that is in question.
4) Disable “maximum used memory” by clearing the selection box

Microsoft Visual Studio 2008 Team Foundation Server - ENU -- Error 28925.TFServerStatusValidator: The tool could not call the Team Foundation Server ServerStatus Web service."

Log snippet:

Unhandled Exception:
System.IO.FileLoadException: Unverifiable code failed policy check. (Exception from HRESULT: 0x80131402)
   at Microsoft.TeamFoundation.Common.

ExceptionFormatter.FormatExceptionForDisplay(Exception ex)
12/20/07 08:59:34 DDSet_Status: Process returned -532459699
12/20/07 08:59:34 DDSet_Error: The Commandline '"C:\DOCUME~1\EWITTE~1\LOCALS~1\Temp\TFServerStatusValidator.exe" ...' returned non-zero value: -532459699.
MSI (s) (9C!20) [08:59:36:624]: Product: Microsoft Visual Studio 2008 Team Foundation Server - ENU -- Error 32000.The Commandline '"C:\DOCUME~1\EWITTE~1\LOCALS~1\Temp\TFServerStatusValidator.exe" ...' returned non-zero value: -532459699.

Changing the trust level in the web.config files <trust level> element to any level other than Full will cause Team Foundation Server installaiton to fail with a 28925 error.

The change to the "root" web.config file causes all ASP.NET applications to attempt to run at the trust level specified.  TFSServerStatusValidator application requires Full Trust and fails if any level less than full is specified.
Resolution

Set the trust level to Full Trust to apply to Team Foundation Server Applications. 

Preferred method:
An entry can be added to the web.config file located in ([Team Foundation Program Files Folder]\Microsoft Visual Studio 2005 Team Foundation Server\Web Services) that applies only to Team Foundation Server Applications.

Add to System.web node:
<trust level="Full" originUrl="" />

Alternative:
This can also be done in the root level web.config for all .NET 2.0 services.

Details: http://support.microsoft.com/kb/949548

Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.

This error can be caused if the Team Foundation Server name is failing to resolve via DNS. This can be solved by:

1. Check the settings in internet explorer and select the option to bypass proxy server for local adresses. Tools - Internet Option - Connections - LAN Settings - Bypass proxy settings for local addresses.
OR
2. Add server name to DNS so it resolves correctly.

Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.

Log snippet: 

TFServerStatusValidator - Team Foundation Server Status Validator tool (C) Copyright 2006 Microsoft Corporation. All rights reserved.

The request failed with HTTP status 407: Proxy Authentication Required (The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. ).
ProxyAuthenticationRequired
ErrorCallingServerStatus
01/18/07 13:03:04 DDSet_Status: Process returned 2325
01/18/07 13:03:04 DDSet_Status: Found the matching error code for return value'2325' and it is: '28925'

01/18/07 13:03:04 DDSet_Error: 2325 MSI (s) (C8!A0) [13:04:17:281]: Product: Microsoft Visual Studio 2005 Team
Foundation Server (services) - ENU -- Error 28925.TFServerStatusValidator: Calling
the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.

01/18/07 13:04:17 DDSet_CARetVal: 28925
01/18/07 13:04:17 DDSet_Status: QuietExec returned 28925
01/18/07 13:04:17 DDSet_Exit: QuietExec ended
MSI (s) (C8:10) [13:04:17:328]: User policy value 'DisableRollback' is 0
MSI (s) (C8:10) [13:04:17:328]: Machine policy value 'DisableRollback' is 0
Action ended 13:04:17: InstallFinalize. Return value 3.

If you are using a proxy server in which ISA (Internet Security and Acceleration) Server for authentication.
(<http://www.microsoft.com/technet/isa/default.mspx>)

Edit the machine.config file in the
%windir%\Microsoft.NET\Framework\v2.0.50727\CONFIG folder to use the defaults from the Internet Explorer proxy, specify the proxy address, and bypasses the proxy for local access and the customer’s domain.

<configuration>
………..

<system.net>

<defaultProxy enabled="true" useDefaultCredentials="true">

<proxy
usesystemdefault="true"
proxyaddress="http://192.168.1.100:8080"
bypassonlocal="true"
/>

<bypasslist>
<add address="[a-z]+\.Domainame\.com$"/>
</bypasslist>

</defaultProxy>

</system.net>

…………

</configuration>

Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the
problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.”

Log snippet: 

MSI (s) (B8:D4) [12:18:00:437]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI18C.tmp, Entrypoint: QuietExec
06/25/07 12:18:00 DDSet_Status: LANGID: 1033
06/25/07 12:18:00 DDSet_Entry: QuietExec started
06/25/07 12:18:00 DDSet_Status: Hiding command line parameters
06/25/07 12:18:00 DDSet_Status: Commandline:
"C:\WINDOWS\TEMP\TFServerStatusValidator.exe" ...
06/25/07 12:18:00 DDSet_Status: IgnoreExitCode: 0
06/25/07 12:18:00 DDSet_Status: Silent: 0
06/25/07 12:18:00 DDSet_Status: ActionStart: 0
06/25/07 12:18:00 DDSet_Status: Cost: 0
06/25/07 12:18:00 DDSet_Status: WorkingDirectory:
06/25/07 12:18:00 DDSet_Status: HideCmdLine: 1
TFServerStatusValidator - Team Foundation Server Status Validator tool (C) Copyright 2006 Microsoft Corporation. All rights reserved.

The request failed with HTTP status 403: Forbidden.
Forbidden
ErrorCallingServerStatus
06/25/07 12:18:04 DDSet_Status: Process returned 2325
06/25/07 12:18:04 DDSet_Status: Found the matching error code for return value
'2325' and it is: '28925'
06/25/07 12:18:04 DDSet_Error: 2325
MSI (s) (B8!30) [12:18:25:062]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28925.TFServerStatusValidator: Calling the Team
Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.

06/25/07 12:18:25 DDSet_CARetVal: 28925
06/25/07 12:18:25 DDSet_Status: QuietExec returned 28925
06/25/07 12:18:25 DDSet_Exit: QuietExec ended
MSI (s) (B8:50) [12:18:25:109]: User policy value 'DisableRollback' is 0
MSI (s) (B8:50) [12:18:25:109]: Machine policy value 'DisableRollback' is 0
Action ended 12:18:25: InstallFinalize. Return value 3.

Start inetmgr (IIS manager)
Under Websites
Under Properties for all websites ->Directory Security
Under IP Address and Domain Name Restrictions->Select Edit
Enable ‘Grant Access’

 

Content by: Arunrama

Reviewed by: Lucky