Thursday, August 8, 2013

Integrate Yammer with on-premises SharePoint 2013 environments

http://www.microsoft.com/en-us/download/details.aspx?id=39357

This white paper addresses how to replace the social features in SharePoint Server 2013 with equivalent Yammer features in a SharePoint Server 2013 on-premises deployment

Monday, June 3, 2013

What is SkyDrive Pro in SharePoint 2013 | Sharegate's Blog

What is SkyDrive Pro in SharePoint 2013 | Sharegate's Blog

Great explanation by the author Benjamin Niaulin. Thank you!

Thursday, April 25, 2013

Versioning Your Published InfoPath Forms

Versioning Your Published InfoPath Forms

Infopath template has version number, you can see the number via Form Options/Versioning. Also whenever you publish the infopath form, the version number is incremented.

A good practice of designing infopath form template is to show the version number on the form. You can add a calculated value field to the bottom of the form and set its default value to

substring-before(substring-after( /processing-instruction()[local-name(.)
  = "mso-infoPathSolution"], 'solutionVersion="'), '"')

Sohel's Blog: SharePoint 2010: Configure Kerberos Authentication...

Step by step instructions on how to configure Kerberos Authentication with SharePoint 2010

Sohel's Blog: SharePoint 2010: Configure Kerberos Authentication...: SharePoint 2010 supports two authentication mode: Classic mode and Claims based. Today I’m going to explain how to configure Kerberos authen...

Friday, April 19, 2013

IE 8 shows javascript error when displaying SharePoint 2007 site

All the way to the left of the IE status bar, there is a yellow exclamation mark with "Error on page." text. Double click on the text brings up a popup showing "Element not found" error in init.js file.

How to fix: run Office Diagnostics: Diagnose and repair crashing Office programs by using Office Diagnostics

If above does not fix the problem, then try repair the Office installation by going to the Control Panel.

If your installation of Office has custom or 3rd party add-ons, consult your administrator before running the Office repair, since the repair can potentially break those add-ons.

Your mileage may vary and good luck!

Monday, March 18, 2013

How to: Set up People Search in SharePoint 2013

Good article by Corey Roth

Here is the link: http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2013/01/03/how-to-set-up-people-search-in-sharepoint-2013.aspx

Thursday, March 14, 2013

Make a radio button in InfoPath form read only


Conditional formatting is the answer. To set the control to always be disabled do the following:
  1. Right click on your field and select Rules
  2. Create a new formatting rule and click Condition
  3. Choose The expression from the dropdown 
  4. type true() or 1 in the text field (this tells InfoPath to always apply this formatting)
  5. Check the Disable this control checkbox.
  6. Click OK

Tuesday, January 29, 2013

Increase list attachment size limit

For document library, to increase the maximum upload size, the following change should be sufficient:

Central Admin > Application Management > Web Application General Settings, select the web application, set the Maximum Upload Size to the new value then hit OK.

In order to upload attachment with size greater than 50 MB, in addition to changes above, we also need to modify the web.config file. In the web.config file, replace with

There are other factors to consider when adjusting the maximum upload size, such as disk space, site quota, execution timeout, etc.





Wednesday, January 16, 2013

User Profile between SharePoint and AD out of synch

There are many reasons that user profile information displayed in SharePoint may be out of synch with the information in AD. One such reason is name change because of marriage.

If the Account Name is changed, you can use the "stsadm -o migrateuser -oldlogin xxx\abc -newlogin xxx\xyz -ignoresidhistory" command to migrate the old user to the new user.

For display name change, deleting the user from the site collection user information list should fix the problem. You can access this hidden list by going to http://xxx/_catalogs/users/simple.aspx page.
To delete the user, go to: http://xxx/_layouts/userdisp.aspx?Force=True&ID=xyz make sure id is correct for the user, then click "Delete User from Site collection".
 
You may also want to delete the user from the user profile of the central 
administration too. 

This post from Todd Klindt explains above stsadm command really well. 

See also http://blogs.c5insight.com/Home/tabid/40/entryid/181/How-to-Remove-a-User-from-a-SharePoint-2010-Site-Collection.aspx on how to remove a user from a SharePoint 2010 site collection.
 
Here is the basic steps from above post:
  1. As a site collection administrator, click Site Actions –> Site Permissions
  2. Click into any existing group (like site Owners).  The URL will be something like http://server/_layouts/people.aspx?MembershipGroupID=28.
  3. Change the 28 to a 0.  The list should now show you All People. 
  4. Find the user, click the checkbox by their name.  Click Actions, Delete Users from Site Collection.
  5. Now add the user back to the appropriate group.
The following powershell commands may be handy too:

Set-SPUser -Identity ‘Domain\username’ -DisplayName ‘Last, First’ –Web http://SharePointSe rver*
This forces a manual sync of properties from AD

Set-SPUser -Identity ‘Domain\username’ –Web http://SharePointServer –SyncFromAD*

To force Sync of all users,
Get-SPUser –Web http://SharePointServer | Set-SPUser –SyncFromAD*
 
 

Thursday, January 10, 2013

Sharepoint Fault Handler in vs 2008

Please see  Sharepoint Fault Handler in vs 2008

Also below is a copy.

Fault Handler
To get more detailed information about this error, it is necessary to add a Fault Activity (equivalent of a catch block) and to log it.
Select the workflow in the (Visual Studio) Workflow Designer, click on the lower left side of the Designer and click on the Fault Handler:
image
Another view of the Workflow Designer will show up:
image
Drag and drop a FaultHandler activity from the Workflow Foundation toolbox into  fautlHandlersActivity1 :
image
In the property page of this last activity select the FaultType property by browsing the mscrolib assembly:
image
Select System.Exception:
image
Now we will log the StackTrace into the workflow history log: drag and drop a LogHistoryList activity into the handler (if you don’t find this activity drag and drop the microsoft.Sharepoint.WorkflowAction.dll assembly to a new Visual Studio toolbox tab) :
image
Select the logToHistoryListActivity1 and set its HistoryOutcome property to the stack trace value of faultHandlerActivity1:
image
image
Rebuild the solution , redeploy (install.bat) and test the workflow.
The trace will show up in the workflow status :
image