Event ID: 8214; Event Source: Windows SharePoint Services 3
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 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 Alternate Access URL for the default zone, http://servername. Review the Alternate Access mappings for this Web application at http://servername:14188/_admin/AlternateUrlCollections.aspx and consider adding http://serverip as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3" />
<EventID Qualifiers="0">8214</Event
<Level>2</Level>
<Task>807</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2010-10-08T17:
<EventRecordID>13150</Even
<Channel>Application</Chan
<Computer>servername.domai
<Security />
</System>
<EventData>
<Data>A request was made for a URL, http://serverip, 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:14188/_admin/AlternateUrlCollections.aspx and consider adding http://serverip as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854</Data>
</EventData>
</Event>
I have stoped all IIS services and found that my users were able to access server shares again. Could someone please shed some light on this for me?
Thanks
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 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 Alternate Access URL for the default zone, http://servername. Review the Alternate Access mappings for this Web application at http://servername:14188/_admin/AlternateUrlCollections.aspx and consider adding http://serverip as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows SharePoint Services 3" />
<EventID Qualifiers="0">8214</Event
<Level>2</Level>
<Task>807</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2010-10-08T17:
<EventRecordID>13150</Even
<Channel>Application</Chan
<Computer>servername.domai
<Security />
</System>
<EventData>
<Data>A request was made for a URL, http://serverip, 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:14188/_admin/AlternateUrlCollections.aspx and consider adding http://serverip as a Public Alternate Access URL if it will be used frequently. Help on this error: http://go.microsoft.com/fwlink/?LinkId=114854</Data>
</EventData>
</Event>
I have stoped all IIS services and found that my users were able to access server shares again. Could someone please shed some light on this for me?
Thanks
itgroove
You built a web application and specified a URL for it but users (some) are connecting to a URL that is not defined. You will want to "extend" your web application to include this other URL if the intended URL is not available within SharePoint, which will create the necessary alternate access mapping. Alternatively, instruct any users using an invalid path to stop doing that.
ASKER
Ok, I understand the alternate url within SharePoint, however some users are having trouble connecting to the server using its IP address, when they try connect this error pops up. The sharepoint site is only accessible via a url and not ip address and can be accessed without establishing a vpn connection to the network, which is the way I want it.
So, int.domanin.com allows me access to the sp site, which is right, but from run command \\serverip does not allow for shared folder to be accessed.
Is there a setting in IIS/SharePoint that can be set to allow access to the site only from the url and not the server's ip?
So, int.domanin.com allows me access to the sp site, which is right, but from run command \\serverip does not allow for shared folder to be accessed.
Is there a setting in IIS/SharePoint that can be set to allow access to the site only from the url and not the server's ip?
I guess the first question is why would you want to connect to the IP? The purpose of DNS/hosts is to remove the dependency on an IP which could change at some point (migration, moves, etc.) and because a name is easier to remember than an IP.
But if you are determined to point them to an IP, you are probably having an issue because another site is listening on the same port and IP (probably the 'default web site') and only 1 site can be on an IP/PORT. You need host headers (which incorporate DNS/hosts) to allow for more than one website to be hosted by the same IP.
But if you are determined to point them to an IP, you are probably having an issue because another site is listening on the same port and IP (probably the 'default web site') and only 1 site can be on an IP/PORT. You need host headers (which incorporate DNS/hosts) to allow for more than one website to be hosted by the same IP.
ASKER
Ok, I think the actual problem is being missed. The sp site I created works fine; what doesn't work is that my users can't access the file server when they have connected via vpn.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I haven't added the DNS to the VPN, I'll try add it and test. Other thing that is a tad weird is that only XP clients have this problem, on Win 7 I am able to connect to the file server without issue even with sharepoint services started.
ASKER
Ok, have configured my VPN to export DNS and am able to ping and connect to the server using the short name. Will attempt to connect on one of the clients in the same way.
ASKER
Added my DNS to the VPN address export list, works fine.