none
Event Viewer Error - Event ID : 8214

    Question

  • Hi
    in event viewer i have too many error with event id : 8214 with following details :

    Source : Windows SharePoint Services
    Event ID : 8214
    Category : Topology
    User : N/A
    Computer : SERVER

    Description :
    The description for Event ID ( 8214 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: A request was made for a URL,
    http://myInternetIPAddress, which has not been configured in Alternate Access Mappings.  Some links may point to the Alternate Access URL for the default zone, http://server.  Review the Alternate Access mappings for this Web application at http://server:100/_admin/AlternateUrlCollections.aspx and consider adding http://myInternetIPAddress as a Public Alternate Access URL if it will be used frequently

    The sharepoint & AD is on the same machine (server)

    can anybody help me to workaround this problem ?
    thanks

    this is my Signature
    Thursday, August 27, 2009 9:53 PM

Answers

All replies

  • Did you verify the Alternate Access Mappings? Also you may want to check that you have a DNS entry for the AAM...
    Thursday, August 27, 2009 9:57 PM
  • Did you verify the Alternate Access Mappings? Also you may want to check that you have a DNS entry for the AAM...

    Thanks Nikole
    can u give me more comments ? beacuse i'm new to AAM & DNS conception.
    thanks in advance
    this is my Signature
    Thursday, August 27, 2009 10:34 PM
  • Your AAM should match your DNS entry for the site. The AAM set up link can be found in Central Admin under Operations then under Global Configuration.  

    DNS - IP: 10.111.XXX.XXX - http://mysite.com

    AAM - http://mysite.com

    Simple as that....
    Monday, August 31, 2009 4:27 PM
  • hi,
    i have the same problem and my AAM and DNS are ok.

    do you  have any ideas?

    in other post, a uses has said to recriate the database of engine search (moss 2007 search service) and it will fix the problem, but its is much radical for my application.. =(

    thanks

    Raphael
    Wednesday, September 02, 2009 12:04 PM
  • Looks like this issue has been resolved here

    http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/29c1a681-5996-4e71-ada7-3abc4fe772b5?ppud=4

    See if this helps or post back.
    Alpesh Nakar Blog: http://alpesh.nakars.com/blog | Twitter: @alpesh SharePoint Resources: http://www.justsharepoint.com | Twitter @justsharepoint
    Thursday, September 03, 2009 2:45 AM
  • Hi,

    I received the same error described above.  And I really didn't want to do a reinstall.  And I was able to solve this issue by recreating a new application pool within IIS and moving the applications that existed on the original cental admin application pool into the new app pool.  You would also have to change the cental admin site config (within IIS) to point to the new application pool. 

    I am not sure if this solution will work for all MOSS configurations but it did resolve my issue. 

    Monday, November 09, 2009 9:59 PM