11 September, 2013

Webpart security + disable web part connections– SharePoint 2010

One of our developers has reported that he is trying to setup connection between two webparts but somehow the connection option is disabled.
There might be a possibility that you will not get a connection menu also.

By using Web Part connections, you can create or enhance your Web Part Pages. You connect Web Parts so that when you perform an action in one Web Part, it changes the contents of another Web Part.

Now the next question will arise as:
1)   Why the connection option is disabled?
2)   Why the connection menu is greyed out?
3)   Why the connection menu is not available?
4)   Is there any setting at the site collection level or at the web application level by which we need to turn on any feature/activate something…

Let me tell you guys there is a setting which is present at the web application level so need to whether its enabled or not.

How to enable this option?
1)   Open the central administration
2)   Application management
3)   Web applications
4)   Manage web applications
5)   Select the web application for which you would like to enable the option
6)   On the top-Ribbon-You will find an option as ‘webpart security’
7)   Click on it and you will get one frame window which specifies ‘security for web pages
8)   Here you will find the option of Web part connections
9)   Select the option “Allows users to create connections between Web Parts”

Click OK and that’s it. You are done. 

After doing this, still not able to setup connection between two webparts?


In which Microsoft has specified several reasons in which web part menu may not be enabled or visible on your web part page / The Connections submenu is hidden or unavailable:

1)   You are not using the correct browser. You must use Internet Explorer version 5.5 or later to create, modify, or delete a connection between Web Parts.
2)   The Web Part you are trying to connect from does not allow connections. You can try to find or import another Web Part that does what you want and that allows connections.
3)   The zone that contains the Web Part does not allow connections.
4)   The Web Parts were connected in shared view and so the connection cannot be changed in personal view. If you can, switch to shared view.
5)   You do not have permission to make Web Part connections.
6)   Web Part connections are not supported at the site.

Some other possibilities:

Only compatible Web Parts are available from the Connections submenu. This situation can occur for one or more of the following reasons:

The Web Part you are trying to connect to does not support making connections. Not all Web Parts are designed to be connected.

1)   The Web Part you are trying to connect from is not compatible with the Web Part you are trying to connect to because it has an incompatible Web Part type. This can occur for the following reasons:
2)   You are in personal view, the Web Part you are trying to connect from is a shared Web Part or personalized Web Part, and the Web Part you are trying to connect to is a private Web Part on the same Web Part Page.
3)   The Web Part you are trying to connect from is a private Web Part, and the Web Part you are trying to connect to is a shared Web Part or personalized Web Part on the same Web Part Page.
4)   The Web Part you are trying to connect to or from allows only one connection. To create a new connection, you must first remove the current connection from that Web Part.
5)   The Web Part you are trying to connect to is already connected to the Web Part you are trying to connect from through a different connection type. Web Parts can have more than one connection, but each connection must be to a different Web Part.
6)   The Web Part you are trying to connect to is not compatible with the Web Part you are trying to connect from because the Web Part is required to run on either a client or server. There are two situations that can apply:
7)   The Web Part you are trying to connect to currently runs on the client, and the Web Part you are trying to connect from runs on the server.
8)   The Web Part you are trying to connect to currently runs on the server, and the Web Part you are trying to connect from runs on the client.

In this case, the Web Parts you are trying to connect must both run either on the client or on the server.

For assistance, contact the site administrator.

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.

10 September, 2013

Datasheet view is disabled SharePoint 2010

Client machine attributes:
OS- windows 7
Explorer- IE9, 64-bit
SP version- SP2010

One of my users has reported an issue that he is facing some problems while using datasheet view. Further probing, we know the truth that he has created a custom list and then trying to click on ‘datasheet view’ but the option is disabled i.e. datasheet view is greyed out.

Error message:
This control is currently disabled.





Resolution:
Million thanks to Microsoft for publishing this KB and make it available to us to understand the background as well as resolution on this issue.


As per this article:
You can install the 2007 Office System Driver: Data Connectivity Components to enable the Datasheet component. These components are available from the Microsoft download center:

Concrete Fix:
Go for a 32-bit office version, rather than 64 bit.

The list cannot be displayed in DataSheet view – SharePoint 2010

One of my team mate working on the server where windows server 2008 R2 was installed, he tried switching the view from standard to datasheet and he got the following error:

The list cannot be displayed in DataSheet view for one or more of the following reasons:
- A datasheet component compatible with Miicrosoft Sharepoint Foundation is not installed.
- Your web browser does not support ActiveX controls
- A component is not properly configured for 32- or 64-bit support.

If you are facing the above mentioned error message then I would request you to check the installed office version first.

If you have any confusion as how to check the version then please refer the following link: http://www.howtogeek.com/howto/24259/beginner-discover-if-youre-running-the-32-or-64-bit-version-of-office-2010/

Why we are checking the office version? Is it necessary?

Yes, it’s very necessary to know the office version we are using whether it is 32 bit or 64 bit.

Microsoft strongly recommends the use of 32-bit (x86) versions of Office 2010, Project 2010, and Visio 2010 applications as the default option for all platforms.

Resolution:
Make sure you use 32 bit version of office.

FAQ: can we install 32 bit office on 64 bit OS? – Yes, absolutely no probs.

Once you install the 32 bit office in such problematic scenarios then I am pretty sure that your issue will be resolved. Thank you.

In case of any issues/queries then please feel free to contact, I would be more than happy to help you as well as resolves your issues.

Product applies to:

SharePoint Server 2010

SharePoint Foundation 2010

Unable to process create message + User Profile + Connection problems + Event ID:6306

Today my client has requested me to setup a new environment for SharePoint which will be used for deployment purpose.

Here is the farm entity:
§  2 WFE’s
§  2 APP servers
§  Windows server 2008 R2
§  SQL Server 2008 R2: active-passive clustering

While trying to create a synchronization connection in the user profile management then we were getting the following error:

Error#1:
Unable to process create message

Error#2:
No exact match was found

Event log contains the following event id:
6306

ULS logs throwing the following error:
Microsoft.ResourceManagement.Service: System.InvalidOperationException: Retrieve schema failed
   at Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.Create(String typeName, IList`1 createParameters, Guid creator, Guid cause)
   at Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.ProcessInputRequest(RequestType request)
   at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessInputRequest(RequestType request)
   at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
   at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
   at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey)
   at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
   at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Create(Message request)

Resolution:
Thanks to this following articles (Author- Balasubramanian Murugesan) who helped me to resolve this issue:


Reference:



Product applies to:
1)   SharePoint Server 2010
2)   SharePoint Foundation 2010

World Clock and Weather Web Part - SP2013

SharePoint is collaborative software intended to bridge the gap between remote locations within an organization or a network of people. This web part delivers a nice GUI display of time and weather and it helps keep all users connected to each others’ environments.



The Bamboo Solutions World Clock & Weather Web Part allows users to display local time and weather for selected major cities around the globe. It addresses a pretty basic need that SharePoint does not have out of the box.

In addition to supporting multiple presentation interfaces and look & feel options, the World Clock Web Part allows you to specify the size of each clock, direction (vertical or horizontal), and whether to display seconds for each clock. You can also re-order the clocks to match your requirements.

Happy to share some good news as Bamboo has released the world clock and weather webpart for SharePoint 2013.


Enjoy and Happy SharePoint to all of you…

Million Thanks 2 Bamboo Solutions!!