ERROR HRESULT E_FAIL while working on audit reports - Resolved

Problem description:

Facing an issue here in Audit Reports. The issue is when one site collection admin tries to run the Security Settings Audit report the report is getting generated successfully; however if another site collection admin tries to run the same report he gets an error. When checked in to the log files the error was "System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component. At System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal”

Error message:

HRESULT E_FAIL has been returned from a call to a COM component. At System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal

Logs:

System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component. at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.Office.Server.OpenXml.Internal.ByteStream.Write(Byte[] rgb, Int32 offset, Int32 cb) at System.IO.BufferedStream.FlushWrite() at System.IO.BufferedStream.Flush() at System.IO.StreamWriter.Dispose(Boolean disposing) at System.IO.StreamWriter.Close() at System.Xml.XmlTextWriter.Close() at Microsoft.Office.RecordsManagement.Reporting.AuditReportGenerator.CloseDataPart() at Microsoft.Office.RecordsManagement.Reporting.AuditReportGenerator.Dispose() at Microsoft.Office.RecordsManagement.Reporting.ReportData.CloseCurrentReport() at Microsoft.Office.RecordsManagement.Reporting.ReportData.Dispose() at Microsoft.Office.RecordsManagement.Reporting.ReportBase.AggregateReports(Hashtable query, SPFolder folder, ReportNameGenerator reportNameGenerator) at Microsoft.Office.RecordsManagement.Reporting.ApplicationPages.CustomizeReport.OKBtn_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Troubleshooting steps:

1.   Working for few users so it’s not a global issue

2.   Working in other browser but not in IE

3.   There are no multiple domains for whom it’s not working

4.   No restrictions on user accounts via GPO

5.   No errors in the event logs

6.   Other SP functionality is working fine for those users for whom auditing is not working

Resolution:

1.   For whom it’s not working, let him logged in to the SharePoint site

2.   Open the SharePoint site

3.   IE -> Tools -> compatibility settings

4.   Check "Display all websites in compatibility view".

5.   Add your SharePoint site on the top ("add this website" section) if its empty (by default it takes but sometimes it’s not)

6.   Refresh it and check the results

Product applies to:

a)   SharePoint Server 2010

b)   SharePoint Foundation 2010

c)   SharePoint Server 2013

d)   SharePoint Foundation 2013

Health check page throwing 404 - File or directory not found - NLB configuration

Today I was working on configuring the network load balancer for our web front ends. Let me give you some details on this before I start explaining the issue – NLB configuration can be done in two ways as follows:

1.   Health check file (Recommended one) – running IIS required.

2.   TCP port based health check

I was using the recommended way i.e. first one (health check file). We have 5 web front ends, while doing the configuration; you need to place this file on all the 5 web front ends. Why? – Good question! – If one server goes down then the requests will automatically get routed to the next available server.

Once you have placed the file then you need to browse that file in browser, just to make sure that you are getting the reply like this – http://108.34.45.145/healthcheck.txt

Proper output should be there, if not then there is something wrong in configuration. I faced the same problem as I was getting the reply from one server only and remaining servers were throwing the following error message:

404 - File or directory not found.

HTTP Error 404.0 - Not Found the resource you are looking for has been removed, had its name changed, or is temporarily unavailable

If the one server is giving me a proper output then the question is why the other servers are not working! There should be some problem in configuration, let me clear – not from the NLB side but from the IIS side.

I checked the IIS of the server where it was working and compare it with the remaining ones but didn’t find any differences.

So I tried browsing the local host site which is by default there in IIS – You should get IIS construction page. I tried browsing this IIS default website from the servers where I am not getting the output and result was same i.e. default website giving me “webpage cannot be found”

Why the default websites giving me error message? – The reason is so simple as they are in stopped status J

The server where it’s working, I checked the status of the default websites and it was in started mode. So the bottom line is - Sometimes solutions are simple but took some time to figure it out.

Resolution for this issue:

If you are working on NLB configuration with respect to health check page then make sure the default web site in started status.

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.

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Product applies to:

1.   SharePoint Server 2010

2.   SharePoint Foundation 2010

3.   SharePoint Server 2013

4.   SharePoint Foundation 2013

5.   SharePoint Server 2007

The site collection containing this sandboxed solution has exceeded its daily resource usage quota

