次の方法で共有

ForeFront Identity Manager: HostId is not registered

  • [アーティクル]

Issue: you see the following exception in the event log. this gets logged every 5 seconds:

.Net SqlClient Data Provider: System.Data.SqlClient.SqlException: HostId is not registered
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at Microsoft.ResourceManagement.Data.DataAccess.RetrieveWorkflowDataForHostActivator(Int16 hostId, Int16 pingIntervalSecs, Int32 activeHostedWorkflowDefinitionsSequenceNumber, Int16 workflowControlMessagesMaxPerMinute, Int16 requestRecoveryMaxPerMinute, Int16 requestCleanupMaxPerMinute, Boolean runRequestRecoveryScan, Boolean& doPolicyApplicationDispatch, ReadOnlyCollection`1& activeHostedWorkflowDefinitions, ReadOnlyCollection`1& workflowControlMessages, List`1& requestsToRedispatch)

Resolution: Restart Forefront Identity Manager Synchronization Service (or restart computer). this will re-create the missing HostId

Thanks to Scott Cheney (Microsoft) for the resolution!

Comments

  • Anonymous
    April 28, 2010
    Restarting the computer did not seem to add the HostID entry as I still get these errors, and the User Profile Sync service will not start.  Is there a way to manually register the HostID
  • Anonymous
    May 12, 2010
    i am not aware of that. you probably need to reset your profile sync service. let me know if you need directions for that.
  • Anonymous
    May 28, 2010
    I have the same issue with missing HostId and restart did not do the trick of creating a new id. How can this be done in another way?
  • Anonymous
    June 03, 2010
    I have the same behaviour,It's happening when starting the SharePoint User Profile Synchronization Service.And even after restarting Service / Machine, and also reinstalling everything I still get those messages.Any help would be fully appreciated.Many thanks.Etienne
  • Anonymous
    June 06, 2010
    The comment has been removed
  • Anonymous
    June 09, 2010
    HelloI'm having the same problem (hostid is not registered)... I restarted both, the FIM Sync Service and the server but still have the same problem.Any idea?
  • Anonymous
    June 09, 2010
    The comment has been removed
  • Anonymous
    June 18, 2010
    Hi,I have the same problem, has anyone solved this? Restart of the machine did not help.I have also done the suggested test with "$directoryEntry = new-object -typename System.DirectoryServices.DirectoryEntry("WinNT://somedomain/user")", but the command worked fine so that should not be the issue.Thanks,Mikael
  • Anonymous
    June 23, 2010
    RebootRestart Forefront Identity Manager Synchronization ServiceRestart Forefront Identity Manager ServiceAt least it worked for me!
  • Anonymous
    June 24, 2010
    I have rebootet, but after that the Forefront services are stopped, and according to technet these should not be started manually?
  • Anonymous
    June 27, 2010
    The comment has been removed
  • Anonymous
    June 30, 2010
    The comment has been removed
  • Anonymous
    October 11, 2010
    Our problem was solved when we changed the network configurations (disable IPv6 and added the gateway for our dedicated network card) and added the SQL alias. We had VS2010 installed on the server which told us that there is problem with owstimer.exe. we debugged it with VS2010 and it told that there are problems with network (and/or proxy).One way more to solve this.