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!)

Live Mesh UAC no longer required

I got this email yesterday from the Live Mesh team


  1. Live Mesh is now available in all English-speaking countries (not just the U.S.)

  2. Removed the User Account Control (UAC) requirement when installing and using Live Mesh with Windows Vista SP1

  3. Index for Desktop Search now works with Live Mesh folders

  4. Fixed bug where an underscore in a Hotmail account name returned an “Invalid Hotmail Address” error

  5. Fixed bug with Silverlight 2 Beta 2 failing to load in Silverlight Media View

  6. Fixed bug where the notifier tooltip incorrectly indicated that Live Mesh Remote Desktop was unavailable for a computer running in non-admin mode

  7. Fixed bug where the Live Mesh folder icon was not displayed in the e-mail inviting someone to share a folder

  8. Fixed one of the bugs that caused Live Mesh to fail to start

  9. Fixed problem with Live Mesh returning errors when waking from sleep/hibernate

It is great news that UAC is no longer required!


Live Mesh install on Windows Server 2008

I blogged here about not being able to install Live Mesh on Windows Server 2008, which I am running as my main workstation.

MsftGuy has a solution for this issue.  Basically you run the LiveMesh.exe from the command line with the -force argument.

Thanks for the tip! Helped me a lot



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)

Allowunsafeupdates and Sharepoint – A technical overview

Pavlov’s got a great post on AllowUnsafeUpdates and Cross-site scripting.  A must read for all SharePoint developers.



Sharepoint Deployment Planning Services

If you are a Microsoft partner, great news is here. Microsoft is planning to pay for a 10 day engagement in SharePoint deployment called SDPS. Partners with Information Worker competencies can qualify.  More details here


My firm is planning to get qualified too.  Apparently we need individuals who have passed 70-630 and 70-631.  

Planning a SharePoint solution

Ishai has a great post here on how to plan a Sharepoint solution.  Great Post for all developers/architects



Close InfoPath Forms Services form using Code

I was working on a way to close an InfoPath form using C# or VB.NET from the form code-behind after the user submits the form. The steps below help in running some custom code to save the data and then close the form.

Here are the steps to close the Form

  • Set the Submit Action[Tools->Submit Options] within InfoPath for the form to “Perform custom action using Code” . Click the Edit Code option to submit the form using code
  • Set the After Submit option under Advanced to “Close the Form”


Click the Edit Code button next to the perform custom action to submit the data. Editing the code adds an handler for the Form Submit event and a FormEvents_Submit method is created in the code behind. Once the code completes the submission, set the CancelableArgs.Cancel property of the SubmitEventArgs to false.

Here is a sample FormEvents Submit method

In the SubmitConnection method, I retrieve the required data connection and call the execute method for submission

Dim fileSubmit as FileSubmitConnection = CType(Me.Connections(“SharePoint Save”),Microsoft.Office.InfoPath.FileSubmitConnection)


In the above sample, the data connection that I want to use for Submit is named “SharePoint Save”. I typecast it as a FileSubmitConnection.

I found this solution on one of the forum posts


%d bloggers like this: