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

08 September, 2013

Failed to start workflow. This server is not licensed + Nintex 2010 + SP2010

Problem description:
Some users reported that there are workflows with errors. This error occurs it looks like there is some issue with the license on a farm’s server.

Error message:
Failed to start workflow. This server is not licensed.



Probable Possibilities:
The server admins are incorrect; the Nintex licenses are not configured correctly.  If this were true, I would expect the error to occur more frequently, and not just when multiple workflows start.  For example, I would expect a workflow manual start to occasionally throw the error.

There is a problem with the way Nintex checks for licensing when workflows are distributed among front-end servers or queued up for execution.

Resolution:
If you are facing this error then request you to see the following thread and you will get the answers that you are looking for:

Thank you.

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