Hi, Yesterday we reinstalled our FIM virtual machines from scratch. One VM for AD; and another one for SQL, WSS and FIM. We followed the guidance from Technet (http://technet.microsoft.com/en-us/library/ff512685%28WS.10%29.aspx) and (http://technet.microsoft.com/en-us/library/ff512686%28WS.10%29.aspx). We tried to open the FIM Portal, and once again got the 'Service not available' error message. We then enabled detailed stack tracing and the message now says the following: Server Error in '/' Application. -------------------------------------------------------------------------------- The remote name could not be resolved: 'http' Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Net.WebException: The remote name could not be resolved: 'http' Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [WebException: The remote name could not be resolved: 'http'] System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) +1003 System.Net.HttpWebRequest.GetRequestStream() +23 System.ServiceModel.Channels.WebRequestHttpOutput.GetOutputStream() +124 [EndpointNotFoundException: There was no endpoint listening at http://http/ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.] System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +10258154 System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +539 System.ServiceModel.Description.IMetadataExchange.Get(Message request) +0 Microsoft.ResourceManagement.WebServices.MetadataClient.Get(String dialect, String identifier) +236 Microsoft.ResourceManagement.WebServices.Client.SchemaManagerImplementation.RefreshSchema() +68 Microsoft.ResourceManagement.WebServices.ResourceManager.get_SchemaManager() +150 Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(String typeName, LocaleAwareClientHelper localePreferences, ContextualSecurityToken securityToken) +35 Microsoft.IdentityManagement.WebUI.Controls.ConfigurationModelBase.RetrieveResources(String type, String filter, List`1 attributes) +168 [ServerDownException: Error connecting to server] Microsoft.IdentityManagement.WebUI.Controls.ConfigurationModelBase.RetrieveResources(String type, String filter, List`1 attributes) +1171 Microsoft.IdentityManagement.WebUI.Controls.PortalUIConfigurationModel.RetrievePortalUIConfiguration() +269 Microsoft.IdentityManagement.WebUI.Controls.PortalUIConfigurationModel.get_PortalUI() +118 Microsoft.IdentityManagement.WebUI.Controls.PortalUIConfigurationModel.get_BrandingLeftImageUrl() +16 Microsoft.IdentityManagement.WebUI.Controls.BrandBar.get_BrandTable() +117 Microsoft.IdentityManagement.WebUI.Controls.BrandBar.CreateChildControls() +32 System.Web.UI.Control.EnsureChildControls() +146 System.Web.UI.Control.PreRenderRecursiveInternal() +61 System.Web.UI.Control.PreRenderRecursiveInternal() +224 System.Web.UI.Control.PreRenderRecursiveInternal() +224 System.Web.UI.Control.PreRenderRecursiveInternal() +224 System.Web.UI.Control.PreRenderRecursiveInternal() +224 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3394 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927

when u install, u must have specified http://hostname instead of just "hostname" IIRC, it's in the Microsoft.ResourceManagement.Service.exe.config file inside program filesThe FIM Password Reset Blog http://blogs.technet.com/aho/

hi, "when u install, u must have specified http://hostname instead of just "hostname"" are you referring to the SQL, WSS or FIM installation? and which installation step are specifically referring to? thanks,

hi, "when u install, u must have specified http://hostname instead of just "hostname"" are you referring to the SQL, WSS or FIM installation? and which installation step are specifically referring to? thanks,

when u install FIMPortal, u are asked for FIMService's hostname, u used http://xxx instead of just xxx to fix that open C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.config and look for "resourcemanagementclient". Mine is like <resourceManagementClient resourceManagementServiceBaseAddress="http://xxx:5725" timeoutInMilliseconds="60000" />

nTony, that seemed to have changed the problem - I now cannot log into the portal at all, it prompts me for authentication and eventually get a HTTP Error 401. the user I am using is Domain Administrator, and the user is part of the Farm Admins in Sharepoint and Site Collection Administrators I have reset IIS and also restarted the entire machine next question regarding the actual setup of FIM - I have been following this guide: http://technet.microsoft.com/en-us/library/ff512686(WS.10).aspx If you look at the "FIM Portal" installation section - which step stipulates that I have to type in the machine name WITHOUT the 'http://' ? thank you

nTony, that seemed to have changed the problem - I now cannot log into the portal at all, it prompts me for authentication and eventually get a HTTP Error 401. the user I am using is Domain Administrator, and the user is part of the Farm Admins in Sharepoint and Site Collection Administrators I have reset IIS and also restarted the entire machine next question regarding the actual setup of FIM - I have been following this guide: http://technet.microsoft.com/en-us/library/ff512686(WS.10).aspx If you look at the "FIM Portal" installation section - which step stipulates that I have to type in the machine name WITHOUT the 'http://' ? thank you

The guide says: 1. For the FIM service: In Configure FIM Service and Portal – Configure connection to the FIM Service, type the name of the server or the alias that the clients should use to contact the FIM Service For the Portal: On the FIM Service server address page, type the name of the server hosting the FIM Service. This should be the same server name or alias used during the FIM Service installation. It says to provide the "...name of the server or the alias..." twice. So if you follow it to the word you have to provide something like "fimsvc.contoso.com". "fimsvc" might be the name of your FIM Service server, or like I did, it might be a DNS alias. 2. As for the first time load which takes a minute, this is normal and is caused by the way IIS has to load several assemblies after an application pool recycle. 3. As for accessing the Portal, make sure you use the user which actually intalled the FIM Service binaries. Besides that, you can also do this: On the Configure FIM Service and Portal – Configure security changes configured by setup, to allow clients to contact the Web service interface, select Open ports 5725 and 5726 in firewall This will make sure you don't really need much permissions in sharepoint. If you installed the FIM Service with user X, and afterwards you log on with user Y (which is a domain admin), user Y will still get errors. Domain Admin membership gives you zero permissions in the portal http://setspn.blogspot.com

The guide says: 1. For the FIM service: In Configure FIM Service and Portal – Configure connection to the FIM Service, type the name of the server or the alias that the clients should use to contact the FIM Service For the Portal: On the FIM Service server address page, type the name of the server hosting the FIM Service. This should be the same server name or alias used during the FIM Service installation. It says to provide the "...name of the server or the alias..." twice. So if you follow it to the word you have to provide something like "fimsvc.contoso.com". "fimsvc" might be the name of your FIM Service server, or like I did, it might be a DNS alias. 2. As for the first time load which takes a minute, this is normal and is caused by the way IIS has to load several assemblies after an application pool recycle. 3. As for accessing the Portal, make sure you use the user which actually intalled the FIM Service binaries. Besides that, you can also do this: On the Configure FIM Service and Portal – Configure security changes configured by setup, to allow clients to contact the Web service interface, select Open ports 5725 and 5726 in firewall This will make sure you don't really need much permissions in sharepoint. If you installed the FIM Service with user X, and afterwards you log on with user Y (which is a domain admin), user Y will still get errors. Domain Admin membership gives you zero permissions in the portal http://setspn.blogspot.com

Thanks Thomas for the quick response. I just RESETIIS, and the Portal is working again...not really understand why 2 previous resets and a reboot did not help, but glad it appears to be working again :-) about this line (for future installations)- this implies that I must NOT insert "HTTP://" before the name of the server, correct? "It says to provide the "...name of the server or the alias..." twice. So if you follow it to the word you have to provide something like "fimsvc.contoso.com". "fimsvc" might be the name of your FIM Service server, or like I did, it might be a DNS alias." And to keep things simple for now I have been only using one account for everything (installing, configuring and administering the Portal) and that is the fabrikam\administrator account (domain, enterprise and local admin account).

