Monthly Archives: March 2004

You are browsing the site archives by month.

SBS 2k3 Knowledge base articles

828053 – ISA Server prevents connection to a remote desktop when you connect through Remote Web Workplace on a Windows Small Business Server 2003-based computer:

838304 – How to publish http://Companyweb to the Internet by using ISA Server 2000 on a server that is running Windows Small Business Server 2003, Premium Edition:

 Services may stop abruptly when you shut down or restart a Windows Small
Business Server 2003-based computer;EN-US;839262

Don’t be too cheap – call PSS when you get stuck.

Ray, the SBS guru posted this to the newsgroup… but I’d highly recommend that you pay attention to his note at the bottom about calling PSS.  Don’t ever be TOO cheap.  Yes, calling PSS is a US$245 call, but it is worth every penny.  The support folks live and breathe SBS and know this box better than anything else.  Don’t ever be afraid to reach out for help for your server. 

296788 Offline Backup and Restoration Procedures for Exchange

I recommend you to make a copy of the old MDBDATA folders. In case 
something goes wrong, you still have an untouch copy.

If the article seems complicated, in a nut shell, here is what you need to 

1. Make a backup of the old MDBDATA folder
2. Stop the Microsoft Exchange Information Store service
3. Delete the files in the mdbdata folder (which contains the new clean 
4. Put back the priv1.edb, priv1.stm, pub1.edb, and pub1.stm
5. Start the Microsoft Exchange Information Store service
6. Open Exchange system Manager, go all the way to the Mailbox Store and 
Public folder store. Right-click each one, database tab. Check the box 
"this database can be overwritten by a restore".
7. Right-click and Mount Store.

If the database is in clean shutdwown state, and you rebuild the server 
with the same server and domain name, the store will mount. Of course, 
there are always other problems that may show up. If you run into the 
problem, post back the errors from the application/system log and see the 
next step.

8. Assuming no problem, then close and reopen the Exchange system manager. 
Expand mailbox store, right click Mailbox, and run Clean up agent. 
Mailboxes on your right should be RedX. Right click each one and Reconnect 
to connect back to a user account. If you don't see the user on the list, 
it means the user already has a clean mailbox. You then need to go to AD 
Users and Computer, right click that user, Exchange Tasks and Delete 
mailbox. Back to Exchange System Manager, run Cleanup agent again, and 
reconnect the mailbox back to the user.

To save time, you should consider calling PSS at 1-800-936-4900 and let us 
to walk you through the steps. 

XP sp2 – download and test it out!

To aid IT professionals in planning and testing for the deployment of Windows XP SP2, Microsoft is making available this preview, based on Release Candidate 1 (RC1) of the SP2. Additionally, we have established 11 newsgroups for sharing information.

Exchange utilities

 Aaron out in the public newsgroups posted this nice recap of Exchange utilities: 

Thanks Aaron!!

SCANPST.EXE: This utility is used to SCAN Personal Message Stores (.PST) and
Offline Message Stores (.OST). It checks message headers and file structure
and attempts to correct any corruptions. Further reading: PSS ID Number:

REQMAIN: This is actually an MSMAIL utility. It is used by an MS Mail server
during directory replication. It can be useful to an Exchange administrator
when replication needs to be forced because it can also be manually run.
REQMAIN -t will cause a Post Office to TRANSMIT updates.

MTACHECK: Used to scan the MTA queue for corrupt messages. These message
could be clogging the MTA. MTACHECK rebuilds the queue to get things running
again and places corrupted messages in files for later viewing. The MTA must
be stopped to run this utility. Further Reading: PSS ID Number: Q163326

ESEUTIL: The "Extensible Storage Engine (ESE)" Utility. ESE is the name for
the new database engine in Exchange 5.5. This tool is used on the IS and
Directory to defragment, repai, and check integrity. It does this based on
the database low-level table structure, not the data content. It is not
intended for regular maintenance, it is for troubleshooting only and in
consultation with Microsoft. It is considered a tool of last resort. The
particular service corresponding to the database being checked should be
stopped (DS or IS). Complete syntax can be found in the Exchange Resource

EDBUTIL: The "Exchange Database Utility (EDB). This is the primary Off-line
routine maintenance utility for both the IS and the DS. The respective
services must be stopped. It has the ability to Defragment, do a Consistency
Check, and do some database recovery.

ISINTEG: The Information Store Integrity utility. Also an off-line utility,
it can be used to repair the IS database. It is not intended for routine
maintenance. Rather it should only be used upon the advice of Microsoft. It
is used to test and repair errors in the Information Store. It has several
notable uses that have reported appeared on exams:
  a.. ISINTEG -PATCH: Used after performing an off-line file-based backup of
Exchange databases. Each object within Exchange is identified by a Globally
Unique Identifier (GUID). The GUID is partially based on time. If you roll
back a server, it is theoretically possible to duplicate GUID values for
other objects that have since been created in the Organization. Therefore,
the GUIDs must be patched during the backup process. This happens
automatically through API calls when Exchange is backed-up ONLINE. When it
backed-up OFFLINE, you must use this command to patch the GUIDs.
  b.. ISINTEG -FIX: Provides high-level database recovery, fixing structural
problems with, for instance, the schema. Often used in the event of a sudden
shut-down resulting in corruption to the IS causing it not to start upon
reboot. Not a routine recovery tool though, restore from backup and playback
of logs is preferred.

Event 8331 – Titanium error – we have a hotfix! [Thanks Damian!]

 A new hotfix is available that may affect a number of SBS 2003

The symptoms described below on an SBS 2003 Server running on a system with
2 or more logical processors (this will include CPU’s with hyperthreading
support) are covered by this hotfix.


You may receive several (1 per minute) Event Id 8331 for MsExchangeAL in the
event viewer.

Event Type:             Error
Event Source:         MSExchangeAL
Event Category:       Address List Synchronization
Event ID: 8331
Date:                       11/20/2003
Time:                       5:06:16 PM
User:                        N/A
Computer:                CONTOSO

The service threw an unexpected exception which was caught at

Note that the source file and line number may differ

Another symptom is that AD updates from Exchange are not working, new users
do not get stamped with Exchange attributes. You may see the symptoms and
have no new events.

If you have seen those symptoms, are seeing it or even if you have an SBS
2003 system that has 2 or more logical processors and you are running
Exchange, you can contact PSS and ask for the hotfix found on KB article
837444. The call for a hotfix is a no-charge call. In order to find the
local PSS number for your country, go to, the
US number is (800) 936-4900.

The actual KB article is still in works and should be ready soon, but the
hotfix is live right now.

This fix will be included in Exchange 2003 Service Pack 1.



-- Damian N. Leibaschoff, MS IST, MCSE Microsoft Corporation


If you are having issues with saving files on your SBS2003 check this:

If you can’t save any files into your folders check two items:

First, ensure your permissions are set right:

Next ensure that disk quotas aren’t causing issues – review this KB for information on Disk quotas and adjust them or turn them off if needed

326212 – HOW TO: Manage Disk Capacity and Usage Using Disk Quotas in Windows Server 2003:;en-us;326212

Are faxes not opening right on your SBS 2003?

If your faxes are not opening right, it’s probably because Quicktime was loaded up. Try uninstalling Quicktime or the following steps:

1. Save a .TIF file on the Desktop.
2. Right click on the .TIF file, move to Open With, and then select Choose Program.
3. Select Windows Picture and Fax Viewer from the list. 
NOTE: Place a check mark from Always use the selected program to open this kind of file. 
4. Click OK to open the photo image with Windows Picture and Fax Viewer. 
5. Close this window, and then test if this problem is solved.

Take a look at these:

319196 OFFXP: Cannot Preview Scanned TIFF File in Windows Picture and Fax Viewer
329270 You Cannot View TIFF Images Using Windows Picture and Fax Viewer

An option put forth by Kevin W. in the newsgroups is to load alternative TIF viewer programs:

Check out:  or

Gavin reports that alternatiff has lots more options for viewing and he’s considering loading this up on all his installs.


Port Reporter tool – for tracking tcp/ip port usage data

Download Port Reporter a logging service for Windows that logs TCP/IP port usage data.

ExchDump tool – gathers Exchange configuration info

ExchDump is a command line utility that gathers Exchange configuration information from various sources used in troubleshooting support issues.

Wanting more training on Sharepoint?

Download details: SharePoint™ Developers’ Conference 2003: