StoragePoint Customer Evidence Video Released!

The marketing folks on the StoragePoint team recently released a very compelling StoragePoint customer evidence video.  The list of customer success stories with StoragePoint continues to grow.  There is little question that StoragePoint is the premier BLOB remoting solution for SharePoint.  Check out the video below.  For more information on StoragePoint visit  Stay tuned for information on the highly anticipated release of StoragePoint 3.0 with full support for SharePoint 2010.

Merge Content Databases After StoragePoint Externalization

It’s not uncommon to have multiple SharePoint content databases for a single SharePoint application.  The separation of site collections into different content databases is typically done in an attempt to work around content database size recommendations provided by Microsoft (see Microsoft’s Plan for Software Boundaries document for more information).  In many cases organizations have one content database per site collection.  After deploying StoragePoint into your existing SharePoint farm the next logical step is to run the externalize job(s) which will relocate your existing content outside of the content database.  Once completed you will be left with very small content databases that can now be merged (note that you will have to run the DBCC_ShrinkDB script several times to reclaim your unused database space or rebuild table indexes before running dbcc_shrinkDB.  For more information consult the StoragePoint Administrator’s Guide).  Merging SharePoint content databases can be done using the stsadm command. Execute the steps below to merge your content databases.



  1. **** Important!  Microsoft recommends applying the April Cumulative Update before you merge content databases.  There are known issues with this merge database command prior to this update.
  2. Even though your content databases will be very small after relocating BLOBs with StoragePoint’s externalize job, you must make sure you have enough free space to merge content databases.  The general rule is that you must have at least three times the size of source site collections database size.  *** Note:  Do not use the value returned for the StorageUsedMB property when running the stsadm -o enumsites -url webappurl to determine your database size.  With StoragePoint deployed this property will reflect the total space used by content in SharePoint but not the actual size of the content database. 
  3. In order to execute the following STSADM command you must be a member of the Farm Administrators group and be an Administrator on the local computer.  Additionally you need to have Full Control permission for any site collection being moved.  For SQL Server, you must be a member of the db_owner database role.

Steps to Merge Content Databases

  1. From a SharePoint server in your farm, open a command prompt and navigate to %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin
  2. Type the following STSTADM Command
    STSADM –o mergecontentdbs –url <url of web application> –sourcedatabasename <source db name> –destinationdatabasename <dest. db name> –operation2 Note that the URL is the URL of the web application that contains the site collection.  This is not the URL of the site collection itself.
    Operation2 = full database merge

  3. Restart IIS by running iisreset/noforce from a command prompt.

BlueThread Announces StoragePoint for SharePoint 2010

LAS VEGAS, Oct. 19 /PRNewswire/ — (at the Microsoft(®) SharePoint(®)
Conference); BlueThread Technologies(®), Inc. (BlueThread) announced
StoragePoint(®) for SharePoint 2010. Attendees at the conference can preview a
demonstration of the 2010 version at the BlueThread booth.  StoragePoint
enables organizations to realize at least a 95% reduction in the size of their
SharePoint content databases by relocating content BLOBs (Binary Large
Objects) out of the SQL database onto virtually any Cloud-based or on-premise
storage platform. It improves SharePoint manageability, scalability,
performance and security without any sacrifice to functionality or user


“We wanted to provide our clients with unprecedented SharePoint 2010 BLOB
storage flexibility,” says Rob D’Oria, BlueThread’s CTO and co-Founder. “With
StoragePoint 2010, you will be able to create policy-based storage profiles
which manage content BLOBs at a very granular level.  It also leverages both
SharePoint 2010 EBS and RBS provider interfaces. Clients can choose to use
them independently, side-by- side or leverage our out-of-the-box the EBS to
RBS migration capability.”

D’Oria continues, “Organizations don’t have to wait for 2010 in order to
realize the benefits of StoragePoint. WSS 3.0 and MOSS 2007 customers can
install StoragePoint within their existing SharePoint deployment while taking
comfort that a no-hassle upgrade to 2010 is already in place.”

Mark Wiley, Chesapeake Energy’s IT Supervisor for Document Management &
Collaboration said; “Our current StoragePoint deployment reduced our content
databases from 450 gigabytes to less than 20, a reduction of over 95%.  Not
only did it dramatically improve SharePoint manageability, it surprisingly
increased performance as well.  As an early adopter of Microsoft technologies,
we are looking forward to SharePoint 2010 and leveraging StoragePoint.”

“BlueThread is a great partner and StoragePoint is a perfect complement to our
SharePoint 2010 ECM solution,” said Ron Cameron; President and CEO of
Knowledgelake, a BlueThread partner. “StoragePoint enables our customers who
are scanning millions, or even ten-of-millions of documents with our software
to manage them simply and easily within SharePoint.”

Customers can download a 30 day, no-cost trial version at StoragePoint’s


