26 February, 2014

25 February, 2014

You cannot delete a hidden column

Working on lot of tickets nowadays, trying to share as much as i can!

Today’s article is based on a simple issue but needs a quick trick to resolve it. I have resolved this issue within a quick span but it might be difficult for somebody to troubleshoot and will take lot of time to get stuck on the same. Just wanted to save your time by sharing this article, but still after following the below mentioned information, if your issue still remains unresolved then please drop a note in the form of comment and I would be there to help you!

Problem description
One of the users is trying to delete a column from a custom list but he is facing a very weird problem which might scare you initially, as hey what happening in my farm J

Error message
You cannot delete a hidden column. <nativehr>0x81020092</nativehr> <nativestack> </nativestack>


What’s the ultimate goal? – To delete the column!

Please follow these steps-

Resolution
a)   Open the list where you are trying to delete the column
b)   List settings
c)   Go to the columns section
d)   Click on the column that you want to delete
e)   Change the metadata of that column - example from single line of text to multiple line of text
f)    Click OK
g)   Click on that column again
h)   Hit Delete
i)     You would be able to delete that column without any problems.


If you have any queries/questions regarding the above mentioned information then please let me know. Thank you.

There has been a critical error while processing the form

One of our users has reported a concern that they are facing problems while opening the SharePoint list. When I checked the list then I could open it without any problems, further I checked the customizations but it’s an out of box list.

SP entities
a)   SharePoint 2010 site
b)   Internet explorer 11
c)   Permissions- contributor

Here is the error message that I was talking about:-

Error Message-1:
Object doesn't support property or method 'addeventlistener'

Error Message-2:
There has been a critical error while processing the form.



Troubleshooting
1.   Check in different machine to isolate the issue
2.   Check in different browsers to make sure that browsers are not the culprit
3.   Check the user permissions
4.   Check for any customization's
5.   Check the firewall restrictions

Resolution
SharePoint 2010 does not recommends/support IE11
1)   Open the IE
2)   Tools
3)   Compatibility view settings
4)   Enter the URL of your SharePoint site (without default.aspx / Home.aspx) in the “Add this website” section
5)   Click on Add
6)   Close
7)   Close the Internet explorer
8)   open your SharePoint site in a new IE
9)   Check the results and confirm!


In case of 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.

How to monitor SharePoint – Part -2


If you have any queries / questions regarding the first part then please feel free to ask so that we can discuss and proceed further…

We are going to discuss the remaining sections today in descriptive manner-

Usage data and health data collection
 As we discussed, ULS, Event Viewer logs, SharePoint Health Analyzer are vital enough to provide the cause behind the issues but sometimes not everything gets captured inside these logs, example-

1.   Traffic Reports - How many hits a page got, how the user got there, and what browser they used to get there.
2.   Search Reports - What was searched for, top clicks, failed queries.
3.   Inventory Reports - What space is being used by whom, how many sites you have, what languages those sites use.

"Site usage reports" have been renamed as Web Analytics.

You can access Web Analytics reports by going to Site Actions -> Site Settings.  Under the Site Actions heading you will see two links, Site Web Analytics Reports and Site Collection Web Analytics Reports.

Inventory Reports:
The inventory reports are targeted to help the site administrators in managing the site by keeping track of the site structure and storage and version issues.

1.   How much disk space is being consumed?
2.   How many sites have been created?
3.   What languages are in use?

Developer Dashboard

Developer Dashboard is one of the clean and neat tools to troubleshoot performance issues. This functionality is disabled by default but pretty useful. With the help of developer dashboard (DD), we can easily recognize type of problem, either programmatically by using the object model or visually by looking at page output, critical events, database queries, service calls, and SharePoint requests allocation.

How to enable this:-
$svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService
$ddsetting=$svc.DeveloperDashboardSettings
$ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$ddsetting.Update()

Best Practices on Memory Leak
Microsoft has created an awesome too to find out the memory leaks.


If you have any questions/queries then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Product applies to:
a.    SharePoint Server 2010
b.    SharePoint Foundation 2010

References:
Capacity requirements for the Web Analytics Shared Service in SharePoint Server 2010: http://technet.microsoft.com/en-us/library/gg440601.aspx

Reporting and usage analysis overview (SharePoint Server 2010)

Web Analytics in SharePoint 2010: Insights into Reports and Metrics

24 February, 2014

How to monitor SharePoint? - Part -1

Monitoring- Looks very simple, isn’t it? J One of the most debatable / discussable topic in today’s SharePoint market but let me tell you guys, this terminology has a very broad scope and that’s why big organizations invest heavily on third party tools to get appropriate output as per the desired requirement.

1.   Why the monitoring has so much importance?
2.   Why the monitoring has gain a huge demand right from the day 1 of the SharePoint birth?
3.   Is this monitoring – a need of the time?
4.   Don’t we have out of box (OOB) monitoring options available?
5.   Why we are so dependent on the third party tools? Just because these tools are simplifying your output in an easy manner?  

Why monitoring is needed in SharePoint?
a)   To ensure the availability and reliability
b)   To identify potential errors before an error causes problems
c)   To notify administrators when problems occur

In this today’s article, we will explore the default monitoring options / OOB options which need to be evaluated properly so that we can use them in an appropriate manner.

First of all- Let me share the CORE OPTIONS that we can use OOB-
A.   Diagnostic logging
B.   SharePoint Health analyzer
C.   Usage data and health data collection
D.   SharePoint Developer Dashboard

Every core options has so many nested sub sections that I am going to share now-

Diagnostic logging:
Diagnostic logging / ULS logs- pretty useful utility in terms of troubleshooting any issues. ULS logs will give you the root cause behind the actual issue. SharePoint tracing service is responsible for the creation of ULS logs, If this service gets stopped then you won’t be able to see the ULS logs so make sure this service always in started mode.

Where you will find this service:
Start -> Run -> Services.msc -> SharePoint Tracing Service.

Where you will find the ULS logs:
C:\Program Files\common files\Microsoft Shared\Web Server Extensions\14\Logs

Note: If you have customized the location then you will find in different drive but path will be same.

Which tool will be useful to analyze the ULS logs: ULSViewer.exe
You can download from here: http://ulsviewer.codeplex.com/

Where you will find this section in SharePoint?
a)   Open the Central Administration
b)   Monitoring
c)   Configure diagnostic logging
d)   Select all Categories
e)   Select the following default settings-
§  Least critical event to report to the event log - Warning
§  Least critical event to report to the trace log – Unexpected
f)    Enable this option- Enable Event Log Flood Protection
g)   In the path section, you can configure the location where you want to store the logs
h)   Number of days setting which specifies the log validity.

SharePoint Health Analyzer (SHA):-
SHA is equally important; in fact I can say this is so powerful which will give your complete statistics of your SP environment.  This tool is an enhancement / introduced in this SP 2010 version as it was not there in SharePoint 2007/previous versions.

What’s the specialty of this tool?
a.    Identifies problems
b.    Recommends solutions
c.    Repairs the functionality itself
d.   Automatically resolves the problem
e.    These checks run on an hourly / daily / weekly or even monthly basis.

Where you will find this utility in SharePoint?
a.    Open the Central Administration
b.    Monitoring section
c.    Health Analyzer
d.   Review problems and solutions

Who is working under the HOOD?
Curious to know- Right? These rules and alerts are based on Timer Jobs so basically there are so many jobs are running in the background that runs on daily/weekly/hourly/monthly basis.

Still writing on the remaining two core sections that I will cover in the next post. Stay tuned :)

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.