Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
After install FIM Portal 'service not available'; This page has encountered a critical error

Answered After install FIM Portal 'service not available'; This page has encountered a critical error

  • Wednesday, October 03, 2012 12:33 PM
     
     
    Sign In to Vote
    0

    I've just installed FIM 2010 R2 ( along with the massive number of pre-reqs sucessfully - I believe).

    I've cannot login to FIM Portal.

    After logging into the FIM server (where all FIM services were installed) - as the system admin or FIM portal admin, I get the following stack trace when pointing to http://<server>/identityManagement/default.aspx

    [WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]
       Microsoft.SharePoint.ApplicationRuntime.SafeModeSettings.EnsureSafeModeSettingsInitialized() +25420967
       Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous) +27616569
       Microsoft.SharePoint.SPRequestManager.GetContextRequest(SPRequestAuthenticationMode authenticationMode) +268
       Microsoft.SharePoint.Administration.SPFarm.get_RequestAny() +173
       Microsoft.SharePoint.SPRegionalSettings.get_GlobalInstalledLanguages() +27
       Microsoft.SharePoint.Administration.SPTemplateFileSystemWatcher.RefreshInstalledLocales() +60
       Microsoft.SharePoint.Administration.SPTemplateFileSystemWatcher.Initialize() +69
       Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.System.Web.IHttpModule.Init(HttpApplication app) +931
       System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +480
       System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +336
       System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +350
       System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +382

    [HttpException (0x80004005): This page has encountered a critical error. Contact your system administrator if this problem persists.]
       System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11335894
       System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88
       System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +4355316

    EVENT LOGS:

    Application and Services Logs: FIM/FIM agent logs are empty

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          10/3/2012 8:00:02 AM
    Event ID:      8306
    Task Category: Claims Authentication
    Level:         Error
    Keywords:     
    User:          domain\user
    Computer:      IDMAN01-A
    Description:
    An exception occurred when trying to issue security token: Could not connect to http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843. .
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
        <EventID>8306</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>47</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-03T12:00:02.229292700Z" />
        <EventRecordID>28255</EventRecordID>
        <Correlation ActivityID="{073FFD7D-17D6-493E-96E0-D950AC0EB97E}" />
        <Execution ProcessID="1752" ThreadID="1856" />
        <Channel>Application</Channel>
        <Computer>IDMAN01-A</Computer>
        <Security UserID="S-1-5-21-3377398617-3690804955-2338930767-1797" />
      </System>
      <EventData>
        <Data Name="string0">Could not connect to http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843. </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          10/3/2012 8:00:02 AM
    Event ID:      2138
    Task Category: Health
    Level:         Warning
    Keywords:     
    User:          domain\user
    Computer:      IDMAN01-A
    Description:
    The SharePoint Health Analyzer detected a condition requiring your attention.  The Security Token Service is not available.
    The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.
    Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=160531".

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
        <EventID>2138</EventID>
        <Version>14</Version>
        <Level>3</Level>
        <Task>8</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-03T12:00:02.230269300Z" />
        <EventRecordID>28256</EventRecordID>
        <Correlation ActivityID="{073FFD7D-17D6-493E-96E0-D950AC0EB97E}" />
        <Execution ProcessID="1752" ThreadID="1856" />
        <Channel>Application</Channel>
        <Computer>IDMAN01-A.ngdev.net</Computer>
        <Security UserID="S-1-5-21-3377398617-3690804955-2338930767-1797" />
      </System>
      <EventData>
        <Data Name="string0">The Security Token Service is not available.
    The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.
    Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=160531".
    </Data>
      </EventData>
    </Event>

    AND FROM THE LOG FOLDER 14 UNDER SHAREPOINT

    http://go.microsoft.com/fwlink/?LinkID=142683".  203e5ce4-83f9-47d2-80f5-30d05674d7c6

    10/03/2012 08:00:01.26 OWSTIMER.EXE (0x06D8)                   0x0CE4 SharePoint Foundation         Monitoring                    b4ly High    Leaving Monitored Scope (Health Rule Execution: Microsoft.SharePoint.Administration.Health.ServiceIsNotRunning, Microsoft.SharePoint.Health, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c). Execution Time=1.06689537357402 203e5ce4-83f9-47d2-80f5-30d05674d7c6

    10/03/2012 08:00:01.27 OWSTIMER.EXE (0x06D8)                   0x0CE4 SharePoint Foundation         Monitoring                    b4ly High    Leaving Monitored Scope (Executing Hourly All Microsoft SharePoint Foundation Timer rules.). Execution Time=1111.74604593601 203e5ce4-83f9-47d2-80f5-30d05674d7c6

    10/03/2012 08:00:01.27 OWSTIMER.EXE (0x06D8)                   0x0CE4 SharePoint Foundation         Monitoring                    b4ly Medium  Leaving Monitored Scope (Timer Job hourly-all-sptimerservice-health-analysis-job). Execution Time=1113.34624931381 203e5ce4-83f9-47d2-80f5-30d05674d7c6

    10/03/2012 08:00:02.22 OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fsq7 High    Request for security token failed with exception: System.ServiceModel.EndpointNotFoundException: Could not connect to

    http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843.  ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:32843     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 ... 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.22* OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fsq7 High    ...timeout, Exception& exception)     --- End of inner exception stack trace ---     at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)     at System.Net.HttpWebRequest.GetRequestStream()     at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()     --- End of inner exception stack trace ---    Server stack trace:      at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()     at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)     at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Dispatcher.RequestC... 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.22* OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fsq7 High    ...hannelBinder.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)     at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)     at Microsoft.IdentityModel.Protocols.W... 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.22* OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fsq7 High    ...STrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo) 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.22 OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         8306 Critical An exception occurred when trying to issue security token: Could not connect to

    http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843. . 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.23 OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fg9z Medium  SecurityTokenServiceNotAvailable: Error checking BPA rule: System.ServiceModel.EndpointNotFoundException: Could not connect to

    http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843.  ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:32843     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResul... 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.23* OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fg9z Medium  ...t, Int32 timeout, Exception& exception)     --- End of inner exception stack trace ---     at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)     at System.Net.HttpWebRequest.GetRequestStream()     at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()     --- End of inner exception stack trace ---    Server stack trace:      at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()     at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)     at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Dispatcher... 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.23* OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fg9z Medium  ....RequestChannelBinder.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)     at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)     at Microsoft.IdentityModel.Pr... 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.23* OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Claims Authentication         fg9z Medium  ...otocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)     at Microsoft.SharePoint.Administration.Health.SecurityTokenServiceNotAvailable.Check(). 073ffd7d-17d6-493e-96e0-d950ac0eb97e

    10/03/2012 08:00:02.23 OWSTIMER.EXE (0x06D8)                   0x0740 SharePoint Foundation         Health                        2138 Warning The SharePoint Health Analyzer detected a condition requiring your attention.  The Security Token Service is not available.  The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.  Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "

    http://go.microsoft.com/fwlink/?LinkID=160531".  073ffd7d-17d6-493e-96e0-d950ac0eb97e

    Help.

    10/03/2012 08:00:01.26 OWSTIMER.EXE (0x06D8)                   0x0CE4 SharePoint Foundation         Health                        2137 Critical The SharePoint Health Analyzer detected an error.  One or more services have started or stopped unexpectedly.  The following services are managed by SharePoint, but their running state does not match what SharePoint expects: SPAdminV4.  This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface.  If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.  SharePoint was unable to automatically repair this error.    To stop or start a service managed by SharePoint, use the SharePoint service management interface in the SharePoint Central Administration Site.  If a service has crashed, restart the service manually on the affected servers by running... 203e5ce4-83f9-47d2-80f5-30d05674d7c6

    10/03/2012 08:00:01.26* OWSTIMER.EXE (0x06D8)                   0x0CE4 SharePoint Foundation         Health                        2137 Critical ... "net start [service name]" from a command prompt. For more information about this rule, see "


    • Edited by Osho27 Wednesday, October 03, 2012 12:42 PM update
    •  
     

