Exchange 2007 suddenly stops receiving external emails
Exchange 2007 or SBS 2008 suddenly stops receiving external emails.
Internal and outgoing emails are working fine. Emails are not bouncing back. Exchange Management Console seems to be OK. Exchange stores mounted and all Exchange services running.
This behaviour could be caused by a low space on one of the hard drives. Disk doesn't have to be completely full, just getting close to this.
Check Application logs for following events:
Event ID: 15004
Level: Warning
Source: MSExchangeTransport
Resource pressure increased from Medium to High.
Resource utilization of the following resources exceed the normal level:
.....
Event ID: 15006
Level: Error
Source: MSExchangeTransport
The Microsoft Exchange Transport service is rejecting message submissions because the available disk space has dropped below the configured threshold.
Resource utilization of the following resources exceed the normal level:
...
Simply free up some space on the hard drive in question and email delivery will resume. On Small Business Server 2008 the first suspect would be WSUS database.
Windows Small Business Server 2008
Exchange 2007
Schedule Automatic Computer Restart
To avoid restarting server during working hours you easily schedule restart to be performed at night. Obviously the same can be applied to a workstation rather than server.
Create a text file restart.txt with text:
shutdown /r /c "Your message displayed before restart"
If you want to shut down instead of restart, use this text instead:
shutdown /s /c "Your message displayed before shut down"
Rename the file to restart.bat
a. For Windows Server 2003 and Windows XP
Start > Programs > Accessories > System Tools > Scheduled Tasks
Add a new Scheduled task
In Task Tab > Browse > select your restart.bat file
In Schedule Tab > Schedule Task > select Once and set the restart date and time
b. For Windows Server 2008 and Windows 7
Start > All Programs > Accessories > System Tools > Task Scheduler > Task Scheduler Library
Create Basic Task
Name: Restart
Trigger: One Time, select Date and Time
Action: Start a program - select your restart.bat file
Finish
When restart is initiated and message is displayed you have 30 seconds to cancel the restart:
Start > Run >cmd
shutdown -a
Windows Server 2003
Windows Server 2008
Windows XP
Windows 7
Windows Event ID 10016 (DCOM)
This article uses a particular Windows Event ID 10016 error caused by Windows SharePoint Services 3.0 on SBS Server 2008 as an example, but can be used to troubleshoot other 10016 (DCOM) errors.
Event ID: 10016
Level: Error
Description:
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.
1. Find name of the offending COM application:
Start > Run > regedit
Expand HKEY_CLASSES_ROOT\CLSID\{61738644-F196-11D0-9953-00C04FD919C1} or just search for the ID (61738644-F196-11D0-9953-00C04FD919C1) in regedit (F3)
Make a note of the "Default" value - IIS WAMREG admin Service
2. Fix the permission problem:
Start > Run > dcomcnfg
Component Services > Computers > My Computer > DCOM Config
IIS WAMREG admin Service > Properties
Double check that Application ID matches CLSID in the 10016 error
Security Tab > Launch and Activation Permissions > Edit > Add
Add the account mentioned in 10016 error (NETWORK SERVICE) and grant the equired permissions (Local Launch and Local Activation).
Windows Small Business Server (SBS) 2008
Manually truncate MS SQL 2005 log file (.LDF)
If MS SQL database Recover Model is set to "FULL" and regular full backups are not performed databases log files (.LDF) can grow very large.
If you are working with a production database make sure you know what you are doing as you may loose ability to restore your database to any point in time since your last backup. If production database backups and storage management are set up properly you should never need to truncate logs manually.
To manually truncate log file on test/development SharePoint_Config database:
1. Open SQL Server Management Studio and run following SQL query:
USE SharePoint_Config
BACKUP LOG SharePoint_Config WITH TRUNCATE_ONLY
This will truncate log file but won't reduce actual file size.
2. To shrink actual file run:
USE SharePoint_Config
DBCC SHRINKFILE (N'SharePoint_Config_log', 50)
50 - Log file target size in MB.
OR
SQL Server Management Studio > Databases > SharePoint_Config > Tasks > Shrink > Files
3. To prevent future growth of the log file run:
USE SharePoint_Config
ALTER DATABASE SharePoint_Config SET RECOVERY SIMPLE
OR
SQL Server Management Studio > Databases > SharePoint_Config > Properties > Options > Recovery Model > Simple
Microsoft SQL Server 2005
- Troubleshooting SQL 2005 SP4 and other Windows Update installation errors
- ntbackup logs missing
- List all files on the server
- Outlook 2010 exchange proxy settings automatically changes to incorrect details
- Export private key and certificate from IIS .pfx file
- Restore Exchange 2007 mailbox to a test lab server (ntbackup)
- Useful Exchange 2007 and 2010 Management Shell commands
- Message Size Limits in Exchange 2007
- Disconnect or block user
- Send Email from a .bat script