Wednesday, February 8, 2012

Sad but true facts... SP2010


More than often we assume something will surely work in SP2010 since it behaves a certain way in scenarios... but alas! After spending hours, you finally come to know that it is a limitation....and is by Design.... here are some points worth mentioning which have kept me awake in my implementation days


1.       Timer jobs are run from the SharePoint Timer Service also known as owstimer.exe. To debug a timer job attach the debugger to the owstimer.exe process, set a breakpoint and wait until your timer job is executed. This could take minutes for each debugging session, so be patient! The deployment of a timer job is easy if you have a Template for 2005. However, redeploying a solution involves restart of the SharePoint Timer Service and IIS leading to a session reset for connected users.


2.      Calculated columns: Cannot use the ID column in the calculated fields. The simple truth is that the ID field does not exist before you save your new record in SharePoint list. Alternate solution could be to use a SP designer workflow, which updates the field. 

3.    Approver/Lookup Limitation - when I tried to add a new set of approvers (10) to my List here's what we have:
This view cannot be displayed because the number of lookup and workflow status columns it contains exceeds the threshold (8) enforced by the administrator.

Operations that exceed the list view threshold are allowed in the following time window defined by the administrator:
Daily, from 5:00:00 PM to 11:00:00 PM.


Well - this can be changed easily in central admin.
Go to you Central Admin–> Manage Web Applicaiton
Select your webapplicaiton–> Click on the General Settings–>Select Resource throttling
             Now look at List View Lookup Threshold and increase the number as per your requirement.
             However, this takes a toll on the performance of Sharepoint and hence is not recommended!

Alternate solution can be to divide your list in multiple lists so that it has just the required no. of approvers. Well, it takes some redesign effort to get this going, knowing the views need to be configured for the multiple lists!!


4.       The 'Microsoft.ACE.OLEDB.14.0' provider is not registered on the local machine. - get this error when you have tried to access the "Excel" data source!

I had to uninstall any office related products (office, Visio, SP designer) which were 32 bit version and then install AccessDatabaseEngine_x64.exe from the link below.


Top of Form

Bottom of Form


No comments:

Post a Comment