Tags: | Categories: SharePoint, Windows, SharePoint development Posted on 2/26/2014 9:33 PM | Comments (0)
We used a very useful tool to make our SharePoint environment responsive after application pool recycles or web server restarts (iisreset) for years which is available under the GPLv2 license on CodePlex. It is called SPWakeUp which is a quite fast and simple tool to breathe new life into your server before you add that back to "production". Issues with the original solution As our environment grew, the wake up of the SharePoint sites took so long, for instance waking up a SharePoint environment with a ~0.5TB database took about a half hour which in our case meant high risk because as a general practise we remove the server from the load balancer for the maintenance period and we only add that back after the wake up. The second problem with the application was that it is full of memory leaks which in this case is not a serious issue because when the application stops the memory will be freed, but not too nice anyway. Improvements As per our original goal, we wanted to speed up the wake up process (reduce the time required for the run), also we wanted to reduce the memory usage by eliminating memory leaks. To achieve these goals a large part of the application has been modified/rewritten, but we tried to keep the most of the original source code and processing logic as possible. It means that for instance we tried to keep the wake up order of the sub sites within each site collection although changing the order would meant less code. Multi threaded application The "verbose" mode has been extended with multi threading capabilities. The application will open each site on its own thread. Because the application utilize the thread pool object, it will not consume the resources of the server, but it will run faster after the collection of the sites on the portal. How it works The followed process is very easy: Reads the farm configuration (Web application list) Navigates through the site collections and sub sites Based on the site list, it can parallely send http or http requests to the portal. Downloadable content As the original version of the software is distributed under GPLv2, this software must follow that license as well. SPWeakUp.zip (35.79 kb) Compilled code.zip (16.33 kb)  
Tags: , , , , , | Categories: SharePoint, SQL Server Posted on 5/28/2006 11:22 PM | Comments (1)
Microsoft SQL Server 2000 (2005) is capable to provide full text indexing and search services for most document types by default. All of the Microsoft Office document formats belong to the supported/searchable document types, like Word and Excel. Some other text like filters are also supported like simple txt files and html files. This feature can also be extended by installing additional indexing filters which is used by Windows Indexing Service originally. These kind of filters are usually written by third parties, like Adobe who created one for PDF indexing. Windows SharePoint Service 2.0 relies on the SQL Server's full-text indexing capability, so that functionality can also be extended by installing new filters on the SQL Server (additional configuration is required on the WSS). The issue we found regarding the MHT (Web archive) files is quite interesting, because the SQL Server/WSS doesn't really index those files although those are simply text files so the indexing should work without installing additional filters. Solution Applying some registry modifications can solve our problem: After navigating to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\Filters\Extension key, we need to create a new key called ".mht" and assign a value to it: {5645C8C2-E277-11CF-8FDA-00AA00A14F93}. The modification requires to rebuild and repopulate the full-text indexes on the SQL Server.
Tags: , , , , , | Categories: SharePoint Posted on 4/14/2006 1:53 AM | Comments (1)
I ran into this problem when the company where I was working used Novell Netware network. When the users were switching Explorer View in any document libraries they received a very simple error message about the WebDAV client. After searching through the internet without any success we dug deep into the problem ourselves and we found that the WebDAV client is simply not registered on the client computers (Windows XP). So the following two registry keys' values must contain the word "WebClient" to be able to use WebDAV:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder\[ProviderOrder] HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\NetworkProvider\Order\[ProviderOrder] After this registry modification you must reboot your computer.
Tags: , , | Categories: SharePoint Posted on 5/26/2005 2:20 AM | Comments (0)
If you would like to avoid wander through the menus of the Central administraton site of SharePoint you can do the followings: Windows SharePoint Service (WSS) version is available on the Control PanelControl Panel → Add or Remove Programs → Microsoft Windows SharePoint Services → Click here for support information → Version SharePoint Portal Server (SPS) version is also available on the Control PanelControl Panel → Add or Remove Programs → Microsoft Office SharePoint Portal Server → Click here for support information → Version Virtual Server version number on Central AdministrationSharePoint Portal Server Central Administration → Windows SharePoint Services → Configure Virtual Server Settings → <version_of_portal’s_VS> Schema versionThe information is stored on the SystemVersion table in the <portal>_SITE database.  SQL Server Enterprise Manager → <SQLInstance> → Databases → <portal>_SITE → Tables right click on the SystemVersion table → Open Table → Return all rows