Thanks Thomas for the quick response. I just RESETIIS, and the Portal is working again...not really understand why 2 previous resets and a reboot did not help, but glad it appears to be working again :-) about this line (for future installations)- this implies that I must NOT insert "HTTP://" before the name of the server, correct? "It says to provide the "...name of the server or the alias..." twice. So if you follow it to the word you have to provide something like "fimsvc.contoso.com". "fimsvc" might be the name of your FIM Service server, or like I did, it might be a DNS alias." And to keep things simple for now I have been only using one account for everything (installing, configuring and administering the Portal) and that is the fabrikam\administrator account (domain, enterprise and local admin account).

Indeed, you do not need to insert HTTP:// as Anthony suggested.http://setspn.blogspot.com

Indeed, you do not need to insert HTTP:// as Anthony suggested.http://setspn.blogspot.com

awesome ! thank you will add this in to my growing 'personal' install and config file for FIM :-) thank you for everyone's help once again !

on another note, the above solution to the original problem worked for about 10 minutes...then it kept on prompting me for login on every single link in the Portal, and eventually threw up a 401 error. Going to reinstall everything, again.

Did you followed everything in the "Before you begin" (http://technet.microsoft.com/en-us/library/ff512685(WS.10).aspx) section? Most of those steps aren't just best practice, they're are required.http://setspn.blogspot.com