Scribd
Upload
116 views4 pages

Troubleshooting For SharePoint Server

The document provides troubleshooting information for several common errors in SharePoint Server. It describes the cause of each error and the resolution steps to fix it. Some example errors addressed include failed upgrades, search service issues, script errors, and slow crawl performance. Resolutions involve manually copying files, starting services, installing updates, configuring proxy settings, and clearing tag mappings.

Uploaded by

DarksMan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
116 views4 pages

Troubleshooting For SharePoint Server

The document provides troubleshooting information for several common errors in SharePoint Server. It describes the cause of each error and the resolution steps to fix it. Some example errors addressed include failed upgrades, search service issues, script errors, and slow crawl performance. Resolutions involve manually copying files, starting services, installing updates, configuring proxy settings, and clearing tag mappings.

Uploaded by

DarksMan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Troubleshooting for SharePoint Server

Error: Failed to upgrade SharePoint Products and Technologies


(Office SharePoint Server 2007)
Cause
This error occurs when the SharePoint Products and Technologies Configuration Wizard cannot locate or modify the
Web.config file.

Resolution
To resolve the issue, you must manually copy the Web.config file from the following folder:

%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Config

to the following folder:

%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Template\Layouts.

After the Web.config file is in the Layouts folder, you can run the SharePoint Products and Technologies
Configuration Wizard again

Error: Failed to start the Office SharePoint Server Search service


Cause
During an update, the Office SharePoint Server Search service might not automatically restart.

Resolution

Important:

To run the Stsadm command-line tool, you must be a member of the Administrators group on the local
computer.

Manually start the Office SharePoint Server Search service


1. On the drive on which SharePoint Products and Technologies is installed, open a command prompt window
and change to the following folder:

%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin

2. Type the following command, and then press ENTER:

stsadm –o osearch –action start

Setup stops responding when you use an alternate location for


the Updates folder (SharePoint Server)
Cause
This is a known limitation. If you want to use the Updates folder, you must use the default location for the
SUpdateLocation parameter. The default location is the Updates folder at the root of the update installation
source.

Resolution
Do not change the value of the SUpdateLocation parameter.

Error: The search request is unable to connect to the search


service
Cause
This error may indicate that you do not have enough disk space on your query server. If adequate disk space is not
available, your query servers will slow down or stop.

Resolution
Add disk space to your query server. This issue occurs because the method used to merge indexes has been
changed in SP1 to improve performance and reduce server downtime. However, this change increases the disk
space that is required to perform a master merge. Previous to SP1, a minimum of twice the physical size of the
index was required. With SP1, the minimum disk space requirement on a query server or index server is 2.85 times
the physical size of the index.

Content Editor Web Part script error


Cause
The Windows SharePoint Services 3.0 Service Pack 1 (SP1) Language Template Pack must be installed along with
the Office SharePoint Server 2007 SP1 Language Template Pack.

Resolution
You can prevent this issue from occurring on your Office SharePoint Server 2007 Web servers by installing the
Windows SharePoint Services 3.0 SP1 Language Template Pack.

If you already installed the Office SharePoint Server 2007 SP1 Language Template Pack without the Windows
SharePoint Services 3.0 SP1 Language Template Pack and your users are experiencing the script error, you can
resolve this problem by installing the Windows SharePoint Services 3.0 SP1 Language Template Pack on the
affected Office SharePoint Server 2007 Web servers.

Unknown error when you check out from or publish to a


document library
 Cause

The error is caused by an incorrect installation and configuration of Office SharePoint Server 2007. This error,
reported in system diagnostics during application operations, may indicate a work-around that instructs the
administrator to change machine key values in the Office SharePoint Server 2007 farm to resolve the issue.
Microsoft does not require or recommend that system administrators edit machine key values. The underlying
cause of the error is a configuration issue that may have occurred during or following the initial Office SharePoint
Server 2007 farm installation.
 Resolution

Test and verify your Office SharePoint Server 2007 Standard Edition farm installation method and isolate possible
errors in application code or in post-installation configuration. To do this, create a new Office SharePoint Server
2007 Standard Edition baseline Virtual Machine by using the procedures in the following article in the Microsoft
Knowledge Base: Unknown Error in Microsoft Office SharePoint Server 2007 (http://go.microsoft.com/fwlink/?
LinkId=116157&clcid=0x409).

Custom list templates do not appear on the "Create Page" page


of a SharePoint site
 Cause

This problem can occur if you create the custom list template in a site that has a different site definition identifier
(ID) than the site that you added the template to. For example, this problem might occur if any one of the
following conditions is true:

 You create a custom list template in a Office SharePoint Server 2007 site, and then you import the
template to a portal site.

 You create a custom list template in a portal site, and then you import the template to a Office SharePoint
Server 2007 site.

 You create a custom list template in a Office SharePoint Server 2007 site, and then you import the
template to another Office SharePoint Server site that uses a different site definition ID.

 Resolution

Create the custom list template in the Office SharePoint Server 2007 site or in the portal site where the template
will be used. For example, if Office SharePoint Server 2007 sites that are based on the Team Site template require
a custom survey template, create the custom survey template in a site that is based on the Team Site template.

Crawl performance is unexpectedly slow


 Cause

This issue can occur if a proxy server is not configured for the search service in Office SharePoint Server 2007 and
a proxy server is configured in Microsoft Internet Explorer. When a proxy server is not configured for the search
service in Office SharePoint Server 2007, the account that is configured as the default content access account uses
the proxy server settings that are configured in Internet Explorer.

 Resolution

Use the following procedure to remove the proxy settings that are configured in Internet Explorer and restart the
Office SharePoint Server Search service.

1. Remove the proxy settings that are configured in Internet Explorer. To do so, follow these steps:

a. In Internet Explorer, on the Tools menu, click Internet Options.

b. In the Internet Options dialog box, click the Connections tab, and then click LAN settings.

c. In the Local Area Network (LAN) Settings dialog box, in the Proxy server section, clear the
Use a proxy server for your LAN (These settings will not apply to dial-up or VPN
connections) check box, and then click OK.
d. In the Internet Options dialog box, click OK.

2. Restart the Office SharePoint Server Search service by performing the following steps:

a. Click Start, point to Administrative Tools, and then click Services.

b. In the list of services, right-click Office SharePoint Server Search, and then click Restart.

ASP.NET user control security exception


 Cause

Controls or assemblies loaded from outside the global assembly cache are not trusted by default.

 Resolution

Clear the tagMapping properties of the control by inserting the following lines in the Web.config file:

<code>
<tagMapping>
   <clear/>
</tagMapping>
</code>

You might also like