This Site and This List Scopes Not Working in MOSS 2007

Hi Guys,
Long time didn't post useful stuff in our site. I had to work on many projects and documentations, so that didn't have a chance to get hold with sharepointlk blog. Sorry for that..

Recently I'm assigned to a project for Intranet on SharePoint 2007. I managed to deploy all the components of MOSS 2007 on Windows Server 2008 using SharePoint 2007 SP2 setup.

While working on the site and adding web parts, I discovered that I couldn't do search within the site or list in particular sub site or the list.

Was struggling and going through various blogs and resolved the issue, so I thought of share the workaround with you guys...

My environment;
• Windows Server 2008 32 bit
• MOSS 2007 with SP2
• Installed Arabic language Pack (MOSS 2007 & WSS 3.0)
• Arabic Language Pack SP (MOSS 2007 & WSS 3.0)
• Latest Cumulative update for MOSS 2007 & WSS 3.0
(June Cumulative Update (CU)
Released June 29, 2010
This update provides hotfixes for Windows SharePoint Services 3.0 (KB 983311) and Office SharePoint Server 2007 (KB 983310))


After having installed above mentioned software and hotfixes, I have created the collaboration website and few sub sites with in the same web application

Configured alternative access mapping for my sever name and was able to access successfully. When access the SharePoint web site being in the windows sever 2008, it is keeping prompting me for user name and password and finally its gives me blank white page but I can access the website using the local machine name and it succeeded without any errors. I could access the web site from client machines using AAM name and was successful.

So I ignored accessing the web site from windows sever 2008.

Configured the search and started the crawl, I got access denied error for the web site I created in SharePoint even though the default content access account has full rights to the web site, the error is;

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (The item was deleted because it was either not found or the crawler was denied access to it.)




Then I change the content source from AAM name to local machine name, crawl was success and I could do the search using central search site but I couldn’t do the search using “This Site & This List”.



Was going through some blogs and MS articles, found below workaround to solve the issue for above mentioned “Access Denied” error and search no result when you search using “This Site & This List”

To resolve the issues, you need to disable the loop back check in the registry mentioned in below article
http://support.microsoft.com/kb/896861

That fixed the issue I had and I was able to crawl the website using AAM and could search “This Site & This List” Search

Hope above information is useful

Cheers !!!

2010 First 5 key Improvements….............................

1. No timeouts - So yes, in the previous 2007 in place upgrade, there would be failures based on timeouts related to things like large lists.

2. Continue on failure – Think of it as on error resume next. In the previous if you ran into something missing or something unexpected upgrade would fail.

3. Resume – After a failure you will now be able to resume where you left off.

4. Error Logging – So the error logging is much better. It’s in it’s own file so that definitely makes it much easier to troubleshoot and identify issues.

5. Better status output – new stsadm command localupgradestatus which allows you to see the progress of the upgrade after the configuration wizard has been run. In fact the new UI in Central Admin, Upgrade Status page in 2010 will also allow you to see the database upgrade status.

FQDN and SharePoint 2007 Server Name

Dear Guys,

Recently I was working on a project where it involves 17 SharePoint 2007 Server Farm. As I did the architecture of the solution, my client wants to keep their entire internet facing Web Front End SharePoint Servers on DMZ. We managed to install the WFEs on DMZ with additional domain controller on DMZ which has one way trust for internal network DC. Microsoft NLB had configured for these SharePoint Web Front End Servers in DMZ.

Everything was working smoothly until I configure the Search Service for the farm.

Scenario is;

Web Front Ends (DMZ Zone)
Index Server (Intranet Zone)
Central Admin Server (Intranet Zone)
Database Server - Cluster (Intranet Zone)

When I access the website search, it was giving me the following error;

Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.

I have checked the services for search and was running and search service was started as well. I recreated the search and did the full crawl again but no luck. Even I recreated the SharedService associated with it and still no luck.

I just the browsed the web site using machine name which has the web application hosted from a client which is residing intranet network and search was working perfectly. when I browse the website using named configured in NLB, search is not working and giving the same error message as Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.


I logged into one of the web front end servers and tried the search, still it is giving me the same error message in search result page.

Went through "Event Viewer" and discovered some warning messages saying that the Web Front End Server (in DMZ) could not contact the INDEX server located in intranet network. In my firewall, I have opened all the ports from WFEs to SharePoint Server Farm Servers.

When did the PING command from WFEs server to INDEX Server located in intranet network by MACHINE NAME (Example IndexServer), I got request time out as reply.

BUT

When I did the PING command from WFEs Server to INDEX Server located in intranet network by FQDN NAME (Example IndexServer.domain.com), I got reply successfully.

DISCOVERED

I added the INDEX Server name in all the WFEs' host file as NetBIOS name for its IP Address HURRAY !!!!! Search was working smoothly as expected.

CONCLUSION

SharePoint 2007 Technologies Servers does not identify machine with FQDN names and it only recognize with NetBIOS name of Farm servers.

Hope above information would help you guys when you all into DMZ related deployment for SharePoint 2007 Farm.

Cheers !!!!