Empty SharePoint’s Recycle Bin

If you have a lot of items in your SharePoint recycle bin, it will be a pain to select items and delete them page by page.

Here is a cool trick to empty the recycle bin without paging through them


6 Things that you think will work in SharePoint but doesnt

  1. When you have a Gantt view of the Task List, Web part connections are unavailable.  Hence you cant filter a Gantt View using the Filter Web Parts
  2. DateTime columns cannot be used for Grouping in the Content Query Web Part out of the box
  3. You cannot use the PortalSiteMapProvider to retrieve Navigation items from another site collection
  4. If you have a Date Column in a List, it cannot be used as a Lookup Column on another List
  5. If you activate a Feature on a site and then save it as a Site template and create a new site from this template, the FeatureActivated code doesnt fire
  6. You cannot write back to a List from Excel 2007.  This was available in Excel 2003. You will need Access for writing back to a List from Office (Update: Refer to WorkerThread’s link below for an add-in)

If you have any more of these oddities, please post in the comments and I will update this list

Edit: When you use the Content Migration APIs to copy lists and libraries from one farm to another, person fields do not copy over correctly

Create Publishing Pages on custom Document Libraries in SharePoint

Have you ever wanted to create pages in your custom document libraries in MOSS 2007 ?

When you click on Create Page under Site Actions, it always defaults to the Pages library. Well not any more.

Here is a great post on how to work around that limitation.


Some things to note after making these changes

  1. Import the Microsoft.SharePoint.Publishing namespace in your custom page
  2. Enable the Page Content Type for the document library for it to show up in the dropdown list

MOSS 2007 ULS Logs Folder in 12 Hive is Empty!


The Microsoft VHD for MOSS 2007 is a great time saver.  You can download the VHD from here

Download MOSS 2007 VHD

I am working on a demo for BDC and ran into some issues.  As usual when I looked at the 12 hive folder there were no logs.  Not a single log file.  I logged into the Central Admin Console and setup the Logging parameters and still nothing. 

I thought this might be related to the Timer service being corrupted and hence restarted the timer as well to no avail.

Poking through the services, I noticed that the Windows SharePoint Services Tracing service was disabled.  I set the service to Automatic start and the logs started to fill up.  It makes sense to disable this in a VHD by default, but a valuable lesson was learned. When some one else builds an MOSS 2007 image, do not assume all the services are on!

Sharepoint – Managing Access Requests email

The SharePoint administrator for our client recently changed teams. She was still receiving all the access request emails and wanted us to move it to another user. This took quite a bit of snooping around, since the option is not available front and center in the Site Settings page. We looked at all the security groups and checked to see if there were any access request emails set up on the groups. All those groups looked fine, but she was still getting those emails. Then we looked at the site permissions and sure enough there was an option under Settings called Access Requests with her email in it.


SharePoint Single Signon Error 0x8063064a

Our environment had 2 front end servers with MOSS 2007. The single sign-on service was leveraged within the web parts and everything worked fine on one server. However the following message was found in the event log on the second front-end server.

Event Type:    Error

Event Source:    Office SharePoint Server

Event Category:    SSO

Event ID:    6494

Date:        7/1/2008

Time:        2:43:21 PM

User:        N/A


The Microsoft Single Sign-on (SSOSrv) service failed to store credentials for user <DOMAIN\UserName>, enterprise application definition postini. The error returned was 0x8063064a. For more information, see the Microsoft SharePoint Products and Technologies Software Development Kit (SDK).


The Microsoft Single Sign-On Service was running as “LocalSystem” on the second server. Once we changed that to run as the MOSS 2007 application pool account, everything started working back as usual.

Unable to find file RSSharePointSoapProxy error in SQL Reporting Services SharePoint mode

After installing SQL Reporting Services on our Web front end servers, our Sharepoint site crashed and burned with the following error in the event log

Unhandled exception was caught:
System.Configuration.ConfigurationErrorsException: Could not load file or
assembly ‘RSSharePointSoapProxy, Version=, Culture=neutral,
PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system
cannot find the file specified. (c:\inetpub\wwwroot\web.config line 68) —>
System.IO.FileNotFoundException: Could not load file or assembly
‘RSSharePointSoapProxy, Version=, Culture=neutral,
PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system
cannot find the file specified.
File name: ‘RSSharePointSoapProxy, Version=, Culture=neutral,

We had just installed the SharePoint Reporting Services add-in , so were sure that the necessary assemblies were on the server, since there were no errors during the installation. However we noticed that the installation was done with a non-admin account.


Running the installation using the same service account as the SharePoint application pool resolved the issue

SQL Reporting Services and SharePoint Integrated Mode 401 errors

After setting up SQL Reporting Services in SharePoint Integrated mode, trying to access the Report Server site using http://<remoteserver>:8080/ReportServer gave 401 errors. One weird thing that we noticed was when trying to set authentication to NTLM on our IIS web site, our values were getting reset to Anonymous access. A quick Google search brought up this post, which had the fix for the issue


Run the following from a command prompt within the C:\inetpub\AdminScripts folder

cscript adsutil.vbs set w3svc/NTAuthenticationProviders “NTLM”

Here is the link to the post





SQL Reporting Services Install issue in SharePoint Integrated mode

When trying to set the Web Service Identity within the Reporting Services Configuration Manager in a SharePoint integrated mode , we encountered the following issue

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070003
   at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

At first we thought the WMI provider was corrupted and tried to go that route for resolving this issue. After quite some time we figured that it may have been something with the applicationPool and hence started looking at the Web site configuration within IIS. Sure enough, in the ASP.NET tab for the web site, there was no entry for the ASP.NET version. After setting the value to 2.0 , we re-ran the configuration and the issue was fixed.


Check to make sure the right ASP.NET version is selected on your Reporting services website.  While you are there ensure that the ASP.NET web service extension is set to Allowed.  If these dont fix your issue running the aspnet_regiis -i might help as well ( I havent tried this!)

SharePoint Incoming emails not picked up

Incoming emails not picked up in MOSS 2007

 When trying to setup email enabled document libraries, we setup the front end server with the SMTP service. On sending emails we saw the emails getting deposited into the C:\Inetpub\MailRoot\Drop folder. However the emails were not getting picked up and routed to the service. We tried to restart the Timer Service, gave folder permissions and nothing seemed to work. Upon checking the event logs we found the following entries

A critical error occurred while processing the incoming e-mail drop folder.
The error was: Value cannot be null. Parameter name: path.

Source: Windows SharePoint Services 3
Category: EMAIL
Event ID: 6872;

“The Execute method of job definition
Microsoft.SharePoint.Administration.SPIncomingEmailJobDefinition (ID
d7c219ba-839d-4580-adc2-fa512a8cb833) threw an exception. More information is
included below.
Value cannot be null.
Parameter name: path”

Source: Windows SharePoint Services 3
Category: TIMER
Event ID: 6398″

This looked like the incoming email drop folder was not setup properly in the Central Admin Console. We checked and sure enough the drop folder was empty. Setting that value fixed this error. To set the drop folder

Central Admin-> Incoming email settings

Click Advanced and type in the email drop folder.

 Here is a great whitepaper on how to setup incoming emails (Whitepaper)

%d bloggers like this: