none
Error when accessing BHOLD Self Service (HTTP status 401: Unauthorized) RRS feed

  • Question

  • Hi,

    I have started looking at the BHOLD suite and installed it on a server running FIM2010R2. The installation of the BHOLD suite seemed to be completed without problems and the BHOLD service are up and running under the B1User account and all BHOLD products can be started with my Administrator user.

    However when I click on the link "BHOLD Self Service" in the FIM portal, the silverlight plugin starts and after a short while shows the following error message:

    "UserViewModel.GetAuthenticatedUserCompleted 'http://IMCDBS301A:5151/BHOLD/RoleExchangePoint/BHOLDRoleExchangePoint.svc'
    System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]
    Arguments: NotFound
    Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.1.10329.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]
    Arguments: NotFound
    Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.1.10329.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
       at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
       at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClass5.<EndGetResponse>b__4(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)

    When I look in Application log (event log) I see:
    Error in function call GetInfo fn:objectsbyattributep1:IDMDEMO\Administratorp2:3p3:25 Exception The request failed with HTTP status 401: Unauthorized. StackTrace at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at BholdSvrProxy.BHOLDsvc.B1ScriptService.GetInfo(String functionName, String parameter1, String parameter2, String parameter3) in d:\_Bld\10\16\Sources\main\src\samples\BHOLD\2011 R2\Common\BholdSvrProxy\Web References\BHOLDsvc\Reference.cs:line 700 at BholdSvrProxy.BHOLDproxy.GetInfo(String fn, String p1, String p2, String p3) in d:\_Bld\10\16\Sources\main\src\samples\BHOLD\2011 R2\Common\BholdSvrProxy\BHOLDproxy.cs:line 115

    Note that IDMDEMO\Administrator is my FIM and Domain administrator that I use in the portal.

    I have ensured that the webhome containing 'http://IMCDBS301A:5151/BHOLD/RoleExchangePoint/BHOLDRoleExchangePoint.svc' has windows authentication enabled and that the user B1User is member of the BHOLDApplicationGroup and ISS_IUSRS groups.

    I would really appreciate if someone is able to point me in the right direction so I get the BHOLD Self Service working.

    thanks and best regards
    Søren Aamand

    Wednesday, August 29, 2012 7:35 AM

Answers

  • Hi,

    I had a similar issue with my install. Make sure you review the information from the release note.

    For me it was the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\FIM\CoreWebPath, I replaced the server name in the value with the IP address of the server.

    Hope this helps.

    Pat...

    • Marked as answer by Søren Aamand Friday, August 31, 2012 8:00 AM
    Wednesday, August 29, 2012 1:01 PM

All replies

  • Hi,

    I had a similar issue with my install. Make sure you review the information from the release note.

    For me it was the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\FIM\CoreWebPath, I replaced the server name in the value with the IP address of the server.

    Hope this helps.

    Pat...

    • Marked as answer by Søren Aamand Friday, August 31, 2012 8:00 AM
    Wednesday, August 29, 2012 1:01 PM
  • Could it be that the spn of the servername is already registered by the service account of FIM? A workaround that worked in the past was to remove the spn from the fim service account and adding it to the b1user service account.

    I've also seen it happening that the IPv6 hostname was different from the IPv4 hostname which causes the HTTP status 401: Unauthorized issue.

    I hope this helps.

    Regards,

    Remy


    Remy de Vries - BHOLD Expert - Technical Consultant - Elephant Security


    Wednesday, August 29, 2012 2:03 PM
  • I've seen this too and it was fixed by Patrick's suggestion - replace any server names in the Registry with the IP address, just in case.

    Dave Nesbitt | Architect | Oxford Computer Group

    Thursday, August 30, 2012 8:14 PM
  • Hi,

    I've fixed the problem, which was a wrong password in: BHold/FIM CorePassword. After it was fixed, the problem is gone :-)

    Akos Regi
    Consultant
    Oxford Computer Group GmbH



    Friday, August 31, 2012 7:33 AM
  • Thanks a lot. Patrick's suggestion fixed the issuet. I'm really excited to dig further into BHOLD.
    Also thanks to you other guys for your contributions. I really appreciate it.

    best regards

    Søren Aamand


    Friday, August 31, 2012 8:03 AM
  • Hi

    I found out that if the Default Alias in the BHOLD Portal is only the accountName (as the TLG describes it in step 10 Management Agent Attribute Flows) you cannot logon because of exactly this error.

    The Default Alias has to be "DomainName\sAMAccountName".

    Henry

    Friday, June 14, 2013 2:16 PM
  • We are experiencing the exact same problem now. We tried changing the registry key to ip, but it didn`t work. Anybody have any ideas?

    Regards, Remi www.iamblogg.com

    Wednesday, January 15, 2014 10:06 PM
  • I solved the problem by doing a reinstall of BholdFIMIntegration (uninstall, new install). I had to patch the registry key again with the IP.

    Wednesday, January 15, 2014 11:50 PM