Uninstalling Windows SharePoint Services 2.0

There are different degrees to which you can uninstall Microsoft Windows SharePoint Services. Depending on your needs, you can choose from the following options:

-Remove Windows SharePoint Services from a virtual server and preserve the site content.
You can choose to remove Windows SharePoint Services, but keep the site content in the content databases. This allows you to extend the virtual server again later and reconnect to the site content. If you leave the content databases intact, you can reconnect to them, from the same virtual server or from a different virtual server, and continue hosting the site content using the same Uniform Resource Locator (URL). Use this method to temporarily remove and then restore a virtual server, or to change which virtual servers are hosting which content in a server farm setting.

-Remove Windows SharePoint Services from a virtual server and delete the site content.
You can choose to remove Windows SharePoint Services and delete the site content in the database. Use this method to remove a virtual server permanently, but continue using Windows SharePoint Services on other virtual servers. For example, use this method if you are finished with a project and no longer need the associated Web sites.

-Uninstall Windows SharePoint Services completely from a server.
You can choose to uninstall Windows SharePoint Services by using the Add/Remove Programs control panel. This method does not delete site content. You can reinstall and reconnect to the site content. Use this method to repair an installation or to remove a Web front-end server from a server farm.

Removing from a Virtual Server by Using HTML Administration
To remove Windows SharePoint Services from a virtual server by using HTML Administration, you use the Remove Windows SharePoint Services from Virtual Server page.

Remove from a virtual server
-Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint -Central Administration.
-On the Central Administration page, under Virtual Server Configuration, click Configure virtual server settings.
-On the Virtual Server List page, select the virtual server you want to configure.
-On the Virtual Server Settings page, under Virtual Server Management, click Remove Windows SharePoint Services from Virtual Server.
-On the Remove Windows SharePoint Services from Virtual Server page, select one of the following:
-Remove without deleting content databases
This removes only the Windows SharePoint Services folders from the virtual server — the content database remains intact, so you can reconnect to it later using the same virtual server or a different one.
-Remove and delete content databases
This both removes the Windows SharePoint Services folders from the virtual server and deletes the content database. You will not be able to reconstruct the sites previously stored on that virtual server unless you have a backup.
-Click OK.

Removing from a Virtual Server by Using the Command Line
You can use the unextendvs operation with the Stsadm.exe command line utility to remove Windows SharePoint Services from a virtual server. The unextendvs operation takes the -url parameter and the optional -deletecontent parameter. When you use unextendvs without the -deletecontent parameter, it leaves the content databases in place, so that you can reconnect to the content for a virtual server. When you include the -deletecontent parameter, the content databases are removed and the virtual server is removed from the configuration database.

For example, to remove Windows SharePoint Services from a virtual server, but preserve the content databases, use the unextendvs operation with syntax like the following:
stsadm -o unextendvs -url http://servername

To remove Windows SharePoint Services from a virtual server and remove the content databases permanently, use the unextendvs operation with syntax like the following:
stsadm -o unextendvs -url http://servername -deletecontent

Note:-When you use the unextendvs operation with the -deletecontent parameter, you cannot reconnect to the site content later.

Uninstalling from the Server Computer
If you want to remove Windows SharePoint Services from a server computer entirely, you can uninstall by using the Add or Remove Programs control panel. Uninstalling Windows SharePoint Services does not remove any chained products that were installed, such as WMSDE. You must uninstall these programs separately.

Uninstall
-On the server computer, click Start, click Control Panel, and then click Add or Remove Programs.
-Select Windows SharePoint Services, and then click Remove.

When you use the Add or Remove Programs control panel to remove Windows SharePoint Services from a server, it calls a command-line operation, stsadm -o uninstall, to perform the task. The uninstall operation does not remove any chained products that were installed. The uninstall operation takes the optional -deletecontent parameter. When uninstall is used without the -deletecontent parameter, it leaves the content and configuration databases in place, so that Windows SharePoint Services can be reinstalled, and you can reconnect to the databases and continue hosting sites. When the -deletecontent parameter is used, the content and configuration databases are removed, and you cannot recover the site content.

Refferance:-http://technet.microsoft.com/en-us/library/cc288469.aspx

SharePoint 2007 Installation on Windows Server 2008

