Error Id 8214
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Event ID 8214 SharePoint > SharePoint Legacy Versions - Setup, Upgrade, Administration and Operations Question 0 Sign in to vote Hi allMy event log is full of errors with ID 8214I 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 Reply | Quote All replies 0 Sign in to vote Hi,Looks like this issue has been resolved herehttp://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/29c1a681-5996-4e71-ada7-3abc4fe772b5?ppud=4feedback if this dosen't helpBest Regards, Ammar MCT Monday, October 05, 2009 9:38 AM Reply | Quote 0 Sign in to vote Hi AhmedI 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 ur
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check https://social.technet.microsoft.com/Forums/sharepoint/en-US/81dd4b71-0651-4c27-99bf-90d5e468d09a/event-id-8214?forum=sharepointadminlegacy the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 8214 Source: Windows SharePoint Services 3 Source: Windows SharePoint Services 3 Maintenance: Recommended tasks for Microsoft SharePoint Server maintenance Type: Error Description:A request was made for a URL http://192.168.11.5 which has not been http://www.eventid.net/display-eventid-8214-source-Windows%20SharePoint%20Services%203-eventno-10634-phase-1.htm configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone http://server_name. Review the Alternate Access mappings for this Web application at http://server_name:10042/_admin/AlternateUrlCollections.aspx and consider adding http://192.168.7.23 as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/LinkId=114854 English: Request a translation of the event description in plain English. Concepts to understand: What is causing the The description for Event ID ( ) in Source ( . ) cannot be found ? Comments: Anonymous In my case, I used the information listed on EV100044 to fix this problem (in many cases, the description of this event is not displayed properly, instead you get the The description for Event ID ( 8214 ) in Source ( Windows SharePoint Services 3 ) cannot be found. ... message). x 10 Private comment: Subscribers only. See example of private comment Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Login here! Recommend Us Quick Tip Connect
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help https://www.experts-exchange.com/questions/26530778/Event-ID-8214-Event-Source-Windows-SharePoint-Services-3.html Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Event ID: 8214; Event Source: Windows SharePoint Services 3 Want to Advertise Here? Solved Event ID: 8214; Event Source: error id Windows SharePoint Services 3 Posted on 2010-10-08 Windows Server 2008 MS SharePoint 1 Verified Solution 8 Comments 3,887 Views Last Modified: 2012-05-10 I have run into an interesting problem, we interesting to me. We have a 2008 R2 DC setup and a Sharepoint intranet which is accessible externally using a cname. I allow my users to connect remotely error id 8214 via openvpn to access data on the sever, but my users are unable to access any shares. Upon further investigation I found this error in the event log: Log Name: Application Source: Windows SharePoint Services 3 Date: 2010/10/08 07:04:52 PM Event ID: 8214 Task Category: Topology Level: Error Keywords: Classic User: N/A Computer: SERVERNAME.domain.com Description: The description for Event ID 8214 from source Windows SharePoint Services 3 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: A request was made for a URL, http://serverIP, which has not been configured in Alternate Access Mappings. Some links may point to the Alterna