Category Archives: 202

Hot Fixes for Outlook 2007 Now Available

For those using Outlook2007, two new hotfixes are now available that address specific speed and performance issues as well as a variety of other issues. Hotfixes, by nature, come with some warnings on their use.  Hot fix 961752 and Hot fix 967688

Note #1: If you have never requested a hot fix from Microsoft, or it has been years since you have, you will be pleased to find that the process is quite fast and efficient. No longer do you need to even call Microsoft to request a hot fix!

Simply click on the links above to open up a new window with information on the hot fix. In the upper left of the window will be a clickable link” ‘View and request hotfix downloads’. Click on the link, enter your email address twice plus a security code and within five minutes you will receive an email containing a link to download the hotfix and a required password. The password is only good for a certain number of days (7 days maximum), so it is best that you download the hotfix as soon as you receive the email from Microsoft.

DCOM 10016 Event Error

After installing SBS 2008, you may begin to see DCOM 10016 event errors being reported in your SBS Monitoring reports as soon as users begin to use Sharepoint/Companyweb. This error is also identified if you run the SBS 2008 Best Practices Analyzer. There have been several posts on how to fix this error, but the instruction always were vague in one specific step.

First, here is the DCOM error as reported in the event log and within the SBS Monitoring report:

Event Source: DCOM  Event Id: 10016
Event Details: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

And here is the error as reported in the SBS BPA report:
Local activation permission to the IIS WAMREG Admin Service required

To fix this issue, perform the following steps:

* From the SBS console, click Administrative Tools > Component Services
(or, if you prefer: click Run > comexp.msc)
* Expand down Component ServicesComputersMy ComputerDCOM Config
* Right click on IIS WAMREG Admin Service, then click Properties
Click on the Security tab
* Click the Edit… button within the Launch and Activation Permissions section
* Click Add and add the user named: ‘Network Service
(NB: this is the step that confuses people. Most instructions simply tell you to add the appropriate user, but do not make it clear which user to add!)
* Click on the checkbox to Allow (enable) the Local Activation rights option for this user
* Click OK twice, and close Component Services
* Finally reboot the server for good measure and to ensure the change takes effect

Hope this helps!

SBS 2008 and Sharepoint Log file

If using SBS 2008, one of the things you want to do is to install and run the SBS 2008 Best Practices Analyzer (BPA) on a regular basis. At my first SBS 2008 installation, BPA recenlty reported that my Sharepoint log file was larger than 1gb in size. Strange, I thought, since this customer had not even started using sharepoint. Beyond that, BPA did not offer any suggestions for resolving this issue.

So, here are the instructions (from the SBS BPA team) on what to do:

Step 1: start up command prompt in administrator mode. You do this by clicking on Start, then right clicking on Command Prompt, then clicking ‘run as Administrator’

Step 2: From the command prompt:
1. Type: sqlcmd –E –S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query and press Enter
2. From the 1> prompt, type: select name from sys.databases and press Enter
3. From the 2> prompt, type: go and press Enter
This will display a list of all databases know to SQL server. One of them will look something like this:

Step 3: Now, with the actual name of the Sharepoint database, you will want to enter the following commands, replacing dbname with the actual name of the Sharepoint database. Be sure to leave the brackets [ ], parens ( ), and _log, as noted:

2> Go
1> Use [dbname]
2> Go
1> DBCC SHRINKFILE([dbname_log],2)
2> Go
1> Exit

For example, if your Sharepoint database was named SharePoint_Config_12345, then you would type in:

1> BACKUP LOG [SharePoint_Config_12345] WITH TRUNCATE_ONLY
2> Go
1> Use [SharePoint_Config_12345]
2> Go
1> DBCC SHRINKFILE([SharePoint_Config_12345_log],2)
2> Go
1> Exit

Hope this helps!

SBS2008 and Sharepoint

I’ve listened to three live web training sessions on SBS2008 recently. On all three sessions, they had Microsoft Partners share their “real world” customer experiences with the early betas of SBS2008. I was interested (perhaps surprised?) to hear all three Microsoft Partners rank Sharepoint 3.0 as being one of the major hot topics for their customers.

One of the partners emphasized that we should NOT view Sharepoint as an optional extra, just as most of us do not view Exchange as an option to SBs, but an integral part.

If your only experience with Sharepoint ahs been with version 1.x/2.x, perhaps it’s time to take a look at Sharepoint 3.0!  Did you know it now supports Blogs and Wikis? Or take a Demo tour of Sharepoint 3.0!


SBS and the 3GB switch