1. You must enable the IIS7 Feature Role on Windows Server 2008 with .NET 3.0
-From Control Panel, Programs and Features, Select 'Turn Windows Features On or Off'
-Next, Under 'Server Manager, Features' Select '.NET Framework 3.0 Features'. When askedto install the IIS7 role, select yes.
-Under IIS7 'Security', be sure to select the authenticationyou want, i.e. Basic, NTLM, Kerberos, etc.
-Next, you must slipstreamWindows SharePoint Server 3.0 SP1 AND SharePoint Server 2007 SP1 into your SharePoint Server 2007 installation directory.

2. I used Winrar to extract the files from my SharePoint Server 2007 ISO, but you can alsocopy them into a directory directly from the DVD. Create a directory, we'll use c:\Slipped for our installation point. Copy the entire DVD contents to c:\Slipped

3. Next, you must download and extract both Windows SharePoint Services SP1 and SharePoint Server 2007 SP1you can get them here
http://blogs.msdn.com/sharepoint/archive/2007/12/11/announcing-the-release-of-wss-3-0-sp1-and-office-sharepoint-server-2007-sp1.aspx

-Create a directory to host the WSS 3.0 files after extraction. We will use c:\wsssp1
-create a directory to host the SharePoint Server 2007 files after extraction. We will use c:\mosssp1
-we will assume we have downloaded both service packs to c:\

Extract the WSS 3.0 service pack files by executing 'c:\wssv3sp1-kb936988-x86-fullfile-en-us.exe /extract:c:\wsssp1' Agree to the license terms, and the service pack will unpack.

Extract the SharePoint Server 2007 service pack by executing 'C:\officeserver2007sp1-kb936984-x86-fullfile-en-us.exe /extract:c:\mosssp1' Agree to the license terms, and the service pack will unpack.

4. Copy the service pack files from the above directories into the installation updates directory.
5. Last, run the setup from the x86 directory, and it should install!

Note:-Microsoft has now released a slipstreamed SharePoint Server 2007 SP1 image here

Additional Resources:
MOSS and WSS SP1 files are located here. You will need both service packs for the slipstream installation. Note: the links have both the 32 and 64 bit versions.
WSS SP1: Windows SharePoint Services 3.0 Service Pack 1 (SP1)
MOSS SP1: The 2007 Microsoft Office Servers Service Pack 1 (SP1)

I hope the above information helps you to install sharepoint on windows server 2008 successfully.
All The Best !

The restricted trust level is not supported + Infopath

Recently I tried to create an InfoPath 2007 form template and publish it to a SharePoint Forms Library and I received the following error:The restricted trust level is not supported.

This Form template cannot be uploaded to the server.Review the following 1 error(s) for more information.
Errors
The restricted trust level is not supported.

-Make sure that the form’s trust is set to domain.
-Go to Tools > Form Options > Security and Trust and Uncheck “automatically determine security level” and select “Domain”or "Full Trust" as the level of trust.
-Click “Ok”.

To publish InfoPath 2007 form to a SharePoint library:

Using SharePoint to Verify and Upload the Form Template

The SharePoint Central Administration site contains the Upload Form Template page,to verify a form template before uploading it. Once the form template is verified, enter the path to the form template and upload it to the server.

To verify the form template by using SharePoint Central Administration
1. Click Start, click All Programs, click Administrative Tools, and then click SharePoint 3.0 Central Administration.
2. In the top navigation bar, click the Application Management tab.
3. On the Application Management page, under InfoPath Forms Services, click Upload form template.
4. On the Add Form Template page, click Browse.
5. In the Choose file window, browse to C:\InfoPathLabs\deploylab01.xsn, click the template, and then click Open.
6. In the Deploy Form Template section, click Verify.
7. In the Report Details section, look for any errors and warnings for the form template.
8. If the system warns you that the template already exists, click Application Management, click Manage form templates, click the arrow that appears next to the form template, and then click Remove Form.
9. On the Remove Form Template page, click Remove.
10. If you did not receive a warning, click OK.

Stsadm access denied on Windows Server 2008

We recently faced one situation where we encountered Access Denied errors when attempting to run stsadm on a dev Windows Server 2008 Web Edition.We checked to see if the user account we were using was a local administrator on the server and it was.

We were not sure what was causing the problem.Then we looked into the User Account Control settings and those were enabled to help "protect" the server. Turning those off allowed me to run stsadm from the command line.

The User Account Control (UAC) is found under Control Panel --> User Accounts --> Turn User Account Control on or off.

You do not have permissions to open this file on Excel Services

Hello Guys,
If you receive the following Exception when you try to open the sample workbook or another workbook try the following steps:

