Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 415
  • Last Modified:

User can send but not receive thru Outlook, cannot OWA after ESEUTIL /P

Hi all!  
My environment:
SBS2003 SP2, Exchange 2003 SP2, all XP Clients with Office 2003 (Outlook 2003).

Symptoms:
1 user out of 12 can connect to Exchange from Outlook and view live data in Public Folders, but cannot receive email or get to OWA.  Outlook and OWA are functioning properly for all other users (at least that is the current report).

History:
Yesterday morning, the server was locked, had to hard boot it.  Server came back up, but Pub and Priv would not mount.  Tried ESEUTIL /R, but error said database was shutdown in dirty state.  Perform ESEUTIL /P on both, then ESEUTIL /D on both, then ISINTEG on both until no more fixes were shown.

Possible solutions:
The only course I can think of would be to export from Outlook to PST, then delete Exchange mailbox (leaving the SBS domain Account intact), create a new Exchange mailbox, link SBS Domain acount to the new Exchange mailbox, then import PST data.

Questions:
Are there any troubleshooting steps I can/should perform before moving forward with this plan?  Is there a better way to handle this?  If this is the best way, how would I go about this?  I am not even sure it is possible in SBS because the integration between domain and Exchange is so tight.  Any advice or guidance would be much appreciated.

Thanks in advance!!
0
rjccaz
Asked:
rjccaz
1 Solution
 
shauncroucherCommented:
If I were you I would do the following:

1) Test with one user if creating a new mailbox resolves the sending issue.
2) If it does, then use Exmerge to EXPORT all mailbox data to PST's.
3) Remove their mailboxes / cleanup agent on Exchange
4) Create new mailboxes / use Exmerge to IMPORT data from PST to new mailbox

Shaun

http://www.microsoft.com/downloads/details.aspx?familyid=429163ec-dcdf-47dc-96da-1c12d67327d5&displaylang=en

http://support.microsoft.com/kb/823143
0
 
rjccazAuthor Commented:
Shaun,
THanks for the quick reply.  I was under the gun and continued to search and found basically what you said to do, but using Outlook to export the PST instead of EXMERGE.  Here is what I found:

1. From Outlook export the mailbox to a .pst file. At the Choose folder dialog be sure to choose the top Mailbox folder and check off Include all Subfolders. I recommend opening the .pst file and comparing the original folder contents with the .pst folders to insure everything backed up before proceeding. If you have errors creating the .pst try changing the encryption method to no encryption.

2. From Active Directory Computers & Users, right click on the user account and choose Exchange tasks. Choose Delete Mailbox. (default SBS container - yourdomain\MyBusiness\Users\SBSUsers)

3. From Exchange System Manager, in the left pane, right click on the mailbox container and choose Run Cleanup Agent. Then in the right pane, right click on the users mailbox ( it will now have an X next to it ) and choose Purge. (default SBS container - Servers\yourservername\FirstStorageGroup\MailboxStore\Mailboxes)

4. From Active Directory Computers & Users, right click on the user account and choose Exchange tasks. Choose Create Mailbox.

5. From Outlook import the mailbox from the .pst file you created in the first step

Anyway, it seems to have worked and while the user lost about 1.5 days of email, she is fully functional now.  Plus the rest of the Exchange data seems to be intact.  The lesson learned here: Be prepared for any amount of data loss when using ESEUTIL /P.

Thanks again!
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now