Service Unavailable

You receive a "Service Unavailable" error message when you browse a Windows SharePoint Services 2.0 Web site
Cause:-
This issue may occur if the application pool for the virtual server is configured incorrectly in Microsoft Internet Information Services (IIS) 6.0. This issue may occur if one or more of the following conditions are true:
-The application pool is not running.
-The application pool account uses an incorrect password.
-The application pool account is not a member of both the IIS_WPG group and the STS_WPG group on the server.

Resolution:-
To resolve this problem, follow these steps:

1.Verify that the application pool is configured for the virtual server. The default application pool is MSSharePointPortalAppPool.

Follow these steps to determine the application pool that the virtual server is using:
-Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
-Expand ServerName, expand Web Sites, right-click the virtual server, and then click Properties.
-Click the Home Directory tab.The application pool that is configured for the virtual server is listed in the Application pool box.
-Click OK.

2.Verify that the password for the application pool account is correct. IIS does not automatically poll password changes in Active Directory directory service. If the application pool account is a domain account, and the password expires, you may receive the error message that is described in the "Symptoms" section of this article after a new password is specified for the account.

Follow these steps to verify that the password for the application pool account is correct:
-In Internet Information Services (IIS) Manager, expand Application Pools.
-Right-click the application pool that is configured for the virtual server (for example, right-click MSSharePointPortalAppPool), and then click Properties.
-Click the Identity tab.
-In the Password box, type the password of the application pool account that is listed in the User name box, and then click OK.
-In the Confirm Password dialog box, type the password again, and then click OK.

3.Verify that the application pool account is a member of both the IIS_WPG group and the STS_WPG group on the server:
Use one of the following methods as appropriate to your situation:
-If Windows SharePoint Services 2.0 is installed on a member server:
-Click Start, point to Administrative Tools, and then click Computer Management.
-Expand Local Users and Groups, and then expand Users.
-Right-click the account that is used by the application pool for the virtual server, and then click Properties.
-Click the Member of tab.

Verify that both IIS_WPG and STS_WPG appear in the Member of list. If one or both groups are not listed, add the IIS_WPG group, the STS_WPG group, or both groups (as appropriate) to the list.
If Windows SharePoint Services 2.0 is installed on a domain controller:
-Start Active Directory Users and Computers.
-Expand Users.
-Right-click the account that is used by the application pool for the virtual server, and then click Properties.
-Click the Member of tab.

Verify that both IIS_WPG and STS_WPG appear in the Member of list. If one or both groups are not listed, add the IIS_WPG group, the STS_WPG group, or both groups (as appropriate) to the list.

-Restart IIS to recycle the application pools:
-In Internet Information Services (IIS) Manager, right-click ServerName, point to All Tasks, and then click Restart IIS.
-Click Restart Internet Information Services on ServerName, and then click OK.

Refferances:-
http://support.microsoft.com/kb/823552
http://technet.microsoft.com/windowsserver/sharepoint/bb267377.aspx

Configure usage reporting

Usage reporting is very useful for managing complex site hierarchies with many sites, a large number of page hits, and a large number of search queries, and it is recommended that the service be enabled for deployments of complex site hierarchies. For less complex deployments, usage reporting might not be necessary. It is also possible to disable the service temporarily to conserve resources when other those resources are needed for other processes.

To configure usage reporting, a farm administrator must first enable Windows SharePoint Services usage logging for the farm that hosts the Web application containing the SSP. The SSP administrator enables and configures the usage reporting service. Then, site collection administrators can activate the reporting feature to enable usage reports on the site collection.

Enable Windows SharePoint Services usage logging

Before you can enable usage reporting in a SSP, you must first enable Windows SharePoint Services usage logging for the farm hosting the Web application containing the SSP.

Use the following procedure to enable usage logging for the farm.

Enable usage logging for the farm

1)   On the Central Administration home page, click Operations.

2)   On the Operations page, in the Logging and Reporting section, click Usage analysis processing.

3)   On the Usage Analysis Processing page, in the Logging Settings section, select Enable logging.

4)   Type a log file location and number of log files to create.

5)   In the Processing Settings section, select Enable usage analysis processing, and then select a time to run usage processing.

6)   Click OK.

Enable usage reporting

1)   On the SSP home page, in the Office SharePoint Usage Reporting section, click Usage reporting.

2)   On the Configure Advanced Usage Analysis Processing page, in the Processing Settings section, click Enable advanced usage analysis processing.

3)   In the Search Query Logging section, select Enable search query logging.

4)   Click OK.

5)   Activate usage reporting

After usage reporting is enabled for the SSP, site collection administrators must activate the reporting feature. Until the reporting feature is activated on a site collection, usage reports are not available.

Use the following procedure to activate the reporting feature.

1)   On the Site Actions menu, click Site Settings.

2)   On the Site Settings page, in the Site Collection Administration section, click Site collection features.

3)   On the Site Collection Features page, click the Activate button for the Reporting feature.

Monitor usage reporting