You do not have permissions to open this file on Excel Services.Make sure that the file is in an Excel Services trusted location and that you have access to the file.

1.Open Central Administration -> go to Operations tab -Ensure that the Excel Service is running.
2.Open Central Administration -> go to your configured Shared Service -> click Excel Service Settings.

-File Access Method: ensure that it is not using Impersonation, instead the Option Process Account should be enabled.

3. Open Central Administration -> go to your configured Shared Service -> click add new trusted file location
-Field URL: here you can specify a report library or the whole portal
-Location Type: should be Windows SharePoint Services
-Children trusted: defines whether the children should also be trusted or only the definied path

How to enable SSL site collections using host headers to be browseable using ISA

1.In ISA 2006, right click Firewall Policy, New, and finally SharePoint publishing rule; type a new name for the publishing rule.Click Next.

2.Select Publish a single Web site or load balancer since we are dealing with a single site collection. Click Next.

3.Select Use SSL.. Click Next.

4.Type the name of the published web site, which is the external URL as it would appear on the certificate. Click the box next to Use a computer name or IP address to connect to the published server, and fill in the correct IP address for the server. Click Next.

5.From the drop down for Accept requests for, select This domain name. In the Public name box, type in the domain name you wish to use. Click Next.

6.We now must create a new listener. Give the new listener a name. Click Next.

7.Select Require SSL secured connections with clients. Click Next.

8.Select External Network and then the IP Address. This IP address will be dedicated to accept requests from SharePoint traffic externally. Click on OK, and then click Next.

9. Click on Select certificate and select the correct certificate with the name you are using in the public name. Click on Select.

10. Select the authentication type, and configure as needed. Click Next.

11. If SSO is being used, click on Enable SSO for Web sites published with this Web listener, and configure the SSO domain being used for authentication. Click Next.

12. Click Finish.

13. Select the new Listener, and click on Next.

14. Select the NTLM authentication, and click on Next.

15. Select the first option if AAMs are already configured; if not select the second option. Click Next.

16. Select All Authenticated Users. Click Next.

17. Click on Finish.

Disable MySite and MyLinks in MOSS 2007

In order to turn off or disable the MySite or MyLinks functionality you need to be an Sharepoint administrator.

-Go to the Central Administration Web Page
-Click on the link for Shared Services Administration
If you have more than one SSP, select the one that is running the MySites functionalityUnder "User Profiles and My Sites" click Personalization Services Permissions

Select the group you want to limit the functionality for. More than likely you will just have NTAuthority\Authenticated Users.
In the next screen you will see a list of checkboxes,

--To disable MySites uncheck "Create Personal Site"
--To disable MyLinks uncheck "Use Personal Features"
Once you find it, disabling the functionality is pretty easy.
Hopefully this will save your lot of efforts.

Configure single sign-on

Single sign-on (SSO) is a Microsoft Office SharePoint Server feature that provides storage and mapping of credentials such as account names and passwords. Using SSO, portal site–based applications can retrieve information from third-party applications and back-end systems such as Enterprise Resource Planning (ERP) and Customer Relations Management (CRM) systems.

The use of single sign-on functionality enables users to authenticate only once when they access portal site–based applications that need to obtain information from other business applications and systems.

There are seven main activities that we need to do:
1.Create the SSO service account -- This is the account that the service will run under.
2.Create the SSO groups -- These groups are used to control who has the ability to administer SSO (export the master key) and who has the ability to manage it (add/remove application definitions.)
3.Configure the SSO Service - Set SSO to start and get it to use the service account.
4.Configure SQL Server - Authorize the SSO service account to SQL server.
5.Manage SSO - Setup SSO in MOSS including the groups and the database.
6.Manage the encryption key -- Create the encryption key that will be used for protecting the username and password information on the system.
7.Manage settings for enterprise application definitions -- Define what initial applications SSO will be setup to manage passwords for.

Create the SSO Service Account
We need to create an account for the "Microsoft Single Sign-on Service" (SSO Service) to run as. This account has to be a domain account that has local administrative privileges for the front end web servers, must be a member of the SharePoint group Farm Administrators, must have db_creator and security administrator roles in SQL Server, and must be a member of the group that is defined as SSO administrators.

