Shivaprasad Mungara

Troubleshooting Access denied error - SharePoint 2007 sites

smungara — Tue, 08 Sep 2009 13:25:00 GMT

On the other day I was troubleshooting on the SharePoint Access denied error. The System account and Users who has full rights also got the access denied error.
We checked ULS and took couple of fiddler traces on the site, nothing actually pointed out to the right direction.

The above error can be for many reasons, below is the one of the reason, which can help

We then checked the "Site collection quotas and Locks" under Application management - SharePoint Site Management
We found "Read-Only" was selected
We then changed the settings to "NOT LOCKED"
Then did an IISRESET
We were able to browse the site successfully

Unable to save changes to documents in SharePoint 2007 "There is a problem with the Web Server. Try again later, or contact the server administrator

smungara — Tue, 14 Jul 2009 11:36:00 GMT

When users edit a document they are prompted for a certificate so that the file can be checked out When they try to check in their changes they encounter the error "There is a problem with the Web Server. Try again later, or contact the server administrator"

What is the Cause ?
****************
The problem was NOT the server, although the fix was. The issue is when office 2003 sp3 or office 2007 attempts to communicate with Share Point 2003 or 2007 it uses what is called the office web communication protocol. This protocol gets a header added when you PKI enable your communication between the Share Point server and the Client Workstation. Still all would be well until the office document becomes “complicated”. In other words, when you add special things to the documents, like other objects from other documents, Pictures, Graphs, or any other kinds of things. When this happens Office 2003 SP3 or Office 2007 will change the way the office application communicates with the share point server. To speed the connection up, office changes this communication. The server is designed to handle this type of communication without PKI. With PKI the server has to stream this data in at a slower pace. The Client workstation is unable to understand this streaming so it returns the “Web server Busy” error. Because, the web server is busy and needs more time to save this file. The client won’t give it that time so it shuts the communication down and tells you to try again later.

What you can do to resolve ?
***********************
Increase the value for the UploadReadAheadSize metabase property for Internet Information Services (IIS) using the Adsutil command-line utility.
For example, use the following command to set the value to 200 million bytes.

Adsutil set w3svc/uploadreadaheadsize "200000000"

See the Microsoft TechNet article “UploadReadAheadSize Metabase Property (IIS 6.0)”
at http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/48900606-4881-4a93-a4c1-0e0ac622fee6.mspx?mfr=true for more information.

Error "Server Error in '/" Application." while browsing the site which was restored using the Full farm backup

smungara — Tue, 26 May 2009 11:28:00 GMT

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine

In this Scenario, the Farm level backup was taken moving the configdb on to the new SQL server, then restoring the Farm level backup on the SharePoint Farm.

Now when you try to browse the site, you get an above error.

Then remove the content database from the site and re attach using the stsadm –o command you still tend to see the above error

The best way to resolve the issue

Run the configuration wizard and disconnect SharePoint server from the farm.

Then Run the configuration wizard again and choose to join to the existing SharePoint farm.

Then create a new Site, detach the content database which was created while creating a site

Add the production content database to the site using

stsadm –o addcontentdb –url < > - databasename < >

Now you should be able to browse the sites

No results displayed while do a search in Office SharePoint Server 2007

smungara — Sun, 19 Apr 2009 14:55:00 GMT

When you search for file types or contents in Office SharePoint Server 2007 Search Center with tabs template or Search Server 2008 you do not see any results. You also do not see any errors on the results.aspx page and Event Viewer on the server.
When you enable verbose logging on the server and try the search again, we can find the below errors.

w3wp.exe (0x1454) 0x164C SharePoint Portal Server WebParts 8dxr Unexpected SearchBoxEx AfterDeserialize begin
w3wp.exe (0x1454) 0x164C SharePoint Portal Server WebParts 8dxt Unexpected SearchBoxEx AfterDeserialize end

Edit the results.aspx page and Check if the “Search Core Results” web part is present.
If no then the issue is resolved by adding the “Search Core Results” web part which is missing.
If you see the web part in the results.aspx page, then the issue is due to Invalid XML information is passed to the “Display Discovered Definition” feature.

What next ???

Click on Modify Shared Web Part and uncheck the “Display Discovered Definition” Feature.
Then Click on OK and publish the page
Now you should be able to get the search results.

Small description about “Display Discovered Definition” Feature which I could find online
The Definition Extraction feature finds definitions for candidate terms and identifies acronyms and their expansions by examining the grammatical structure of sentences that have been indexed (for example, NASA, radar, modem, and so on). It is only available for English. Definition extraction feature in MOSS 2007 is a feature that extracts meaning of definition from indexed text. User enters a search query “X”, search returns from the document index a ranked list of sentences containing definitions of “X”, such as “X is Y” with links to the documents in which the definitions were found. In MOSS, implementation definitions are extracted from free text rather than from glossaries.
Definition Extraction feature is integrated with Search Feature at Crawl/Indexing and Query times. During the crawl, tokens with alternate definitions are added to search database. At query time passed search token is compared with existing entry in definitions database. If a match is found the definitions link is populated at the bottom of the search results page. Collapsing the link shows number of definitions.
It’s a default setting and cannot be customized. You can turn off Definition Extraction by Editing the Search Centre results page in question, modifying the Search Core Results web part, and turning off ‘Display Discovered Definition’.

Hope the above information is helpfull

When you start Crawl on SPS 2003 "The address could not be found, (0x80041209 - Cannot Connect to the server. Please make sure the site is accessible. )"

smungara — Fri, 10 Apr 2009 16:58:00 GMT

When you try to run the Crawl in the SharePoint Portal server 2003 you see
Gatherer log shows:
The address could not be found, (0x80041209 - Cannot Connect to the server. Please make sure the site is accessible. )

First try to browse the site from the Web front end servers.
Run the PROXYCFG from all the SharePoint servers including Index server
Run PROXYCFG -u to uninstall the Proxy setting from the Registry and IE

After running the above command you still get the same error then follow the next steps
Try browsing the site from the index server, and you will get an "Page not Found"
When you ping with site name, that will fail
Run NSLookup on site from the index server
Ping the IP which is resolved using the NSLookup, and you should be successful
Add the IP to the hosts file in C:\Windows\System32\Drivers\etc
Now you should be able to browse the site from the index server
Now you should be able to start the crawling on the SharePoint Server 2003 successfully

While try to browse SharePoint Portal site get an error "Cannot connect to the configuration database"

smungara — Wed, 01 Apr 2009 14:20:00 GMT

When you try to view your Microsoft SharePoint Portal Server 2003 Web site, you receive the following error message:

"Cannot connect to the configuration database"

This behavior occurs for many reasons. I have mentioned the workaround for one of the reason where the issue was with MDAC 2.8 SP2 installation broken

We created a UDL file to check the connectivity between SharePoint Portal server and SQL server

When we run the UDL file we get an error RUNdll32.exe "The procedure entry point SystemParametersInfoI could not be located in the dynamic link library MSDART.DLL."

When we click ok we get an error "Error loading C:\PROGRA~1\COMMON~1\System\OLEDB~1\oledb32.dll The specified procedure could not be found."

Check for the version of the MSDART.DLL files in the following location

%windir%\System32

%windir%\System32\Dllcache

%windir%\ServicePackFiles

If you find differences in the file versions then run the below command which is explained in http://support.microsoft.com/kb/889114

C:\>copy %windir%\system32\dllcache\msdart.dll %windir%\system32

Choose Yes

Now try to run the UDL file, if it fails again

Then run the component checker against MDAC 2.8 SP2

Click on the link for MDAC Utility: Component Checker

You will find couple of files missing

To fix the missing files

Browse to C:\windows\inf folder in windows explorer,

Right-click on mdac.inf and select Install,

Then when prompted for i386 places go first to C:\windows\servicepacks, and then if files still can't be found, point to your CD or C:\i386 folder.

Finish the installation

Do an IISreset

You will be able to run UDL without any error

Now you should be able to browse the SharePoint Portal Server 2003 sites

No results are returned when using properties “Created by” and “Last modified by” in SharePoint 2007 advanced search

smungara — Thu, 05 Mar 2009 11:12:00 GMT

RESOLUTION:
******************
1.Install Infra Updates for WSS 3.0 and MOSS.
2.Open Central administration
3.Shared Services
4.SharedServicesX (X being the number of the shared services provider for the site you are creating a mapping)
5.Search settings
6.Metadata property mappings
7.Click "CreatedBy" to edit the properties
8.Make sure "Include values from all crawled properties mapped" is selected
9.Click on Add Mapping
9.There are two Office:4(Text) crawled properties. Map the first Office:4(Text) crawled property to the CreatedBy managed property. Move Office:4(text) to the top in the order

