SharePoint 2010 and PowerShell to count all list items in a Web Application


This problem manifested itself for a variety of reasons, but mainly, our vast Site and its subsites (over 400) have been growing very close to our List View Threshold (LVT), which has already been increased to 10,000.  Normally this wouldn’t be a huge problem, but the custom application we have sitting on top of SP 2010 does not handle lists over the LVT very well, as many of our operations perform tasks on “All List Items” – which as you know is disabled when you pass the LVT.   I have found that you can bypass this in code, however I am not a developer and the C#.NET project is over 600 files, which would be a huge undertaking  for someone like myself.  So, we needed to be able to identify and act upon any list in our web application that would be accessed by our code.  Without a development resource, I figured I’d…

View original post 734 more words

Hardware requirements for all SharePoint 2013 components summarized


Update 2013-01-28 – New note added : Certain Installation Scenarios not supported

Listed below are all of the Hardware requirements that have been announced for SharePoint 2013 and it’s connected services and products.
Covered in the list are, in this order:

 SharePoint_logo_small SharePoint Forundation 2013
 SharePoint_logo_small SharePoint Server 2013
 Office_logo_small Office Web Applications 2013
 Project_logo_small Project Server 2013
 SQL_logo_small SQL Server 2012 Reporting Services in Integrated mode
 SQL_logo_small SQL Server 2012 PowerPivot
 SQL_logo_small SQL Server 2012 Analysis Services Server
 blksthl_B_small Reference links

Note: In addition to the listed HW requirements below, note that certain Microsoft SharePoint Server 2013 installation scenarios are not supported
Not supported are: Dynamic Memory, ReFS(Resilient File system), Install on a DC, Install in a Workgroup, Install on Windows Web Server.

see Microsoft KB:

SharePoint Foundation 2013                Deployment type and scale               …

View original post 1,105 more words

Log Parser Rocks! More than 50 Examples!


Log Parser is a tool that has been around for quite some time (almost six years, in fact). I can’t really do any better than the description on the official download page, so here it is: “Log parser is a powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows operating system such as the Event Log, the Registry, the file system, and Active Directory”.

Log Parser is a command line (yes, command line!) tool that uses a SQL dialect to extract information from data sources. In particular, I have found it to be invaluable for extracting information from the web server logs of the sites that I manage and develop.

First, about that SQL syntax Log Parser uses to query the data sources… many developers seem to have a…

View original post 2,993 more words

Class not registered exception – SharePoint 2013

Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

The console application is running under 32 bit processor. Just change it to 64 bit.
To do this:

  • Right click on Console Application
  • Select Properties
  • Under Build Tab, change Platform Target to x64
  • Rerun the application and hopefully the error should go away now !

Solution: Accessing SharePoint Site or WebApp via Code Returns Null

SharePoint 2013

net stop “SharePoint Server Search”

net start “SharePoint Server Search”

net stop “SharePoint Administration”

net start “SharePoint Administration”

net stop “SharePoint Timer”

net start “SharePoint Timer”