In this article, we will discuss on resource usage with respect to Sandboxed Solutions.

Every time we will learn more and more when there is an issue and we start our analysis, troubleshooting, reproducing the issue and many more! – This is not going to stop J in fact nobody want to – J

I had a ticket in which user was facing the issue – he has uploaded a solution package inside solution gallery but as soon as he tried adding the webpart then he was getting the following error message

The site collection containing this sandboxed solution has exceeded its daily resource usage quota

Quite strange because uploading a package and the error in the next 5 mins – don’t you think something is wrong here? I have checked the resource usage of that solution-

1.   Open the site in which you have uploaded the solution (.WSP)

2.   Site actions

3.   Site settings

4.   Galleries

5.   Solutions

You will see the complete usage here – see the following screenshot.

From the above screenshot, it’s very clear that the resource usage is 0 but still I am not able to add the webpart :) then I thought it might be a permission issue so I tried with the farm account but same problem L - OK, permission is not the issue! – cleared.

Then I thought it might be browser specific so I tried in Mozilla as well as chrome to test the functionality but no changes in the result i.e. same problem – OK, browser is not the issue – cleared.

I checked the ULS logs to get more clarity, additionally event logs but didn’t find anything relevant.

Then I checked the timer jobs in case of any failures but everything was fine there also.

Then I thought there should be some setting from where we can set these resource usage numbers and finally I found it, LOL the setting that you see regularly gets sometimes ignored by us. Start thinking guys and hit the target!

Yes, you are right – “Configure quotas and locks” – by means of this you can check the actual “Sandboxed Solutions Resource Quota”.

So when I checked this then I found out that there were no numbers in the textboxes.

1.   Open the central administration

2.   Application management

3.   Configure quotas and locks

4.   Select the appropriate site from the top dropdown and specify the following numbers

By default these are numbers:

Limit maximum usage per day to: 300

Send warning e-mail when usage per day reaches: 100

Set this numbers and you should be good to go J

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.

Notes: if you are facing this problem in reference to Office 365 then here is the Microsoft endpoint: http://support.microsoft.com/kb/2536051

The Business Data Connectivity Metadata Store is currently unavailable

BDC, Everybody aware as it was there in MOSS 2007 / SharePoint 2007 but now we have BCS – Business connectivity services, one of the important features in SharePoint 2010. Whenever we need to bring external content / connect to external content types then BCS comes into picture. Today’s article is also based on one of the BCS issue which I came across and resolved it with proper analysis and troubleshooting.

Problem description:

One of our users trying to connect to ‘External content types’ by means of SharePoint Designer and facing the following error.

Error message - 1:

The Business Data Connectivity Metadata Store is currently unavailable.

Error message - 2:

There is no business data connectivity service associated with the current web context.

We haven't used the BCS before so this is the first time we came across this error so when I started exploring our farm then I noticed that one of mandatory requirement to make this functionality working is – Service Application.

Point #1: Make sure you have the BCS service application (SA) exists.

So we have created the BCS SA and check the results but same problem i.e. same error message.

Point #2: Make sure you associate this service application with the respective web applications on which you have the site collections.

How to do this? – Here are the details.

1.   Open the Central Administration

2.   Application management

3.   Service applications

4.   Configure service application associations

5.   Make sure its listed under ‘application proxies’

Point #3: BCS service application has a dependency on managed metadata so make sure the managed metadata service application already exist in your environment. If it’s not then please create it.

Point #4: Make the account that you have used for creating the BCS service application has necessary permissions on the web application database.

Point #5: Make sure the Business connectivity service is in started mode via Services on Server.

How to check this? – Here are the details.

1.   Open the central Administration

2.   System Settings

3.   Servers

4.   Manage services on Servers.

5.   Check the respective service i.e. BCS and start it if it’s in stopped status.

That’s it – the issue should be resolved now after following the above recommendations.

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Sandboxed code execution request failed - Resolved

Today’s article is based on Sandboxed Solution. By means of this article, I am going to share some issues that I faced while activating the solution as well as adding the webpart on SharePoint site.

So basically what is Sandbox solution?

When we talk about ‘solution’ then only one term which will comes to your mind i.e. WSP (Windows Solution package). People often misunderstood this Sandboxed concept as something is going to affect the farm, the scope is based on web application, and it’s going to reset the IIS app pools but let me tell you the fact – Sandboxed solution are user code solutions. Now again the new terminology – what is ‘user code solution’?

