Comments on: Search Server 2008: Federated sites that do not return XML http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/ Fri, 12 Mar 2010 07:58:48 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: AndrewWoody http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-1127 AndrewWoody Fri, 19 Feb 2010 18:03:59 +0000 http://21apps.co.uk/?p=69#comment-1127 You are correct the regex is not working any longer, someone commented that they planned to correct this. If I get time I will take a look. You are correct the regex is not working any longer, someone commented that they planned to correct this. If I get time I will take a look.

]]> By: dawsonweb http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-1125 dawsonweb Fri, 12 Feb 2010 14:14:16 +0000 http://21apps.co.uk/?p=69#comment-1125 I just tried this and it doesn't return any results. I think it's the regex. Can anyone confirm if it's still working? Thanks. I just tried this and it doesn't return any results. I think it's the regex. Can anyone confirm if it's still working? Thanks.

]]> By: bradgcoza http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-998 bradgcoza Thu, 13 Aug 2009 14:51:54 +0000 http://21apps.co.uk/?p=69#comment-998 @ David_Effs : There is something not 100% with that fix, it seems to use 100% of my processor and my sharepoint grinds to a halt .... @ David_Effs : There is something not 100% with that fix, it seems to use 100% of my processor and my sharepoint grinds to a halt ….

]]> By: David_Effs http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-991 David_Effs Fri, 07 Aug 2009 18:12:22 +0000 http://21apps.co.uk/?p=69#comment-991 Thanks for a great article. This regex works:<br>Regex searchPattern = new Regex("<li class=g><h3 class=r><a href="(?<link>.*?)"(.*?)>(?<title>.*?)</a>(.*?)</h3><div class="s">(?<desc>.*?)<span class=gl>(.*?)</span>"); Thanks for a great article. This regex works:
Regex searchPattern = new Regex(”<li class=g><h3 class=r><a href=”(?<link>.*?)”(.*?)>(?<title>.*?)(.*?)</h3><div class=”s”>(?<desc>.*?)<span class=gl>(.*?)</span>”);

]]> By: No federated searching of Google… » novolocus.com http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-813 No federated searching of Google… » novolocus.com Tue, 03 Mar 2009 10:05:30 +0000 http://21apps.co.uk/?p=69#comment-813 [...] best solution I can find - several suggestions of creating an intermediate web service to parse standard page requests. Which was the line I was [...] [...] best solution I can find – several suggestions of creating an intermediate web service to parse standard page requests. Which was the line I was [...]

]]> By: Allan Pedersen http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-814 Allan Pedersen Mon, 02 Mar 2009 14:28:34 +0000 http://21apps.co.uk/?p=69#comment-814 Great article, but unfortunately I haven't been able to get it working. If I test the regex in a standard .net console application it seems that the result page is not properly parsed. I guess that the source HTML for the result page has changed since this article was written. Does anyone have the new regex pattern? Great article, but unfortunately I haven't been able to get it working. If I test the regex in a standard .net console application it seems that the result page is not properly parsed. I guess that the source HTML for the result page has changed since this article was written. Does anyone have the new regex pattern?

]]> By: Tom http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-773 Tom Mon, 09 Feb 2009 13:55:57 +0000 http://21apps.co.uk/?p=69#comment-773 Connecting directly with a browser is no problem. Also I am using (for test purposes) the existing live Search Connector, which works too. So I guess there is someting wrong with the connector ... Thank you for your response! Connecting directly with a browser is no problem. Also I am using (for test purposes) the existing live Search Connector, which works too. So I guess there is someting wrong with the connector …
Thank you for your response!

]]> By: Andrew Woodward http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-772 Andrew Woodward Mon, 09 Feb 2009 13:30:09 +0000 http://21apps.co.uk/?p=69#comment-772 Tom, Have you tried to access the site http://www.google.com/search?q=test from the SharePoint server? This looks more like you network is locked down to prevent external access or has incorrect routing. Tom,

Have you tried to access the site http://www.google.com/search?q=test from the SharePoint server? This looks more like you network is locked down to prevent external access or has incorrect routing.

]]> By: Tom http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-771 Tom Mon, 09 Feb 2009 13:27:33 +0000 http://21apps.co.uk/?p=69#comment-771 Same here: No connection to Google available. Starting just the aspx itself creates the following error: No connection could be made because the target machine actively refused it 74.125.39.99:80 Any chance that you will fix this? :-O Same here: No connection to Google available. Starting just the aspx itself creates the following error:

No connection could be made because the target machine actively refused it 74.125.39.99:80

Any chance that you will fix this?
:-O

]]> By: Andrew Woodward http://www.21apps.com/sharepoint/search-server-2008-federated-sites-that-do-not-return-xml/comment-page-1/#comment-697 Andrew Woodward Wed, 07 Jan 2009 16:09:38 +0000 http://21apps.co.uk/?p=69#comment-697 My initial thoughts on this is that the response from Google has changed so the Regex is no longer working. My initial thoughts on this is that the response from Google has changed so the Regex is no longer working.

]]>