Tuesday 6 April 2010

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.

Sunday 4 April 2010

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 !!!!