10.Click "ModifiedBy" to edit the properties
11.Make sure "Include values from all crawled properties mapped" is selected
12.Click on Add Mapping
13.Map the Office:8(Text) crawled property to the ModifiedBy managed property. And move it to top in the order
14.Complete a Full Crawl.
15.In the Advanced Search page, edit the page to modify the Advanced Search Web Part.
16.On the right pane expand the properties and click on the properties
17.Turn <Option Name="AllowOpContains" Value="True"/> from False to True in the Advanced Search Web Part Properties' XML.
18.Save and Publish the Advanced Search page.
19.Search for values in Created By and Modified By properties. The text you enter should match verbatim.

SharePoint Products and Technologies Configuration Wizard, failes with error "Duplicate ID on Sequence microsoft.sharepoint.portal.upgrade.farmsequence"

smungara — Tue, 03 Mar 2009 12:38:00 GMT

SYMPTOMS:

*****************

while trying to run the SharePoint Products and Technologies Configuration Wizard, get the following error

ERROR MESSAGE (If applicable):

****************************************

Duplicate ID on Sequence microsoft.sharepoint.portal.upgrade.farmsequence

ENVIRONMENT:

*********************

Windows 2003 SP2, SQL 2005 SP2 and MOSS 2007 SP1

CAUSE:

*********

Cause not sure

RESOLUTION:

******************

Go to C:\program files\common files\Microsoft shared\web server extension\12\config\upgrade

you will find the file by name "SPSUpgradePremium.xml"

make a copy of the file

edit the file "SPSUpgradePremium.xml"

in your upgrade mapping file "SPSUpgradePremium.xml", there is an element, which looks like this:

Remove this one element from the file and your upgrade will run.

Once the upgrade finishes, please replace the file with the original file

ADDITIONAL INFORMATION: TO - RESOLVE

*******************************************************

in your upgrade mapping file "SPSUpgradePremium.xml", there is an element, which looks like this:

Remove this one element from the file and your upgrade will run

When clicked on SSP Search Settings link get an error "HTTP 403 Forbidden"

smungara — Tue, 03 Mar 2009 11:31:00 GMT

When we click on Search settings link in SSP administration page we get an error "HTTP 403 Forbidden"

To Resolve
***********
We captured the ULS logs and found access denied for the folder C:\Windows\Tasks folder
We then checked the properties on c:\windows\tasks folder and by default we will not see the security tab
To get the Security tab we need to run on command prompt "attrib –s %windir%\tasks"
We found the permission for account WSS_WPG was missing
We added WSS_WPG account to tasks folder and gave read and write permissions
We then added the attrib by running "attrib +s %windir%\tasks"
Did an IISrest
Now we were able to browse the search settings page in SSP administration page

PSconfiguration wizard fails to complete after installing new Patches

smungara — Sun, 22 Feb 2009 12:19:00 GMT

SYMPTOMS:

*****************

while trying to run the SharePoint Products and Technologies Configuration Wizard, get the following error

ERROR MESSAGE (If applicable):

****************************************

The specified SharedDatabase Name=Sharepoint_SSP1_AdminDB Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object."

ENVIRONMENT:

*********************

Windows 2003 SP2t, SQL 2005 SP2 and MOSS 2007 SP1

CAUSE:

*********

Cause not sure

RESOLUTION:

******************

Go to Registry editor

Browse HKLM\Software\Microsoft\Office Server\12.0\BuildVersion

Check the build number

If its 12.0.4518.1016

Manually edit the value 12.0.6219.1000

Close the registry editor

Run the PSconfiguration wizard and it will be Successful

ADDITIONAL INFORMATION: TO - RESOLVE

*******************************************************

The Error says " The databases are been upgraded to a newer version. Please upgrade this SharePoint application server before attempting to access this object"

where the Binary is on a lower build then the database

When we checked on the central administration window, it shows 12.0.6332

when we checked the above registry key found even after installing the SP1 on the MOSS Server the build was 12.0.4518.1016, as it should be 12.0.6219.1000

When installing the Cumulative, it will check the build version in the registry, where it was 12.0.4518.1016