Usage reporting can be viewed in several places:

1)   Site administrators, including administrators of the SSP administration site, can view usage reporting for their site by clicking Site usage reports in the Site Administration section of the Site Settings page.

2)   Site collection administrators can view usage reporting by clicking Site collection usage reports in the Site Collection Administration section of the Site Settings page.

3)   Site collection administrators for the SSP administration site can view a usage summary by clicking Usage summary in the Site Collection Administration section of the Site Settings page.

4)   SSP administrators for search can view search usage reports by clicking Search usage reports in the Search section of the SSP home page.

I hope the above information helps you to configure Usage analysis Processing.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

"My Profile" NOT Working on "My Site" in MOSS 2007

Error message when a user clicks the "My Profile" tab of a "My Site" personal site in SharePoint Server 2007: "Result: 404 File Not Found."

Cause:-
This issue occurs because the My Site Host site template is not applied to the site collection that hosts the personal site provider.

Resolution:-
To resolve this issue, move the personal site provider for My Site personal sites to a different site location. To do this, follow these steps:

1.Add an explicit inclusion included path for My Sites personal sites. To do this, follow these steps:

a.Start SharePoint 3.0 Central Administration.
b.Click Application Management.
c.On the Application Management page, click Define managed paths under SharePoint Web Application Management.
d.In the Web Application box, click the Web application that you want to configure.
e.In the Add a New Path area, type the path in the Path box. Then, click Check URL to verify the URL.
f.In the Type box, click Explicit inclusion, and then click OK.

2.Create a new site collection at the URL that you specified in the included path. To do this, follow these steps:

a.On the Application Management page, click Create site collection under SharePoint Site Management.
b.In the Web Application box, click the Web application that you want to configure.
c.On the Create Site Collection page, specify a title and a description for the site collection in the Title and Description area.
d.In the Web Site Address area, specify the URL of the included path that you added in step 1.
e.In the Primary Site Collection Administrator area and in the Secondary Site Collection Administrator area, specify the administrator for the site collection.
f.In the Quote Template area, specify the template that you want to use.
g.In the Template Selection area, click My Site Host in the Select a template box, and then click OK.

3.Move the personal site provider. To do this, follow these steps:

a.Under Shared Services Administration, click Shared Service Provider (SSP).
b.On the home page, click My Site settings under User Profiles and My Sites.
c.On the My Site settings page, type the URL of the included path in the Personal site provider box in the Personal Site Services area.
d.Configure the options that you want for the other settings, and then click OK.

Refferance:- http://support.microsoft.com/kb/924399

Cannot start the WSS Search Service & Office SharePoint Search not working - Same SQL & WSS\MOSS Server

Cannot start the Windows SharePoint Services Search Service & Office SharePoint Search not working-Same SQL & WSS 3.0\MOSS 2007 Server

Running SQL and MOSS on the same server, I was unable to start the WSS Search Service and the Office SharePoint Search service was showing errors in the SSP Site.

Event Viewer Description:-

Event Type:Error

Event Source:Windows SharePoint Services 3 Search

Event Category:Gatherer

Event ID:10034

Description: Could not access the Search service configuration database.

Context: Application '8f7d4cbe-8cb1-4d32-b406-1737af554479'

Details:The filename or extension is too long.(0x800700ce)


Event Type:Error

Event Source:Office SharePoint Server

Event Category:Office Server Shared Services

Event ID:6482

Description:Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (9d344ee4-eacc-4460-8dc6-bb66bd5ab982).

Reason:The path is not of a legal form.

Techinal Support Details:

System.ArgumentException: The path is not of a legal form.

at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)

at Microsoft.Office.Server.Search.Administration.SearchApi.AddApp(Role role)

atMicrosoft.Office.Server.Search.Administration.SearchServiceInstance.InstallGathererApplicationIf()

at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

atMicrosoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Root cause:-

If you are running SQL and WSS 3.0/MOSS 2007 on the same server,you will need to specify the Database Server, in the SharePoint Configuration Wizard as the NetBIOS name (Server01) and not the FQDN (Server01.Domain.com).Seems to be a bug in SharePoint as I always use the FQDN wherever possible.

Resolution:-

Disconnect from the SharePoint Farm (by running the SharePoint Configuration Wizard) and reconnect, this time using the NetBIOS name for the DB server. You will need to set the Indexer for any SSP’s you have created and restart some of the Services on the SharePoint Server but you should get back up and running.

People search not working in MOSS 2007 Server

Setting up Search functionality in SharePoint server site, which needs configuration of Shared Services Provider (SSP)

1)   Setting up user Profiles

2)   Setting up address to be crawled

3)   Set up of Scope

After the complete configuration, you might come across situation where search in site data works but people search doesn’t seem to work.

This can really very frustrated… Well though it seems like a big issue with installation and stuff but it’s a “miss” in configuration setting.

The addition of url “sps3://sitename “works wonders…..

I hope, this will help and resolves all your problems. Please let me know in case of any queries, Thank you.