Problem Statement

Here is a common symptom for the Self-Service link in the FIM Portal for BHOLD.

Exception

System.Net.WebException ---> System.Net.WebException
  at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult) at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa.<EndGetResponse>b__9(Object sendState)
at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__1(Object sendState)
  --- End of inner exception stack trace ---
at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
 at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
BHOLD_self_service_4.png

Cause

This issue can have multiple causes:

  • If the CoreWebPath Registry (Wow64Node\Bhold\FIM\CoreWebPath) Value displays a Server Name; using an IP address seems to fix this problem for a lot of users.
  • If the CoreDomain or FIMDomain values under this same registry key are not correct
  • Check the core screen for the user attempting to access the self-service link, If the default alias value is not in the form of <domain>\<sAMAccountName>

 

BHOLD Confirmation

To confirm that the self-service link is working, you should see something similar to this:

 

Additional Information

The Application Event Log and the BHOLDRoleExchangePoint.txt file located in the BHOLD Logs folder(SP1) will typically show an error as well but in most cases, it typically shows unauthorized exception error.