No new items as of late, I have not been able to dedicate any of my time to SharePoint but have been spending most of my efforts on SystemAdmin and Manager Tasks.
But wanted to post that I do follow #SharePoint and #SPHelp hash tags on twitter. You should too….
Info Archive
SharePoint Twitter Hash Tags
Posted January 7, 2014 By Kevin BennettUsers listed in People Picker
Posted November 26, 2012 By Kevin BennettHere are some quick notes I ran into when working with our People Picker, or list of all users on Sharepoint 2010.
To see all users of the site: http://SiteAddress/_catalogs/users/simple.aspx
But you cant delete multiple, can only delete each, so go to:
http://SiteAddress/_layouts/people.aspx?MembershipGroupId=0
This will let you delete mutiple users at a time .. huge time saver.
but our people picker was still finding users from the old domain, So i found this: http://technet.microsoft.com/en-us/library/gg602075(d=lightweight,v=office.14).aspx
And set the PeoplePicker to only search our current domain for users. with command:
stsadm -o setsiteuseraccountdirectorypath -path “DC=,DC=local” -url https://SiteCollectionURL
Be the first to comment
The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT:0x80131040)
Posted July 24, 2012 By Kevin BennettReal quick before I forget:
Got the following error day on our Development Sharepoint 2010 server when I attempted to delete a Web Application.
“The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT:0x80131040)”
Did an IISRESET on the application server and was able to delete
I believe this was because I was making changes to the web application and maybe it wasnt in sync with the DB?
ULViewer – You are my bitch
Posted May 31, 2012 By Kevin BennettLet me just say, if you are not using ULViewer or don’t have it in your toolkit .. you should.
What it does: You know that cryptic error message you get in sharepoint .. come on, you know ..the Correlation ID: alksdlkjf-234l3245-0sllksdf-234234. Yeah that awesome error that tells you exactly what is wrong (not)! Well the ULViewer will shed some light on what is happening on your site when that error is generated.
So jump over to your Web Front End server and fire up ULViewer. Select File, Open, ULS Logs. Now Bring up the browser and reproduce that error. Jump back to ULViewer and press pause. Scroll up and look for the event code. You see it … now read the details.
I have found that 4 out of 5 times (that’s the tv version of math, not the scientific) that it will actually tell you what is wrong, either a missing file, missing feature .. etc.
Now use it .. and use it often.