Import ULS log files to SQL Server database for Sharepoint 2010

Sometime you may need to import ULS log files to SQL server . It can be done with several ways by using SQL Server import tools or import from an Excel file to SQL  server. Or you can use fallowing free open source windows application tool. With this tool it can be done with more quickly . By multy-threading and bulk insert architecture feature provides you that ULS logs contains total 1.500.000 row  can be upload in  apprx. 2 minutes. (as you know it depends on your configuration and hardware)

Than you can query SQL tables as you wish : Fallowing query will return execution time over 1 sec for SPMonitoring event records.

select * from WFE1
where [ExecutionTime] > 1000 and [Eventid] =’b4ly’
order by [ExecutionTime] desc

“All These source codes are freeware and is provided on an “as is” basis without warranties of any kind, whether express or implied, including without limitation warranties that the code is free of defect, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the code is with the end user

For Download  ULStoSQLImporter v1.0  for Sharepoint 2010:


CabMaker v1.0 (Command Line Tool)

If you have ever need explore or change a file content inside of wsp file,  you already know that changing extention and rename it as “Cab” file , you can open or extract contained files by using well know compress programs like zip or rar openers. But what if after you change some file for example after fixing an element.xml file , if you  need to make again a wsp , this very simple tool can help make cab(or wsp) files.

Usage: cabmaker <source folder> <cab file name>
Examples :
cabmaker c:\mySolution c:\mysolution.wsp
cabmaker c:\mySolution c:\

For 64 bit systems:
For 32 bit systems:




Sharepoint Tools – WssDownload v1.0 (Command Line Tool)

Hi Everyone,

WssDownload  tool has been relasead. You can use this tool for download all documents in a Document Library as preventing folder structure to your server harddrive.
If you wonder why have i developed this tool , consider a scenario that publishing feature is been corrupted or not activated and windows explorer view not running and you have hundreds of files in your library, how could you download them manuelly ? so i think it is clear that you can use it .

For Download.

WssDownload x86 can be used 32 bit Sharepoint 2007 systems.
WssDownload x64 can be used both Moss2007 x64 and Sharepoint 2010 systems.

* This is a command tool that using sharepoint object model and should be run in sharepoint installed server

WssDownload <site url> <library name> <download path>

WssDownload Presentations c:\\downloads


Good Tools for Fixing Missing Features on Sharepoint

Some scenarios removing a feature unproperly or after migration your sharepoint to upper version  or in a development envoriment adding removing solutions with multiple times cause  getting several kind of feature errors like “Failed to find the XML file at location ’12\Template\Features\{feature name}\feature.xml’

Here is a very good article about this problem and solution.

 You may need belowed tools for fixing that problem. (Some tools are using  just stsadm at background but giving you a visual form experience.)

Wss Remove Feature From Tool
In some situation the STSADM command STSADM.EXE -o deactivatefeature is not able to deactivate a feature either on site collection or on site level.
This can (e.g.) happen if the feature definition for the feature that has to be removed is not installed in the farm.
This tool allows to remove the feature from the site or site collection completly.
WssRemoveFeatureFromSite -scope (site|sitecollection) -url <url-to-site> -featureid <featureid> -force

Wss Analyze Features  Tool
This tool allows to verify if the feature definition files for all installed features are present on the file system. Also allows to verify if the features used in site collections an sites are installed on the server.
In addition it can create a checklist file which can be used to verify if a server has all features installed required to act as destination for a content deployment job of an existing sitecollection.
WssAnalyzeFeatures -url http://server:port
This command will verify all features on the server and in the site collection.
It will create two files:
– ProblemFeatures.txt outlining all identified problems.
– ContentDeploymentFeatures.txt this is the created checklistfile. It will contain all features that have to exist on the target to be able to act as target for a content deployment of the site collection.
WssAnalyzeFeatuers -verify ContentDeploymentFeatures.txt
this command will verify the features installed on the server against the features listed in the ContentDeploymentFeatures.txt checklistfile which was created on the source server.

SharePoint Feature Administration and Clean Up Tool
Find faulty FeatureDefinitions and cleanly uninstall them.
Find Feature remainders in Sites, SiteCollections, WebApps and in the Farm, from e.g. forcefully uninstalled Features from farm without deactivating them before, causing errors.
Also, de-/activate Features Farm wide.

Faulty Feature Tool v2