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.