Pages

30 December, 2013

Today i would like to share a simple and easy topic as it’s a
good idea to choose a title that describes your team or project.

1.Open
your SharePoint site

2.Settings

3.Site
settings

4.Under
the look and feel

5.Click
title, description and logo

6.To
upload your logo from your computer

7.Click
From Computer

8.Click
Browse

9.Locate
the image and click Open

Additional option- You can also upload the
image in your SharePoint document library and select it from there as- browse
to the library where the image is stored, select the image and click Insert.

Click OK and that’s it.

Image will be successfully uploaded and site
logo can be change without any problems.

Note:If you don’t see Title, description, and logo, you
probably don’t have permission to manage that option. You need to have at least
permissions equivalent to being in the Owners group on your site.

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

29 December, 2013

This is my first post on Amol's SharePoint Knowledge Base Blog . I will be starting my posts off with a Quick Fixes Series . The purpose of this series will be to provide immediate solutions to several niggles and quirks in SharePoint that we face on an everyday basis . I will not be diving in depth into the mechanics . Its intended to be a quick solution to your issues.

Lets get started !!

We all of us in development have faced the nagging issue at some point in time of the Default Custom Error Page, this occurs when we have deployed some new code related to web parts or event receivers , or in general for several issues , including deletion of content types etc.

Before we run into the SharePoint ULS Logs or the event viewer or worse yet start debugging the code let's take a moment and let SharePoint show us the actual error.

Step 1:

The first step we need to take is to the change the web.config in the virtual directory of the web application which should ideally be present under a path similar to this : inetpub\wwwroot\wss\Virtual directories folder\[Central Admin PortNo]\web.config

Inside this web.config we should the following entry <customErrors> mode . This attribute will be having a value "On" . We need to change it to "Off" . Make sure you type it in the same way , the words are case-sensitive.

Step 2:

Next we need to find an attribute <SafeMode> CallStackin the same web.config as above . This will be having a value of "false". We need to go ahead and change it to "true".

Step 3(Optional) :

Next we need to find an attribute Debug . It should be having the value "false" by default . Go ahead and change this to "true".

So the 3 changes are :

CustomErrors=”Off” instead of the default CustomErrors=”On”

CallStack=”true” instead of the default CallStack=”false”

Debug=”true” instead of the default Debug=”false”

Once these 3 steps are done we should ideally see a more usable page such as the one shown below :

As you can see this is a much better page . We can go ahead and google the error from here and try and find a relevant fix.

Note:

It is very possible that even after above 3 steps we are still not able to see the error details .

In this case below are a few more troubleshooting steps that you can use to trace or view the error.

Additional Step 1:

There is another web.config present in the SharePoint hive under the _layouts folder . The layouts folder can be found under the path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14

Modify this web.config similar to Step 1 to have the customErrors attribute set as "Off"

Additional Step 2:

If the above does not work then we have another web.config present at the path : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\ADMIN\

Go ahead and change the customErrors attribute to "Off" in this one as well.

These 2 steps should definitely show you the detailed error page in your application if the first 3 haven't already worked.

In addition you can try and enable the default ASP.NET trace to view the errors as well.

This is done by going to web.config again in the virtual directory of your web application i.e the one at :inetpub\wwwroot\wss\Virtual directories folder\[Central Admin PortNo]\web.config

Here find the <system.web> element of the web.config file .

Under this element add the following line : <trace enabled=”true” pageOutput=”true”/>

This will give you some errors traced by ASP.NET trace as well . However this will be useful only when combined with all the above steps.

IMPORTANT NOTE : Please do not forget to perform an IISRESET after all the changes as sometimes the changes in web.config do not reflect by themselves.

Perform an IISRESET and refresh your error page and i sincerely hope you can view a more explicable page than the one you started with .

Good Luck and watch out for more Quick Fixes from my end.

Don't forget to comment and ask your queries in the comment section . I'll get back with my comments ASAP.

22 December, 2013

Recently
I have started working in configuring SharePoint incoming email settings and
completed the functionality on positive note :)

Why I am writing this article? – While working on
this functionality I faced so many challenges and numerous error messages,
& I would like to share those experiences and resolutions so that it would
be useful for all the SharePoint communities.

I
worked on two different environments and every environment has different
challenges:

17 December, 2013

One more new query from end user so here it comes my
new article! Not query but actually an issue which requires some
troubleshooting and correct guidelines to proceed for the resolution. One thing
we need to understand that every issue requires thorough analysis and based on
those analysis points, we can resolve the issue. By means of writing such
articles, I would like to guide my SP-communities, SP audiences, my SP-friends /
my colleagues, SharePoint Administrators- a proper set of guidelines so that
they can resolve the issue and in case of any problems then please reach out to
me so that we can discuss on the same and proceed further!

Farm attributes:-

-2WFE’s,
1 APP, 2 SQL instances in clustering mode

-SharePoint
2013

-Windows
Server 2008 R2

-IE10

Problem
description:-

I
have created an anonymous site in SharePoint 2010 foundation and when i click
on sign in, it shows me "401 UNAUTHORIZED". The machine is on a
hosted environment and I am accessing it through a host header in extranet zone
of alternate access mapping path.

Error message:-

401
UNAUTHORIZED

Troubleshooting
steps:-

1)As
the site is anonymous then it does not have to ask for credentials. Make sure
that's not the case.

2)Make
sure that you have already followed all the guidelines as how to setup the
anonymous site across the complete site collection plus list and libraries.

3)It
might be browser specific so make sure that you test this scenario across
multiple browsers

4)As
this is an extranet site, so obviously customizations are there on the home
page as well. If that is the case then make sure the page is not check out. If
yes then please approve it and check the results

5)In
most of the anonymous cases, one most common issue happens i.e. If the web part
present on the home page need to query data from other list while anonymous
user has no permission to access those lists, then maybe you would get the
problem.

In my case, this is
the resolution:-

1)It
was a webpart causing the problem.

2)Present
on the home page which requires permissions to access that specific list as it
is fetching data from the external list.

3)Removed
the webpart

4)Checked
the results and works like a charm!

Product applies to:-

1.SharePoint
Server 2013

2.SharePoint
foundation 2013

3.SharePoint
server 2010

4.SharePoint
foundation 2010

If you have any queries/questions regarding the above mentioned
information then please don’t hesitate to reach out to me and I will try my
best to help you as much as i can!