Alternative access mappings have not been configured: http://toolbarqueries.google.com
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Hello,
Do you have a solution for this warning? Would I really have to add the URL to AAM in SharePoint to make this go away?
Event ID: 8059
Task Category: Configuration
Level: Warning
Keywords:
User: NT AUTHORITY\IUSR
Description:
Alternate access mappings have not been configured. Users or services are accessing the site http://server.domain.com with the URL http://toolbarqueries.google.com. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL http://toolbarqueries.google.com as an AAM response URL. For more information, see: http://go.microsoft.com/fwlink/?LinkId=114854"/>
Source: Microsoft-SharePoint Products-SharePoint Foundation
Hello,
Do you have a solution for this warning? Would I really have to add the URL to AAM in SharePoint to make this go away?
Event ID: 8059
Task Category: Configuration
Level: Warning
Keywords:
User: NT AUTHORITY\IUSR
Description:
Alternate access mappings have not been configured. Users or services are accessing the site http://server.domain.com with the URL http://toolbarqueries.google.com. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL http://toolbarqueries.google.com as an AAM response URL. For more information, see: http://go.microsoft.com/fwlink/?LinkId=114854"/>
Gregory Miller
why would you not? Did you have a concern about it?
As the error telling you, you need to create an alternate access mapping. Check this thread for more information:
http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/aea5a5c7-761b-4c49-89df-d313d52f1ee7
Hope it helps.
http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/aea5a5c7-761b-4c49-89df-d313d52f1ee7
Hope it helps.
I am familiar with what it is and it will solve the warning message. OR you can just ignore the warning which are just informational. The only reason you would have to do this is if you have some permissions tied back to a specific URL or in the case where an external user is getting a 404 error because SharePoint is including the internal URI in a link. Most things this will not be an issue but in customizations and 3rd party applications, it could get messy.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We have 3 SharePoint servers. All three are in stand alone farms. I am thinking this is a rogue DNS setting. There are many other AAM warnings with odd URLs showing up in the Event logs. I want to warnings to stop to stop the warnings as these are no real resolutions.
I am also thinking this maybe causing the 404 not found messages on some sites on the other 2 servers. At first, you get a 404 not found, and then wait 10 seconds and then the site on the other servers comes up with no problems.
I am also thinking this maybe causing the 404 not found messages on some sites on the other 2 servers. At first, you get a 404 not found, and then wait 10 seconds and then the site on the other servers comes up with no problems.
If I understand you correctly, you are hosting these with a SharePoint hosing company? If this is the case, you are probably getting hit from client computers the former tenant(s) of the IP address you have assigned to the server you currently occupy. If this is the case, you will probably never be rid of the warnings as you cannot possibly control computers of unknown geographic location.
If they are all coming from the same IP, you might be able to ask the hosting company if they can block them. Just a thought.
If I am misunderstanding about your hosing situation, please ignore these comments.
If they are all coming from the same IP, you might be able to ask the hosting company if they can block them. Just a thought.
If I am misunderstanding about your hosing situation, please ignore these comments.
ASKER
The 3 SharePoint servers are in house.
Could it be a DNS problem? People are trying to get to the SharePoint site, but somehow the web request is using the wrong URL, so when IIS on the SharePoint server receives this request, it does not know what to do with it? Therefore, SharePoint throws an error. There are many of these odd AAM messages in the event log with odd URL requests. It seems internet traffic and these web site requests are going to the SharePoint server. Sometimes, I see 404 not found messages on the SharePoint sites. So, it seems AAM errors and 404 not found messages are related?
I am going in the right direction where this problem may be?
Could it be a DNS problem? People are trying to get to the SharePoint site, but somehow the web request is using the wrong URL, so when IIS on the SharePoint server receives this request, it does not know what to do with it? Therefore, SharePoint throws an error. There are many of these odd AAM messages in the event log with odd URL requests. It seems internet traffic and these web site requests are going to the SharePoint server. Sometimes, I see 404 not found messages on the SharePoint sites. So, it seems AAM errors and 404 not found messages are related?
I am going in the right direction where this problem may be?
ASKER
Update: I have discovered that my PC when I open a SharePoint site that the error (warning) occurs. It seems to happen for the first time I open the site, or when I do a IISReset on the server and then open a site, the AAM warning appears. After that, it does not occur again, until I do a IISReset. When opening the site, there are 3 of the same warnings.
I do have the Google Toolbar on my IE 10.
When I click on this links http://toolbarqueries.google.com it resolves to www.google.com.
So, I don't know what is going on.
I do have the Google Toolbar on my IE 10.
When I click on this links http://toolbarqueries.google.com it resolves to www.google.com.
So, I don't know what is going on.