Archive for May, 2014

29
May
14

Remove-SPUser PowerShell Command: How to Use it in SharePoint 2013

I was trying to use the Remove-SPUser cmdlet and kept getting this error:

Remove-SPUser : You must specify a valid user object or user identity.

image

With claims based authentication the cmdlet Get-SPUser returns all users like this:

image

So, you can see the format of the –Identity (UserLogin) is something like this:

i:0#.w|DOMAIN\USERID

This thread referred to the Get-SPUser cmdlet and using New-SPClaimsPrincipal, but what I found was pretty simple.

http://social.msdn.microsoft.com/Forums/en-US/260ad45b-cfe7-4699-842b-fc2ecdf6e543/powershell-cant-getspuser-adfs-user?forum=sharepointgeneralprevious

Use this format for the cmdlet:

Remove-SPUser -identity "i:0#.w|cfgmgt\rwright" -web http://cmsp2013:5555

The trick for me was to put double quotes around the encoded user name.

Now, if the Microsoft documentation would be more accurate…

19
May
14

Create MS Access View Missing after Installing Hotfix KB2553170

Windows 7 SP1, Office 2010, accessing SharePoint 2013 on both Office 365 and on-premises.

You might find you have an issue when attempting to create an Access view from SharePoint 2013.  In this case I was getting an error when I clicked on Access View, "Export to database failed. To export a list, you must have a Microsoft SharePoint Foundation-compatible application."

image

I found an article where this error was being discussed.  There was a hotfix issued in December 2013 that addressed the issue.  However, after installing the hotfix, I found the Access View link on the create view page was missing.  This required performing an Office 2010 repair (from Programs and Features) by selecting Change on Office 2010.

image

After doing this and rebooting, the link was back…and it worked!  This is the 2nd time in the last week I’ve had to perform an Office 2010 repair.  I think it all started when I installed SharePoint Designer 2013 on this machine (it already has SPD2007 and SPD2010).

Hey Microsoft, stop breaking your software!

13
May
14

Opening Office Document Information Panel with Managed Metadata Causes Application to Crash

Every time I opened a Word document (or tried to create one) using a content type in SharePoint 2013 that had a managed metadata column and the document information panel was displayed, Word would crash.

This was happening on both my Windows 8.1 Lenovo Yoga that has Office 2010 and Office 2013 and My Windows 7 Dell D830 that has Office 2010.  Both of these machine had SharePoint Designer 2013 installed on them, in addition to SPD 2007 and SPD 2010.

I found this post from L.L that seemed to address my problem.  It appears that running an office repair fixes the issue.  Yay!

I guess the last one you repair (Office 2013 or Office 2010) is the one that gets registered as the default application.  Which is okay by me, because I am constantly annoyed by the ditching of skeuomorphism and replacement of flat design found within Office 2013.

Keywords:  Office 2010, Office 2013, SharePoint 2013, Managed metadata, Content types, Crash, MS Word 2010, MS Word 2013.




Asif Rehmani’s SharePoint Videos

SharePoint-Videos

Click to access a wealth of SharePoint videos

SharePoint Rx

SharePoint Rx Home

Categories

Posts by Date

May 2014
M T W T F S S
« Mar   Jun »
 1234
567891011
12131415161718
19202122232425
262728293031  
Support Wikipedia