About BlueThread Technologies, Inc.
A Microsoft Gold ISV, BlueThread Technologies(®), Inc. (
is an Ann Arbor, Michigan-based company that specializes in Enterprise Content
Management (ECM) and system performance solutions exclusively for the
Microsoft(®) SharePoint(®) platform. With decades of ECM and years of
SharePoint experience, we develop highly-scalable solutions and tools which
are deployed at some of the largest organizations around the globe

Fixing “Unable to connect publishing custom string handler for output caching”

I was troubleshooting another issue on a client’s production server and ran across the following errors in the event log (Application Log).  The error was occurring on a KnowledgeLake Viewer web service.  After some quick searching I found Namwar Rizvi’s post on how to fix the problem.  It appears that SharePoint output caching is trying to access the web service that is called by a web part which is causing the error to occur.

Event Type:        Error

Event Source:        Office SharePoint Server

Event Category:        Publishing Cache

Event ID:        5785

Date:                9/2/2009

Time:                9:29:56 AM

User:                N/A

Computer:        <WebFrontEnd>


Unable to connect publishing custom string handler for output caching.  IIS Instance Id is ‘50319175’, Url is ‘’.


For more information, see Help and Support Center at

SQL Server Management Studio “Unable to Cast COM of Type …”

Ugh! I am stuck in Windows Registry hell. Here is the situation. I have a Windows Server 2008 R2 Standard Edition install running SQL Server 2008 SP1 and Visual Studio.NET 2008 SP1. It seems that with this configuration I get the following error in SQL Server Management Studio (SSMS).

Unable to cast COM object of type ‘System.__ComObject’ to interface type ‘Microsoft.VisualStudio.OLE.Interop.IServiceProvider’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{6D5140C1-7436-11CE-8034-00AA006009FA}’ failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)

After doing some searching it appears that this is a result of Windows registry corruption that can be solved by re-registering the actxprxy.dll (you need to open the command line running as administrator and run ‘regsvr32 actxprxy.dll’).  There are serveral blog posts that document this solution (below are a few links).  Unfortunately for me this did not fix my problem and I haven’t been able to find a fix making SSMS unusable.  The irony of this situation is that I have a laptop with the exact same problem and it is running Windows 7 RC1 with SQL Server 2005 and Visual Studio.NET 2008 so the common demoninator appears to be VS.NET 2008.  I an anxious to see if others are having this problem if the above workaround was successful for them or not.


Enabling Outlook Instant Search on Windows Server 2008

I have recently switched my laptop over to Windows Server 2008 from Windows 7 to take advantage of hyper-v.  I wasn’t happy with Virtual PC 2007 for Windows 7 and VMWare is too expensive when I have access to Windows Server 2008.  Overall the experience is very good as Windows Server 2008 runs very quickly on my Lenovo t61 (I am not running the Desktop Experience feature as this sucks too many system resources).  Since I am running this machine as my core workstation I am running Office 2007. I ran into a scenario where I wanted to enable Outlook Instant Search.  Here is a link to a good blog post that walks you through the process of enabling Outlook Instant Search on Windows Server 2008.

Attempted to read or write protected memory – Event Id’s 6398, 6482, 7076

I have ran into this issue several times in the past where a SharePoint server’s event log is filling up with event id’s 6398, 6482, and 7076.  These errors typically popup in your event viewer for administrative timer jobs.  According to Microsoft there is an issue with multithreaded applications accessing IIS at the same time.  Microsoft does have a hot fix to address the issue.  The knowledgebase article is located here;EN-US;946517

Enabling Zip Files in SharePoint Multiple Document Upload

This pertains to Windows Vista and Windows 7 only.  If you are running Windows XP then stop reading.

If you are running Vista or Windows 7 and you are attempting use the “Upload Multiple Documents” feature of MOSS 2007 or WSS 3.0 to upload zip files you have probably noticed that zip files do not show in the upload explorer window.  The “Upload Multiple Documents” feature is an ActiveX control that installs with Office 2003/2007 so if you aren’t running either Office versions then the option won’t show up in SharePoint.  The problem with zip files and the ActiveX control has to do with how Vista deals with zip and CAB files. By default Vista is configured to show zip and CAB files as folders allowing the user to drill into their contents within Windows Explorer.  For this reason they do not show up in the ActiveX control that handles multiple file uploads for SharePoint.  To fix this problem you need to delete the following registry keys.  WARNING! Backup your registry before making any changes!


Now deleting the above registry keys is a bit more involved than running RegEdit, finding the keys, and deleting them.  Both keys above are protected keys and are own by the SYSTEM account.  In order to delete the keys you need to change ownership of the keys, delete sub keys first, and then delete the root key.  To do this you need to download the PSExec utility from Microsoft that is part of the Sysinternals tools.  The download is located here .  Once you have downloaded the tools and extracted the PSExec utility from the zip file, you need to then start a windows command prompt as the local machine administrator (if you are not logged in as the administrator then run the following from the RUN dialog:  runas :user/localhost\administrator CMD ).  Once the command window launches navigate to the directory where you unpacked the contents of the zip file that you downloaded earlier and execute the following command: psexec -i -d -s c:\windows\regedit.exe. At this point you are now running RegEdit as the SYSTEM account and will be able to change ownership of registry keys.  It is important to note that you have to delete child keys before deleting the root key.

Bookmark and Share

Configuring Live Writer for SubText

Microsoft Live Writer can be configured to use with SubText.  Here are the steps. 

1). Navigate to the Weblog > Add Weblog Account menu

2). Select Another weblog service 


3). Enter the URL of your weblog (

4). Enter a username and password.


5). Under the type of weblog select Metaweblog API and enter the Remote Posting Url in the following format: 


6). Click Next.  Enter a name for this blog setting and click Finish.



Bookmark and Share