All Replies

  • Wednesday, October 03, 2012 12:56 PM
     
     
    Sign In to Vote
    0

    For clarity, I'd like to add that I did not set up certs on this IIS/SP instance: as I interpretted the instructions as that was an optional step: See below.  Could that be the cause?  WIll get a cert this morning and try to see what happens.

    Implement Secure Sockets Layer for FIM Portal

    We highly recommend that you implement Secure Sockets Layer (SSL) on the FIM Portal server to secure the traffic between the client and server computers.

    To implement SSL with a certificate from an existing internal CA

    1. Open IIS Manager on the FIM Portal server.

    2. Click the local computer name.

    3. Click Server Certificates.

    4. Click Create Certificate Request.

    5. For Common Name, enter the name of the server.

    6. Click Next, then Next.

    7. Save the file to any location. You will need to access this location in subsequent steps.

    8. In Windows Internet Explorer, browse to https://servername/certsrv. Replace servername with the name of the server that is issuing certificates.

    9. Click Request a new Certificate.

    10. Click Submit an Advanced Request.

    11. Click Submit a Certificate Request by using a base-64-encoded.

    12. Paste the contents of the file that you saved in the previous step.

    13. From Certificate Template, select Web Server.

    14. Click Submit.

    15. Save the Certificate to your Desktop.

    16. In IIS Manager, click Complete Certification Request.

    17. Point IIS Manager to the certificate you just saved to the Desktop.

    18. For Friendly name, type the name of the server.

    19. Click Sites, and then select Sharepoint – 80.

    20. Click Bindings, and then click Add.

    21. Select https.

    22. For certificate, select the one that has the same name as the server (this is the certificate that you just imported).

    23. Click OK.

    24. Remove the HTTP binding.

    25. Click SSL Settings, and then check Require SSL.

    26. Save the settings.

    27. Click Start, click Administrative Tools, and then click Sharepoint 3.0 Central Administration.

    28. Click Operations, and then click Alternate Access Mappings.

    29. Click http://servername.

    30. Change http://servername to https://servername, and then click OK.

    31. Click Start, Run, enter iisreset, and then click OK.

     
  • Wednesday, October 03, 2012 1:39 PM
     
     
    Sign In to Vote
    2

    After installing SharePoint, were you able to get into SharePoint Default Site (http://<servername or fqdn> ? If not, you should do SharePoint troubleshooting first and after that trouble any errors getting to FIM Portal. The FIM Portal lives on top of SharePoint, so if SP is not running, FIM Portal won't.

    Try to access SP with the user that installed SP or the user that you specified as owner (primary or secondary owner). If no access, start troubleshooting there. Lokos like youre trying to access using http://localhost ? try with servername instead and check your alternate access mappings as well.

    If you having huge problem and its a fresh installation I suggest to uninstall FIM Portal/Service and SharePoint and reinstall. And do check that you can get to SP Default site before installing FIM.

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

     
  • Wednesday, October 03, 2012 5:11 PM
     
     
    Sign In to Vote
    0

    Thanks Soren... yes, the default site :80 was working and after looking throught sharepoint per your suggestion, I turned on token services and fixed a type in the web.config - and the default :80 site is up and running and I'm gettting a FIM error now:

    When trying to log in as my admin user account, or the portal admin account I see:

    UNABLE TO PROCESS YOUR REQUEST - PLEASE CONTACT YOUR HELP DESK OR SYS ADMIN

    Include this information when contacting your help desk or system administrator.
    Error processing your request: The server was unwilling to perform the requested operation.
    Reason: The requester of this operation is invalid.
    Attributes:
    Correlation Id: 52a12198-0043-4898-bf8a-ae7906f4b0f4
    Request Id:
    Details: The requestor’s identity was not found.

    The event log states the admin account is not found, nor is the portal account underwhich the product was installed.  Odd.

    Microsoft.ResourceManagement.Service: Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: IdentityIsNotFound

    Any thoughts?

    many thanks!!

     
  • Wednesday, October 03, 2012 5:22 PM
     
     Answered
    Sign In to Vote
    1

    Make sure that the account that you're trying to access the FIM Portal/Service exists in the portal/service with has at least the following attributes -

    1) AccountName

    2) DomainName

    3) ObjectSID

    and preferrably also DisplayName. If not, you're unable to access the portal. Be default only the account used to install FIM Service has access permissions to the portal/service.

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    • Marked As Answer by Osho27 Wednesday, October 03, 2012 5:38 PM
    •  
     
  • Wednesday, October 03, 2012 5:22 PM
     
     
    Sign In to Vote
    1
    Also, if SP was "broken" when installing FIM, you may want to uninstall/reinstall the FIM Service if possible...

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

     
  • Wednesday, October 03, 2012 5:43 PM
     
     
    Sign In to Vote
    0

    I missed the memo that stated only the FIM Service account (the account used to install) has access permissions.  That was the problem.  Looks like everything is up and running at this point. Time for snapshot.

    Thank you Soren!!

     
  • Wednesday, January 02, 2013 11:35 AM
     
     
    Sign In to Vote
    0

    Make sure that the account that you're trying to access the FIM Portal/Service exists in the portal/service with has at least the following attributes...

    What exactly do you mean by this? How can I make sure the account exists in Portal/Service - and add it if it does not?

    I think I am facing the same problem as OP.

    Thanks in advance.

    / Klaus

    ---Sig---

     
  • Wednesday, January 02, 2013 2:25 PM
     
     
    Sign In to Vote
    1
    Are you having problems just getting FIM up and running (accessing the Portal for the first time) or after already having it up, then loosing access after synchronization steps, etc?
     
  • Wednesday, January 02, 2013 2:31 PM
     
     
    Sign In to Vote
    0

    I have the Sync stuff up and running, and sharepoint is also working, but I cannot access the Portal (http://sharepointbox/identitymanagement), get the same error you described.

    So I was wondering where it is I need to give access to my current account for it to work with portal?

    ---Sig---

     
  • Wednesday, January 02, 2013 2:54 PM
     
     
    Sign In to Vote
    1

    You might want to verify that the account has SharePoint permissions. Log on as SP Administrator. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration. This will bring up the SharePoint Central Administration in Internet Explorer. On the left, click Application Management. This may bring up a Credentials box. If so, enter the following text for user name and the password, and then click OK. Now the Application Management page will appear. Under SharePoint Site Management, click Site Collection Administrators. This will bring up the Site Collection Administrators page. Under Primary site collection administration, try adding the account you want to logon as.

     
  • Wednesday, January 02, 2013 3:01 PM
     
     
    Sign In to Vote
    1
    Also, it is ONLY the account used for installing the FIM Service that initially has permissions to access the FIM Portal/Service. Did you allow Authenticated Users to access SharePoint during installation?

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

     
  • Thursday, January 03, 2013 1:10 PM
     
     
    Sign In to Vote
    0

    I removed and reinstalled FIM Service and Portal - and now it works. I suspect I had left out the "Allow authenticated users to access sharepoint" during installation as suggested by Søren.

    Thanks for the help. :)

    ---Sig---