One process leads to understand a new process- isn’t it interesting? J

User code solution means user himself can deploy this solution and activate it and does not required SharePoint administrator to deploy. This is a very fine concept in which the scope is restricted to the specific site collection only. I don’t want to talk about ‘farm Solutions’; otherwise this will misinterpret the purpose of this article.

Why Sandboxed solutions are so important:

Sandboxed solutions do not run in the IIS worker process, neither the IIS application pool nor the IIS server must restart.

It is not necessary for the SPUCWorkerProcess process to recycle to load the latest version of the solution.

Problem description:

One user opened a ticket by saying ‘he needs to deploy some package’. Further probing, I came across that he has a WSP file and wanted to use as Sandboxed.

Now the question is – How to configure Sandboxed if it’s not there in your farm?

Here are the details steps:-

Section: 1

1.      Open Central administration

2.      System settings

3.      Under Servers

4.      Manage services on server

5.      Activate this service “Microsoft SharePoint Foundation Sandboxed Code Service”

Section: 2

1.      On the same server which is hosting the Sandbox code service

2.      Click on ‘start’

3.      Administrative tools

4.      Services

Once this configuration done then you are ready to upload the WSF file to the solution gallery. – Where is this solution gallery?

·         Open your SharePoint site

·         Site actions

·         Site settings

·         Under galleries

·         Solution (http://yoursiteURL/_catalogs/solutions/Forms/AllItems.aspx)

Note: Make sure you have site collection admin access to upload the solution in the solution gallery.

Once the solution gets uploaded then you can activate that solution.

How to activate it? -> Click on the solution dropdown -> you will get the option of activate.

In my case, user was trying to add a webpart on the home page of the site but as soon as I select the webpart to add then boom! It throws an error message as following-

Sandboxed code execution request failed.

Let me tell you some story behind this: I have enabled the service only on the app server and not on the web front ends. So basically if I activate any service on app then it does not necessary to activate it on the other servers (WFE’s) – do you support this fact? – would like understand your views!

I negotiated my thoughts for a moment and started the service on rest of the front ends but then a different error comes into picture: see the following-

The Sandboxed code execution request was refused because the sandboxed code host service was too busy to handle the request.

I started exploring the CA, site collection features, site manage features and one link which caught my attention, that is – Manage User Solutions

Where is this link?

·         Open the Central administration

·         System settings

·         Manage user solutions

Once you will open this section then you will get two options:

·         All sandboxed code runs on the same machine as a request.

·         Requests to run sandboxed code are routed by solution affinity.

It took some time for me to understand these terminologies as by practical only you will come to know the actual results.

See the differences:

All sandboxed code runs on the same machine as a request: Sandboxed Code Service should be started on all the WFE’s.

Requests to run sandboxed code are routed by solution affinity: if you start the “Sandboxed Code Service” on app server only then also it’s fine.

So I stick with my logic and select the second point i.e. Requests to run sandboxed code are routed by solution affinity and disabled the service from rest of the front ends.

But the error is still there! I checked the logs, restarted the sandboxed code service, restarted the user code service but still didn’t make any difference.

Then here is the rescue – In our case we checked the state key value and ours was- 0x00023c00

Actual Resolution:

a)      On the server, click Start | Administrative Tools | Services.

b)      On the Services dialog, scroll to SharePoint 2010 User Code Host.

c)      Note the full user name in the Log On As column. You will need this information later.

d)      Open SharePoint Management Shell.

e)      Enter the following at the command prompt, including all punctuation.

f)       (Get-SPManagedAccount –Identity “username”).Sid.Value

g)      Replace username with the name you obtained in step 3. E.g., Domain\FarmAdmin

h)      This will return the user’s SID (Security ID), which you will use in a later step.

i)        Open the registry editor and navigate to:

j)        HKEY_USERS\SID you obtained earlier\SOFTWARE\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\SoftwarePublishing

k)      Be sure the State key value is set to 0x00023e00.

l)        Restart the sandboxed host service on all servers on which it is to run.

No need of server restart as well as IIS RESET.  

Check the results and you will be good.

If you find a different solution, please share as a comment so that everybody will get the benefit of the same.