1.From the Start Menu click Administrative Tools-Active Directory Users and Computers
2.In the left hand pane on the Users folder right click and select New-User from the menu that appears. If your organization places service accounts in a different organizational unit (OU) you can certainly add this account to that location.
3.Enter the First Name (SharePoint SSO), Last Name (Service), and User logon name (SharePointSSOSvc) fields and click the Next button. You can name the account anything you want, however, these values make it clear what the account is used for.
4.Enter the a password into the Password and Confirm password fields. Uncheck the User must change password at next logon checkbox. Check the User cannot change password and Password never expires checkboxes. Click the Next button. This sets the account up to be a service account.
5.Click the Finish button.
6.On the user that was just created, right click and select Properties.
7.Click the Member Of tab.
8.Click the Add button.
9.Enter the group name Domain Admins and click Check Names then click OK. As mentioned above, if you're using another group to provide local administrator access to the farm servers, use that group here.
10.Click the OK button.

Create the SSO Groups
There are two important groups for SSO. The first group is the administrative group which includes those users capable of administering SSO. This includes the ability to backup and restore the encryption key -- because of this they can effectively decrypt all user credentials in the SSO database and thus membership to this group should be severely limited. The second group, a managers group, is used to manage the application profiles in the SSO system. This group doesn't directly have access to passwords but could inadvertently delete all of the stored passwords. In the following steps we'll create both groups and add the SSO service account we created above into the administrators group.

1.In Active Directory Users and Computers (still open from the last set of steps) from the left pane right-click Users and select New-Group. As before if your organization requires that groups be placed in a different OU, select that OU to create group in.
2.Enter the Group Name (SharePoint SSO Administrators) and click the OK button.
3.Left click the new group, and then right click the new group and select Properties.
4.Click the Members tab.
5.Click the Add button.
6.Enter SharePointSSOSvc, click the Check Names button, and click the OK button.
7.Click the OK button.
8.In the left pane, right click Users and select New-Group. As before, if your organization requires a different location, use that location.
9.Enter the Group Name (SharePoint SSO Managers) and click the OK button.
10.Close Active Directory Users and Computers, we're done with it.

Configure the SSO Service
By default the SSO service in SharePoint doesn't start. In this activity we're going to enable the SSO service. On each server in the farm and then once completed we're going to change the account used for SSO in SharePoint Central Administration.

1.On the Start menu click Administrative Tools-Services
2.In the Services application in the right hand pane scroll down to the Microsoft Single Sign-on Service, right click and click Properties.
3.Change the Startup type from Manual to Automatic.
4.Click the Start button.
5.Click the OK button.
6.Close the Services application. We're done with it.
7.Repeat steps 1-5 on each server in the SharePoint farm.
8.On the Start menu click Administrative Tools-SharePoint 3.0 Central Administration
9.Click the Operations tab
10.In the Security Configuration section, click the Service Accounts link
11.In the Windows service drop down list select Single Sign-on Service.
12.Enter the Username (DC\SharePointSSOSvc) and Password for the service account and click the OK button.

Configure SQL Server for the SSO Service Account
The SSO service account needs to create the SSO database and setup the correct permissions. In order to do that it needs the security administrator (securityadmin) and database creator (dbcreator) system roles. In the following steps we'll get permissions setup for the service account.

1.On the Start menu click All Programs -Microsoft SQL Server 2005 - SQL Server Management Studio.
2.If your server name isn't correct in the dialog select the correct server. Then click the Connect button to connect to your SQL server.
3.Click on the plus sign to the left of Security to expand it. Click on the plus sign to the left of Logins to expand it.
4.Right click on the SharePoint SSO service account (DC\SharePointSSOSvc) and click properties.
5.In the Select a page (left) pane select Server Roles.
6.Click the checkboxes to the left of dbcreator and securityadmin.
7.Click the OK button.
8.Close Microsoft SQL Server Management Studio, we're done with it.

Manage Settings for Single Sign-on

In this step we'll go through the process of creating the SSO database by using the Manage settings for single sign-on link on the central administration operations screen.
1.On the SharePoint Central Administration Operations page in the Security Configuration heading select the Manage settings for single sign-on link.
2.Click the Manage server settings link.
3.In the far upper right corner, click the down arrow next to Welcome System Account (or whatever name is displayed.) From the menu that appears, select Sign in as a Different User.
4.In the User name text box enter the SharePoint SSO Service Account (DC\SharePointSSOSvc) and in the Password text box enter the account's password. 5.Enter the administrators group name including the domain name (DC\SharePoint SSO Administrators)in the Single Sign-On Administrator Account section's Account name textbox.
6.Enter the managers group name including the domain name (DC\SharePoint SSO Managers) in the Enterprise Application Definition Administrator Account section's Account name textbox.
7.Click the OK button.

Manage the Encryption Key
The next step is creating an encryption key for the credentials to be encrypted with. In order to do this, follow these steps:
1.On the Manage Settings for Single Sign-on page click the Manage encryption key link
2.Click the Create Encryption Key button.
3.Click the OK button.
4.In the breadcrumbs, click the Manage Single Sign-On link.

With an encryption key set, you're ready to create an application definition.

Manage Settings for Enterprise Application Definitions

The final step is to define an application definition for SSO. This can be done with the following steps.
1.On the Manage Settings for Single Sign-On for... page in the Enterprise Application Definition Settings, click the Manage settings for enterprise application definitions link.
2.Click the New Item button.
3.Enter a Display name (Demo Application), a Application name (Demo), and Contact e-mail address (sharepoint@demo.thorprojects.com).
4.Select the Account type. Generally this will be Individual. Note that this cannot be changed once the application has been defined.
5.Click the OK button.
6.Close the web browser with central administration.

I hope the above steps helps you to configure Single Sign On . If you have any query or doubt regarding any step then please let me know. I would be more happy to answer your queries.

Configure single sign-on

Not able to open the site and central administration page without entering default.aspx page manually

Directory Listing Denied:The Virtual Directory does not allow Contents to be listed

The Project in which i am working consist of three phase testing as Test-QA and then production. Once we are able to deployed successfully then we implement that change in production which is ideal for everyone.As we need to implement Ajax in the sharepoint farm, it requires .net 3.5 with sp1 to be deployed first. After deploying .net 3.5 in the SharePoint test enviornment, we faced some issues and due to some reasons, we had to revert back the changes and uninstalled .net 3.5.

Now the problem starts, after the uninstallation, when we tried to browse the site, we faced wierd error message "The Virtual Directory does not allow Contents to be listed".

After doing some troubleshooting, we were able to resolved the Problem. The steps that we followed as follows:-
Resolution Steps:-
-IIS Manager
-Site
-Properties
-Home Directory tab
-Configuration
-Wildcard Application Maps
-Add the location path of the aspnet_isapi.dll
C:\windows\microsoft.net\framework\v2.0.50727\aspnet_isaspi.dll

Note:-Ensure that the checkbox Verify that the file exists is unchecked, otherwise error 404 page not found will be displayed.
This is because the data is rendered from the SQL database and not from IIS locally, and sharepoint will process this on the run while the site is being accessed.

Manual Uninstallation of WSS 3.0 | MOSS 2007

Few days before, while doing a troubleshooting in my lab on one sharepoint issue, I came across some error message and due to that, i need to uninstall Microsoft office sharepoint server 2007.
But while uninstallation of sharePoint 2007, the uninstaller launched, but vanish shortly after starting.

Attempted to uninstall by means of command line, got error message as mentioned below:-
This product installation has been corrupted. Run setup again from the CD, DVD, or other original installation source.

Cause:Unknown
I tried the below mentioned steps to uninstall Microsoft Office SharePoint Server 2007 and it worked.
Note:- This steps will also worked for Windows SharePoint Services 3.0
Stop services, delete registry hives, and delete binaries.[For WSS v3]
-Disable and Stop the following services
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer

Note the following registry keys:
From HKLM\Software\Microsoft\Office Server\12.0
-InstallPath (default is C:\Program Files\Microsoft Office Servers\12)
From HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
-Location (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)

Delete the following folders:
The value of the InstallPath key
The value of the Location key C:\%CommonProgramFiles%\Microsoft Shared\SERVER12

[For MOSS 2007]
Disable and Stop the following services
-Microsoft Single Sign-on Service
-Office SharePoint Server Search
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer

Delete the following registry hives:
HKLM\Software\Microsoft\Office Server\12.0HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
[x32] - HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\OSERVER
[x64] - HKLM \SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\OSERVER

Delete the following folders:
The value of the InstallPath keyThe value of the Location key
C:\%CommonProgramFiles%\Microsoft Shared\SERVER12

Restart the server and perform an installation as normal.

Spelling did not complete properly. If this problem persists, notify your system administrator.

One of the many great new features in Microsoft Officer SharePoint Server (MOSS) 2007 is the ability to use spell check for any content you add to your site. One of the NOT so great new features of MOSS 2007 is the fact that this no longer works if you lock down your permissions on your server.
We recently locked down the permissions for ‘read only’ access users - essentially your viewers in the web site, which for me is any authenticated user. Unfortunately then the complaints started that when ever a user tried to do a spell check they got the error:
“Spelling did not complete properly. If this problem persists, notify your system administrator”

After some digging around it turned out that this is a permissions error. Turns out if you lock down permissions in SharePoint, user’s can no longer view the dictionary against which SharePoint does it’s spell check, and consequently it no longer works.

Thank to Microsoft as this is fixed with Service Pack 1.
Spell Check Permissions work around
You will need to modify the permissions of the Group to which the user has been added, in your case the user has been given Read Permissions.

1. Browse to the root site and go to “Site Actions”->”People and Groups”.
2. Click on “Site Permissions”
3. For the group (say “Visitors”) to which the user facing the problem has been added – find its “Permissions” level – it was “Read” in your case as checked during the last call.
4. Click on “Settings”->”Permissions Levels”
5. Click on “Read”
6. Check the 2 check boxes for “Browse Directories - Enumerate files and folders in a Web site using SharePoint Designer and Web DAV interfaces.” and “Use Remote Interfaces - Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site.”.
7. Click on Submit and check if the issue reproduces.

Clicking ‘Connect To This Discussion board’ in SharePoint alert email gives error (0×800401F3)

When using Exchange 2003 with Outlook 2007, when you click ‘Connect To This Discussion board’ from a SharePoint alert email, you receive the following error:
Outlook Send/Receive Progress! Task ‘SharePoint’ reported error (0×800401F3) : ‘Unknown Error 0×800401F3′

Cause:-
Certain headers are encoded by SharePoint which Exchange 2003 does not decode. Exchange 2007 does decode these headers and the issue does not occur with Exchange 2007.

Resolution:-
Upgrade to Exchange 2007 to resolve this issue.

APPLIES TO:-
-Microsoft Exchange Server 2003 Standard Edition
-Microsoft Exchange Server 2003 Enterprise Edition
-Microsoft Office SharePoint Server 2007

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.

Content type '0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811' not found

We have a portal server 2007 installation that is working fine except for one frustrating error. We deployed the latest February Cumulative Patches and after this the problem starts. We have one console application that creates a site by using stsadm command.

If we try the same activity by using GUI then everything works fine. This Console application runs in 4 steps and we are facing the problem at step 4 and prompts error message "Content type '0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811' not found in web 'http://moss2007.com' "

When i check the content type on the website i was shocked there was nothing means not even single content type. The weird thing is, that the content type ID is the ID from the “PageLayout” Content Type...

Symptoms:- 

I noticed and marked some of the common areas affected by this content type error message.
 

1)   If we try to create a new page ("Create Page" command from the "Site Actions" Menu) from any of the sites.

2)   After a restore from MOSS 2007 Standard to MOSS 2007 Enterprise.

3)   While creating a new page in a collaboration portal.

4)   While trying to add a new page.

5)   After deploying cumulative updates.

6)   Creating a new Web Site programmatically.

Resolution:-
Now after countless searched on the internet I turn up basically nothing, TechNet is dry, and no one seems to have had this error (not a first for me sadly). I ask a desperation post on Experts-Exchange and run through the drills. 

Checking my xml config files, looking at error logs, etc.
 

There are some resolutions applied for this error message so choose the best one that suites your environment.
 

-Run SharePoint Products and Technologies Configuration Wizard on all the machines.

-Go to Site Central Administration, User Permissions for Web Application and be sure "Use Client Integration Features" and "Use Remote Interfaces" are enabled. That can also work for you.

-This ContentTypeID points to the "PublishingResources" feature.You will need to activate this feature by running STSADM.

-STSADM -o activatefeature -name PublishingResources -url http://moss_url/

Run this commands one by one as follows:-
-stsadm -o activatefeature -filename publishing\feature.xml -url http://url/ -force

-stsadm -o activatefeature -filename publishingresources\feature.xml -url http://url/ -force

-stsadm -o activatefeature -filename publishingSite\feature.xml -url http://url/ -force

-stsadm -o activatefeature -filename publishingweb\feature.xml -url http://url/ -force

-stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://url/ -force

-stsadm -o activatefeature -filename navigation\feature.xml -url http://url/ -force

I hope the above information helps you to overcome this error message.

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.