none
Event ID 8214

    Question

  • Hi all

    My event log is full of errors with ID 8214
    I am not finding any good solutions

    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://ipadress, which has not been configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone, http://serverName. Review the Alternate Access mappings for this Web application at http://servername:portnumber/_admin/AlternateUrlCollections.aspx and consider adding http://ipadress as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854.

    Any one else that has fixed this issue?
    Any tips will be most helpful for me :)

    Regards

    Monday, October 05, 2009 9:08 AM

All replies

  • Hi,

    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

    feedback if this dosen't help
    Best Regards, Ammar MCT
    Monday, October 05, 2009 9:38 AM
  • Hi Ahmed

    I have seen that. A corrupt database is not the issue here. I found that this error with Event ID 8214 is generated when I try to access the sharepoint site by using a url with ip - address, for instance http://123.343454.343

    However, I have another issue which I don't understand why I get. It's a warning that says

    Event code: 3005

    Event message: An unhandled exception has occurred.

    Event time: 03.10.2009 16:54:29

    Event time (UTC): 03.10.2009 14:54:29

    Event ID: 6e3c6eb98c7442ac889859c1501642ef

    Event sequence: 1571

    Event occurrence: 3

    Event detail code: 0

     

    Application information:

    Application domain: /LM/W3SVC/305724665/Root-1-128990346551917484

    Trust level: WSS_Medium

    Application Virtual Path: /

    Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\80\

    Machine name: machine name

     

    Process information:

    Process ID: 8040

    Process name: w3wp.exe

    Account name: Domain\domainadmin

     

    Exception information:

    Exception type: HttpException

    Exception message: Invalid viewstate.

     

    Request information:

    Request URL:

    <here I get a lot of the public url's>


    Any ideas about this one? :-)


    Regeards


    Monday, October 05, 2009 10:07 AM
  • Hi,

    you said this happened when you try to access the sharepoint site by using a url with ip - address
    what if you try to access the sharepoint site by using a url like http://yourportalname
    also please give us a brief of your current sharepoint topology and version
    and if you have applied any SP recently
    Best Regards, Ammar MCT
    Monday, October 05, 2009 10:21 AM
  • Hi

    I don't get this error when accessing the site using url http://portalname

    I am using MOSS 2007 SP 2, a farm with single web front end server

    Also, today I got the error in event log, without having used the http://ipadress.


    Regards
    Tuesday, October 06, 2009 9:15 AM
  • According to http://support.microsoft.com/kb/829743/en-us, this issue can often be caused by leaving the validationKey attribute set to AutoGenerate in the Machine.config file. Instead, you must set the value of the validationKey attribute to a fixed string that is shared by all the machines on the Web farm.

     

    Please refer to http://msdn.microsoft.com/en-us/library/ms998288.aspx for more about validationkey.

    Tuesday, October 06, 2009 10:04 AM
    Moderator
  • Hi GuYuming

    Mt validationkey is allready set to "AutoGenerate": 

     <machineKey validationKey="AutoGenerate,IsolateApps"

    Are there any other things to look at?


    Regards
    Sunday, October 11, 2009 5:12 PM
  • The problem may be caused by the “AutoGenerate” setting. Try manual generated validation key as described in http://support.microsoft.com/kb/312906/en-us  and check if the  problem is solved. The machine key setting could be something like this:

     

    <machineKey validationKey="21F090935F6E49C2C797F69BBAAD8402ABD2EE0B667A8B44EA7DD4374267A75D7AD972A119482D15A4127461DB1DC347C1A63AE5F1CCFAACFF1B72A7F0A281B"

                decryptionKey="261F793EB53B761503AC445E0CA28DA44AA9B3CF06263B77"

                validation="SHA1"/>

     

     

    The article http://support.microsoft.com/kb/829743/en-us lists several possible causes for the error “Invalid viewstate”. Since you had mentioned that you only have one web front end in your server farm, the section “Set the validationKey attribute if you are running in a Web farm” in the article may not apply to your case. However, the section “Determine whether the problem is caused by worker process recycling” may apply.

    Monday, October 12, 2009 1:50 AM
    Moderator
  • Hi

    Are you sure about this? I am very scared to do something with the machine.config as I don't know what it does. My problem seems to be related with mapping. If I instead of using http http://localhost:22417 use the correct address of http://servername:22417, i will not get the problem, but I will get it each time I use localhost or ip-adress in the url.


    Regards.

    Monday, October 12, 2009 8:06 AM
  • I think you had posted two issues in this thread:

    1.      errors with ID 8214. The resolution to this issue is stated clearly in the error information you had posted (related with mapping as you think): A request was made for a URL, http://ipadress, which has not been configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone, http://serverName. Review the Alternate Access mappings for this Web application at http://servername:portnumber/_admin/AlternateUrlCollections.aspx and consider adding http://ipadress as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854.

     

    2.      However, I have another issue which I don't understand why I get” in your second post. My replies are all about this issue.  I am not 100% sure. Just give the result of my study based on your error message for your reference. Please let us know if this would solve your issue.

    Monday, October 12, 2009 8:39 AM
    Moderator
  • Hi

    Sorry for being so messy, and thanks for taking time to answer :)
    Well, I have still have problems with event id 8214, and the other problem regarding warning og Event code: 3005 seems to have dissapeared for the moment, but I am sure it will come up again soon :)

    Each day I still keep getting errors on event id 8214, even when I don't access the site using localhost or ip - address. It's very confusing. Any tips are most appreciated :)

    Regards

    Monday, October 12, 2009 10:37 AM
  • “Each day I still keep getting errors on event id 8214, even when I don't access the site using localhost or ip – address”

     

    One possible reason can be that the content source of search crawler is setup with localhost or IP. You can check the content source setup in Shared Services Administration:-> Search Administration-> Content sources -> Edit Content Source ->start addresses 

    Tuesday, October 13, 2009 1:24 AM
    Moderator
  • Hi GuYuming

    I crawl using this as content source:

    http://servername/
    sps3://servername/

    I thought I was supposed to crawl using internal url. Is it wrong?


    Regards
    Tuesday, October 13, 2009 6:52 PM
  • I think it’s OK to crawl using internal URL.

     

    Since you get Event ID 8214 every day even if you don’t access the site using localhost or IP, I think there may be some visit such as web service call to your site with Localhost or IP.

     

    You can check all your web site visit in IISlog (http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/ab7e4070-e185-4110-b2b1-1bcac4b168e0.mspx ).

    Wednesday, October 14, 2009 1:58 AM
    Moderator
  • Hi

    I still did not get rid of this error. Checking the error in the log file it tells me this:


    10/18/2009 16:10:03.42  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\infoindexuser to local group 2. 
    10/18/2009 16:10:03.42  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\infoindexuser to local group 0. 
    10/18/2009 16:10:03.43  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\siteAdmin to local group 2. 
    10/18/2009 16:10:03.43  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\siteAdmin to local group 0. 
    Monday, October 19, 2009 9:05 AM
  • Hi

    I still did not get rid of this error. Checking the error in the log file it tells me this:


    10/18/2009 16:10:03.42  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\infoindexuser to local group 2. 
    10/18/2009 16:10:03.42  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\infoindexuser to local group 0. 
    10/18/2009 16:10:03.43  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\siteAdmin to local group 2. 
    10/18/2009 16:10:03.43  OWSTIMER.EXE (0x0620)                    0x0D1C Windows SharePoint Services    Topology                       0 Medium   Adding Domain\siteAdmin to local group 0. 

    I think the message you just posted is not error message, just ordinary SharePoint trace log which logs its internal activity.

    Tuesday, October 20, 2009 3:20 AM
    Moderator
  • Yeah, it's from the log, but still I have not get rid of Event ID 8214 :(
    Monday, October 26, 2009 12:33 PM