For several years, there has been an on going discussion on whether or not to enable the /3GB switch in the boot.ini file for an SBS server. By and far, the consensus of opinion has been to NOT use the /3GB option – especially considering that WSS 2.0 or later versions do not support the /3GB switch.




And, finally, this KB article includes a lot of additional information on the /3GB issue (with thanks to SG for the reminder!):


Publishing multiple web or sharepoint sites in SBS

Here are some links to frequently asked questions about hosting multiple websites or sharepoint sites on an SBS server, and hosting multiple mail domains (with thanks toi the M&M ladies, Sean and Vlad)

How to publish websites with ISA 2004:

Hosting a website on your SBS 2000 & 2003:

Publishing multiple sharepoint web sites:

Hosting multiple domains on an SBS Server:
Part 1:
Part 2:
Part 3:

Sharepoint and Full Text Indexing and Searching

With SBS2003 Standard, Sharepoint uses WMSDE. But if you have SBS2003 Premium, and have installed SQL you should consider upgrading your Sharepoint site to SQL. Besides better performance as you add more users, you also gain the ability to enable full text indexing and searching!

Instructions for upgrading Sharepoint to SQL and enabling fulltext search can be found in KB article 837367:

How to Reinstall Sharepoint

I have not had to do this myself, but as I routinely see questions about removing and reinstalling Sharepoint , I thought posting instructions provided by Microsoft CSS may be helpful to someone down the road!

Generally speaking, if you want to completely reinstall companyweb on SBS 2003 SP1, you need to follow the article KB829114 below, but it might ask you to insert the SBS SP1 CD3, so you need to extract SBS SP1 installation folders, and then point the SBS Integrated setup program to the folder for the ‘SP1 CD3’ contents.

The extraction process is listed below, please do follow the exact steps or the extracted files will be removed:
1. Start a cmd prompt and change directory to the SP1 download folder (or the SBS03_SP1 folder on PKG_CD2).
2. Then type “<path>\SBS2003-KB885918-SP1-X86-ENU.EXE /x” (with no quotation marks) and press Enter.
3. Specifying a path for the extracted files (such as C:\SBSSP1)
4. Run the SBS Integrated setup, and when the setup program prompts for the CD3, point it to the folder created above.

829114 How to remove and how to install the Windows Small Business Server 2003

As I know, we are able to keep the original SharePoint database and connect it to the new installation. If the original database is not corrupted, you may manually backup the files and then reconnect the database after reinstalling the components:

829113 How to restore a Windows SharePoint Services CompanyWeb database after

827701 How to perform a disaster recovery operation of SharePoint Services

As I know, on SBS 2003 we have a document which can make a full backup and restore for the whole system. It might be useful to you, I suggest you have a look at it:

Backup and restore SBS 2003:

Best regards,
Charles Yang (MSFT)
Microsoft CSS Online Newsgroup Support

Index PDF documents within Sharepoint

Chad Gross, once again, is the Sharepoint man of the day for coming up with this method for indexing and searching through PDF documents within Sharepoint:

To get full text search capability on SBS, the best method is to follow the instructions on the SBS Premium Technologies CD.  Now, to get full-text search of PDFs (including content) will require a few extra steps:

1) Install the PDF iFilter from Adobe on your SBS:

2) Verify the Indexing service is started & set to start automatically.

3) Add the PDF icon to your docicon.xml file so your Document Libraries  show the correct icons for your PDFs:

Another thing to realize is that not all PDFs are created equal, and some require additional handling in order to be able to search their contents.  Basically, if you create a PDF locally from a Windows application (Word, Excel, QuickBooks, etc.) using Adobe’s Acrobat Distiller or PDFWriter, then the PDF will include text that the iFilter will detect when the PDF is uploaded to your Sharepoint site. 

As a result, you’ll be able to search the contents of these files from Sharepoint.  However, if you’re scanning documents to a PDF format – then what you have is an image dumped into a PDF.  As a result, these scanned documents are not able to have their contents searched without extra handling. 

So what’s the extra handling?  If you’re scanning documents, you’ll want to make sure you run your scans through an OCR application and then create a dual-layer PDF (image + OCR text).  Then when you upload this dual-layer PDF to your Sharepoint site, the iFilter detects the OCR text allowing you to search the contents.

For low to medium volume jobs, I would recommend ScanSoft’s OmniPage Pro – it works with most scanners and is one of the most accurate OCR engines I’ve used.  It also allows for workflow creation to help automate the scan / ocr / save process, and natively supports creating dual-layer PDFs.  If you’re looking at medium to large volumes of scanning, I would recommend 
taking a look at leasing a new copier / printer / scanner / fax unit. Gestetner has several newer units that include the ability to scan to a PDF + OCR right at the unit.