Wiki  >  TechNet Articles  > 

Troubleshooting FIM 2010: WebServices MA - Failed to Update Discovery - TechNet Articles - United States (English) - TechNet Wiki

Table of Contents

Troubleshooting FIM 2010: WebServices MA - Failed to Update Discovery

Table of Contents


OVERVIEW / PURPOSE / GOAL

My goal of this wiki is to provide knowledge and information on the WebServices Connector for FIM 2010.  This particular wiki is going to cover information on the Web Services Configuration Tool, and an error that was encountered, and what was done to troubleshoot it, and what the resolution was here.

PROBLEM STATEMENT

In this case we were attempting to create a new configuration file to connect to the PeopleSoft 9.1 web service.  We enter the address information into the Web Service window, as well as the user information on the second screen and then click next to initiate the discovery of the web service.  During the discovery, we receive an error stating "Failed to Update Discovery". 

TROUBLESHOOTING

To troubleshoot the issue we enabled verbose logging on the WebServices Connector for FIM 2010

WEBSERVICES VERBOSE LOGGING
2012-07-18T11:22:00 [2840:972] Error   - Workspace:DiscoveryForSave : An exception was thrown while running a WSDL import extension: System.ServiceModel.Channels.TransportBindingElementImporter
Error: Invalid URI: The hostname could not be parsed.
--------- Outer Exception Data ---------
Message: An exception was thrown while running a WSDL import extension: System.ServiceModel.Channels.TransportBindingElementImporter
Error: Invalid URI: The hostname could not be parsed.
Exception root Exception type: System.ServiceModel.Description.WsdlImporter+WsdlImportException
Source: System.ServiceModel
Stack Trace:    at System.ServiceModel.Description.WsdlImporter.ImportWsdlPort(Port wsdlPort, ErrorBehavior errorBehavior)
   at Microsoft.IdentityManagement.MA.WebServices.WebServices.ServiceDescriptionProvider.GenerateEndpoints(ServiceContractGenerator generator)
   at Microsoft.IdentityManagement.MA.WebServices.WebServices.WsdlCompiler.Compile(String assemblyFileName, String configurationFileName)
   at Microsoft.IdentityManagement.MA.WebServices.ConfigurationTool.Misc.Workspace.DiscoveryForSave(Boolean compile)
Target Site: ImportWsdlPort
 --------- Inner Exception Data ---------
 Message: An exception was thrown while running a WSDL import extension: System.ServiceModel.Channels.TransportBindingElementImporter
Error: Invalid URI: The hostname could not be parsed.
 Exception root Exception type: System.InvalidOperationException
 Source: System.ServiceModel
 Stack Trace:    at System.ServiceModel.Description.WsdlImporter.CallImportEndpoint(WsdlEndpointConversionContext endpointConversionContext)
   at System.ServiceModel.Description.WsdlImporter.ImportWsdlPort(Port wsdlPort, ErrorBehavior errorBehavior)
 Target Site: CallImportEndpoint
  --------- Inner Exception Data ---------
  Message: Invalid URI: The hostname could not be parsed.
  Exception root Exception type: System.UriFormatException
  Source: System
  Stack Trace:    at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at System.ServiceModel.Description.WsdlImporter.WSAddressingHelper.ImportAddress(Port wsdlPort)
   at System.ServiceModel.Channels.TransportBindingElementImporter.ImportAddress(WsdlEndpointConversionContext context, TransportBindingElement transportBindingElement)
   at System.ServiceModel.Description.WsdlImporter.CallImportEndpoint(WsdlEndpointConversionContext endpointConversionContext)
  Target Site: CreateThis

CAUSE

Discovered that the default port 80 was not being used.

RESOLUTION

Added the correct port to the address information, and everything worked successfully.

Here is an illustration ( sample ) of what it should look like with the port number.

ADDITIONAL INFORMATION

FIM LANDING PAGE: Resource Wiki Page Index
How to enable verbose logging for the WebServices Connector