[Today's post comes to us courtesy of Rod White]

Customers are currently seeing issues where SBS 2008 servers receives faxes successfully, but intermittently faxes routed to email may fail. You may also notice that the Fax Server Services crashes (fxssvc) due to a CDO call. If you look within Fax and Scan Console the Incoming queue folder may show that faxes are in a retry or failed state.

In normal troubleshooting you would enable protocol logging for the "Windows SBS Fax SharePoint Receive Connector" within Exchange Management Console and wait for the failure to occur.  However, this time logging shows nothing.   The reason for this is that the faxes are failing before the connection to Exchange 2007 so nothing is logged.

At the time of the Errors the fax server will continue to route to Folders, Printers, and SharePoint. Faxes are also routed to the Archive folder on the server. Note that customers are not losing faxes, just the notification through email fails.

Log Name: Application
Source: Microsoft Fax
Event ID: 32083
Task Category: Inbound
Level: Error
Description:
Unable to route fax C:\ProgramData\Microsoft\Windows NT\MSFax\Queue\1C9BEB28C4E2F.tif to the requested e-mail address.
The following error occurred: 0x80040211
This error code indicates the cause of the error.
Check the SMTP server configuration, and correct any anomalies.

0x80040211 translates to CDO_E_SMTP_SEND_FAILED

Log Name: Application
Source: Microsoft Fax
Event ID: 32089
Task Category: Inbound
Level: Error
Description:
The Fax Service failed to execute a specific routing method. The service will retry to route the fax according to the retries configuration. If the retries fail, verify routing method configuration.
Job ID: 0x0401c9beb28c4e2f.
Received on Device: 'Courier V.Everything EXT PnP (V90-x2)'
Received file name: 'C:\ProgramData\Microsoft\Windows NT\MSFax\Queue\1C9BEB28C4E2F.tif'.
Routing extension name: 'Microsoft Routing Extension'
Routing method name: 'Route through e-mail'

Log Name: Application
Source: Microsoft Fax
Event ID: 32078
Task Category: Inbound
Level: Error
Description:
A successfully received fax was not routed automatically. You can find the fax in the Inbox/Incoming archive folder by its Job ID. Job ID: 0x0401c9be065c1fd1. Received on Device: 'Courier V.Everything EXT PnP (V90-x2)'

Resolution (Update 8/10/09)

You can now install an update for your SBS 2008 server to correct the issue described in this post. At this time, the knowledge base article is still being written but you can request the fix directly from here:

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=973640&kbln=en-us

Make sure to click "Show hotfixes for all platforms and languages" to download the x64 version.  It is normal that the product shows Windows Vista and not Windows 2008 or SBS 2008.

As previously discussed, an easy way of determining if you have the issue that is corrected by this Hotfix is by restarting the Fax Service on the affecter server, if after doing so, email routing works for a while and then stops again, then this is most likely the same issue this fix is designed to address. On the other hand, if routing always fail, then the problem will most likely persists even after this fix requirement further troubleshooting to isolate the point of failure.

Update (4/11/2011)

This issue can also affect Windows 2008 R2 and SBS 2011 Standard.  The above link will take you to the hotfix for both versions.  For more information, see http://support.microsoft.com/default.aspx?scid=kb;EN-US;973640

Previous Resolution

We are currently tracking this issue, but are unable to provide a solution at this time. If you experience the symptoms in this article, please contact Microsoft Support at 1.800.936.4900.  As always, if the issue is determined to be a bug, there is no charge for the support incident.  To verify that you have the issue we are currently investigating, try restarting the Fax service.  If email routing starts working (for awhile, not a permanent fix) you probably have the issue under investigation.

[Today's post comes to us courtesy of Kim Oehmichen]

We have recently seen a few cases where creating a new user with the Add a New User Account wizard from the SBS Console does not create the respective Exchange 2007 mailbox. 

The wizard finished with the following warnings:

In these cases the AddUser.log (C:\Program Files\Windows Small Business Server\Logs) indicated that the default Mailbox Database was not found:

[8120] 090515.192332.7283: Messaging: MessagingTaskException: Unable to find default mailbox database with name [Mailbox Database] - Check access and verify if mailbox database exists - Error# (80004)

[8120] 090515.192332.7595: AdminTME: Status: TaskId = MessagingTasks.TaskCreateMailbox, RootTaskId = TaskCreateUser, Success: True, Warning: True, Continue: True, Message: Unable to find default mailbox database. Make sure mailbox database exists and you have access to view the database.

This issue will occur when the First Storage Group database name is changed from the default as seen below:

Resolution

1. Open the Exchange Management Console
2. Expand Server Configuration and select Mailbox
3. Open the Mailbox Database Properties of the First Storage Group in the Database Management tab
4. On the General tab, ensure that the name of the database is Mailbox Database
   
5. Apply the change and click OK

Now the Add a New User Account wizard from the SBS Console will successfully create an Exchange mailbox for the user when run.  Note: You will need to manually create a mailbox for any users that were created without mailboxes, while the wizard was in the broken state.

[Today's post comes to us courtesy of Rod White]

When an Administrator attempts to create or delete a user within the SBS 2008 Console they may get an error and a  "View Warning Details" link. Reviewing the details show two warnings:

• Administrator <Admin name> does not have Exchange administrator rights.
• Mailbox does not exist for recipient of welcome mail.

When removing a user account the wizard will hang with the error below:

You will also get the following errors in the C:\Program Files\Windows Small Business Server\Logs\Adduser.log file:

Messaging: MessagingTaskException: Insufficient privledge, not a member of an Exchange administrator group - Error# (80010)

AdminTME: Status: Tasked = MessagingTasks.TaskCreateMailbox, RootTaskId = TaskCreateUser, Success: True, Warning: True, Continue: True, Message: Administrator Robert Brown does not have Exchange administrator rights.

Resolution

1. Open AD Users & Computers > double click the <Admin User name> you are logged on as
2. Select the Member Of tab
   
3. Verify the Primary Group attribute. If the Primary Group is set to Domain Admins then you'll need to change it Domain Users.
   
4. Within the Member of list box, highlight the Domain Users group and click the Set Primary Group button.

You should now be able to run the wizards without error.

[Today's post comes to us courtesy of Justin Crosby]

Windows 2008 SP2 and Vista SP2 has been released.  Windows 2008 SP2 should be installed on SBS 2008.  You can download the X64 version of SP2 here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=656c9d4a-55ec-4972-a0d7-b1a6fedf51a7 or use Windows Update.  As with any update, you should be sure to take a good backup prior to installing.  SP2 will require a reboot so plan accordingly. For more information on Windows 2008/Vista SP2 please see: http://technet.microsoft.com/en-us/windowsserver/dd727510.aspx.

Repair steps for Exchange 2007 on SBS 2008 have been posted to the SBS TechCenter.  These steps cover reinstalling the Client Access, Hub Transport, and Mailbox Server roles for Exchange 2007.  You can view the documents here: http://technet.microsoft.com/en-us/library/dd728006.aspx.  Please note that removing and reinstalling Exchange roles on SBS 2008 should not be a common troubleshooting step.  These documents should only be used when other troubleshooting resources have been exhausted.  Make sure to take a full backup of the server before performing any of the steps.

[Today's post comes to us courtesy of Wayne McIntyre and Justin Crosby]

Note: This article has you make changes to Active Directory.  Before doing so be sure to make a complete backup.

After a mail migration to a new domain/Exchange organization using Exmerge, you will lose the ability to reply to old email and modify old calendar items. The reason this occurs is because the message is stored with x500 address from the old domain. In order to correct this you need to add this old X500 address as proxy address for the user account in Active Directory in the new domain.

You will need to build the user's new X500 proxyAddress from the the user's LegacyDN attribute from the old domain.  To get this attribute, launch ADSIEDIT.msc on the old domain controller and open the properties of the user account.  Locate the legacyExchangeDN value and copy it to notepad.

Next you must prefix "X500:" (without quotes) to the value in notepad.

Example:

Old/Source legacyExchangeDN = /o=TAILSPINTOYS/ou=first administrative group/cn=Recipients/cn=test2

New proxyAddresses = X500:/o=TAILSPINTOYS/ou=first administrative group/cn=Recipients/cn=test2

Note: In our example TailspinToys is the Exchange Org and Test2 is the user's alias. 

On the new domain controller edit the proxyAddresses attribute of the migrated user and add your modified X500 value to the proxyAddresses attribute.  Do Not delete the SMTP: address.  Do Not modify the legacyExchangeDN value on the new domain.

Modifying the value in bulk

If you have a lot of users and want to do this in bulk you can use the tool ADModify.net, which you can download from http://www.codeplex.com/admodify.

1. Launch ADModify and select Modify Attributes.

2. Select your domain in the Domain List and your domain controller in the Domain Controller list and hit the green arrow button.

3. Traverse thru your domain tree until you locate the OU which contains the migrated users and select Add to List.

4. Highlight the users from that OU that you wish to modify then click Next.

5. On the Custom tab, check the boxes for "Make a customized attribute modification" and “Multivalued Append”.  Enter the values as follows then click Go!.

Note: You must modify the values accordingly, with the legacyExchangeDN you retrieved from the source domain.  Do not copy and paste the values from this blog post.

Attribute Name: proxyAddresses

Attribute Value: X500:/o=YourOrgHere/ou=first administrative group/cn=Recipients/cn=%’mailNickname’%

Note: In some cases your mailnickname may have changed, if this is the case you will not be able to do the bulk edit and will have to manually add the x500 address for those users.