Yeah we do. In fact I think you created it. :)
But nothing has changed in this regard and it's only affecting apps within the
one SSP.
I had changed the association for some webapps within this SSP and moved them
to a new one (for our anonymous sites). But some of the legacy webapp URLs are
still present in the Scopes page. I can't see any way to get rid of them.
Also the errors in the logs were for some very wacky URLs which I've never seen
before - {app_url}/content/blah, {mysite_url}//site$$$people.
I just reset all crawled content and did a full crawl. It took about 5 seconds
and reported a single error for each application.
https://{ app_url}
Error in the Site Data Web Service. (The Web application at https://{ app_url}
could not be found. Verify that you have typed the URL correctly. If the URL
should be serving existing content, the system administrator may need to add a
new request URL mapping to the intended application.)
AAM settings are all default and have not changed. And all sites can be
browsed. Either someone's screwed with the firewall settings or something very
weird has happened.
Regards,
Paul
--
Online Developer/Administrator,
ICT Projects Team
CEO Sydney
From: [email protected] [mailto:[email protected]] On Behalf Of
Paul Turner
Sent: Monday, 15 November 2010 8:29 PM
To: ozMOSS
Subject: RE: Can't access site collection scopes
Do you have a custom master applied to the system pages... I have seen lots of
issues lately where they can cause issues.
Regards,
Paul Turner
MCT, MCPD: Enterprise, MCSD, MCDBA, MCTS, MSF, Microsoft vTSP
Consultant
M: 0412 748 168
A: 66 Henley Beach Road, Mile End SA 5031
E: [email protected]<mailto:[email protected]> W:
www.dws.com.au<http://www.dws.com.au/>
This email and any files transmitted with it are confidential and are only for
the use of the person to whom they are addressed. If you are not the intended
recipient you have received this email in error and are requested to delete it
immediately. Any opinion expressed in this e-mail may not necessarily be that
of DWS Pty Ltd.
Please consider the environment before printing this email.
From: [email protected] [mailto:[email protected]] On Behalf Of
Paul Noone
Sent: Monday, 15 November 2010 3:35 PM
To: ozMOSS
Subject: RE: Can't access site collection scopes
No, it's got "=site" but you pointed me in the right direction. It's not ALL
sites. Just the ones associated with our primary SSP. And all the search errors
point to apps associated with SSP as well.
Looks like a rebuild. :\
From: [email protected] [mailto:[email protected]] On Behalf Of
James Boman
Sent: Monday, 15 November 2010 3:52 PM
To: ozMOSS
Subject: RE: Can't access site collection scopes
When you go to view the search scopes page, does the URL have "?mode=ssp" on
the end?
From: [email protected] [mailto:[email protected]] On Behalf Of
Paul Noone
Sent: Monday, 15 November 2010 2:47 PM
To: ozMOSS
Subject: Can't access site collection scopes
Has nyone seen this before or have any idea what might be causing it?
This error occurs when trying to view the Search Scopes
(_layouts/viewscopes.aspx) for any web app in the farm. The temp path
highlighted seems very dodgy indeed.
8<--------
Exception of type
'Microsoft.SharePoint.Portal.WebControls.UnknownModeException' was thrown. at
Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchAdminPageBase.ErrorHandler(Object
sender, EventArgs e)
at System.Web.UI.TemplateControl.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP._layouts_viewscopes_aspx.ProcessRequest(HttpContext context) in
c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET
Files\root\a4a225be\d0aa5016\App_Web_viewscopes.aspx.2a428413.so90lgc5.0.cs:line
0
at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
Kind regards,
Paul Noone
---------------------------------------------------
Online Developer/Administrator
Information Communication and Technology
Catholic Education Office, Sydney
p: (02) 9568 8461
f: (02) 9568 8483
e: [email protected]<mailto:[email protected]>
w: http://www.ceosyd.catholic.edu.au/
_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
