One of the Windows SBS 2003 servers I administer had a BSOD and after bringing it back up the Exchange store wouldn't mount. It gave the error "The database files in this store are inconsistent."
I used the Eseutil.exe utility to check the consistency of the store.
"c:\Program Files\Exchsrvr\bin\eseutil.exe" /mh "c:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
From the output I noticed 2 things. The state was set to dirty shutdown and one of the logs was missing or corrupt.
State: Dirty Shutdown
Log Required: 16655-16655 (0x410f-0x410f)
I tried running Eseutil.exe /r but received an error. I then proceeded to run Eseutil.exe /p which repairs the database. Once that was complete I ran an offline defrag, Eseutil.exe /d, and lastly isinteg.exe -s servernsmr-fix -test alltests which checks for integrity weaknesses.
I was then able to mount the store and users were able to access their mailboxes. A word of caution Eseutil.exe /p is usually a last resort and can cause some data loss. Microsoft recommends restoring from a clean backup rather then doing a repair. I'll leave that decision up to you.
If your printer in Windows Server keeps going offline even if its status says 'Ready' and you know its online try disabling SNMP on the Server.
Right click the printer and choose Properties. Under the Ports tab click Configure Port... and uncheck SNMP Status Enabled.
I couldn't print to a network printer shared through Server 2003 SBS. I tried restarting the Print Spooler on the Server but that ended up freezing the Printers and Faxes window. I tried clearing out the print queue by emptying the following folder:
You will have to stop the Print Spooler to delete the files
To fix this I deleted the TCP/IP port in the registry:
Look for the corresponding IP address. Always backup the registry before modifying anything.