Alternate Access Mappings MOSS 2007
1 WFE to 1 SQL BE. DNS has been configured to resolve the host name of the SPP server to a friendly name; however, resolution still seems to take some time and there are numerous Event IDs 8214 referenceing both the server name and the friendly name:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 8214
Date: 3/20/2012
Time: 6:07:48 PM
User: N/A
Computer: SERVER NAME
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://<servername>, which has not been configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone, http://<friendly name>. Review the Alternate Access mappings for this Web application at http://<servername:port>/_admin/A
In some instances it's the same error only the server name and friendly name are reversed in the error.
I'm at a loss as to how to configure AAMs here. This SPP is only for Intranet/Extranet purposes for the local LAN and across a VPN to a remote site.
Any assistance would be greatly appreciated.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 8214
Date: 3/20/2012
Time: 6:07:48 PM
User: N/A
Computer: SERVER NAME
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://<servername>, which has not been configured in Alternate Access Mappings. Some links may point to the Alternate Access URL for the default zone, http://<friendly name>. Review the Alternate Access mappings for this Web application at http://<servername:port>/_admin/A
In some instances it's the same error only the server name and friendly name are reversed in the error.
I'm at a loss as to how to configure AAMs here. This SPP is only for Intranet/Extranet purposes for the local LAN and across a VPN to a remote site.
Any assistance would be greatly appreciated.
ASKER
tedbilly,
Want to make sure I understand you correctly. When you say "original server: port setting" are you speaking about port 80 in IIS? The SPP server is currently running on 2003 Enterprise with IIS6. I created a web app to use port 80 instead of using the default. Now, when the server was originally deployed everyone used the host name of the server until someone said that we can't and that's bad (understandably), so there was an entry made in DNS which now points the server name to a freindly name. How should AAMs be configured when all the clients on the network use the friendly name which points to the server name in DNS?
Thanks for your time.
Want to make sure I understand you correctly. When you say "original server: port setting" are you speaking about port 80 in IIS? The SPP server is currently running on 2003 Enterprise with IIS6. I created a web app to use port 80 instead of using the default. Now, when the server was originally deployed everyone used the host name of the server until someone said that we can't and that's bad (understandably), so there was an entry made in DNS which now points the server name to a freindly name. How should AAMs be configured when all the clients on the network use the friendly name which points to the server name in DNS?
Thanks for your time.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm off site this week, but can try this remotely in the evening and will try it ASAP! I will get back you and my results. Thank you.
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've requested that this question be closed as follows:
Accepted answer: 0 points for d_sherwood2000's comment #37772959
for the following reason:
Based upon the advice I was given. AAMs can affect all adresses in SharePoint, not just the default web site. The errors for this question regarded the web address for the central admin site. I took the advice of the contributor to this question and applied it to the Central Admin site, had it run over 12 hours and the "Topology" errors ceased.
Accepted answer: 0 points for d_sherwood2000's comment #37772959
for the following reason:
Based upon the advice I was given. AAMs can affect all adresses in SharePoint, not just the default web site. The errors for this question regarded the web address for the central admin site. I took the advice of the contributor to this question and applied it to the Central Admin site, had it run over 12 hours and the "Topology" errors ceased.
If the expert advice led to the solution then points should be awarded.
If yes, did you remove the original server:port settings from the default installations? MOSS 2007 doesn't handle that very well. You can hide the original settings but don't remove them.