Software

Ask something
Discussion Locked

Corrupted Mailbox, Exchange 2000

0 helpful
8 replies

by doanqa

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
What is the best way to troubleshoot a mailbox that can't be opened? I have a user that could not open her mialbox in outlook, "unable to open default folders". This is not the local client because I tried it on another computer with the same result. It also times out in OWA. Are there any utilties or regedits or articles or something that I can look to and try to recover this persons email?

8 replies

by doanqa

This has to do with the information store not being able to pull up the mailbox. It is not the pst.

by tony.colgrove

Use AD Users and Computers on a system that has the ESM (Exchange System Manager) installed. Make sure you are showing the Advanced Options in the MMC. On the Exchange Advanced tab, click on Mailbox rights. Make sure either SELF or the mailboxes owner is present and has READ and MAILBOX OWNER permission checked. Add these or remove them and add them back to see if the user is given access.
As a troubleshooting technique, add another user in as Mailbox Owner and try to open the mailbox withthat users credentials.

by maxwell edison

According to Microsoft article Q244523 titled, "XCLN: Unable to Open Your Default E-Mail Folders"

This problem can occur if named pipes (ncacn_np) is used as the Microsoft Exchange Client remote procedure call (RPC) protocol.

To resolve this problem, use one of the following methods:

Remove the static mapping for either the Exchange Server directory service or information store service, as applicable.

Statically map the ports for either the Exchange Server directory service or information store service, as applicable, to a port that is not in use. Microsoft recommends that you map to a port outside the ephemeral range (the ephemeral port range is from port 1024 to port 5000, including port 1024 and port 5000).

Run the net use command to the IPC$ share on the Exchange Server computer and use the credentials of the user whose mailbox you want to access.

(continued...)

by maxwell edison

.
.
RPC that uses named pipes (ncacn_np) establishes its security identity by using the credentials of the user who is logged on to the Windows NT domain. Because named pipe connections are established by the redirector to the server, the securityidentity is established before RPC communication. As a result, RPC uses the security context that is established by the redirector, and the dialog boxes generated by Microsoft Outlook that request security credentials do not override this security context. Because the user who is logged on does not have permissions for the target mailbox, the logon process to that mailbox does not work.

You can specify the ncacn_np protocol sequence by modifying the RPC_Binding_Order registry value. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q163576 XGEN: Changing the RPC Binding Order
Occasionally the named pipes protocol sequence is used because other protocol sequences did not work.

Other protocol sequences in the RPC_Binding_Order value may not work if either the Exchange Server directory service or information store service is configured to use a static IP address that is in use at the time that the service starts.This prevents the service from binding to that port, which essentially disables that protocol for use with that service. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q194952 XADM: Statically Mapped Port Limitations for Exchange Server

Q155831 XADM: Setting TCP/IP Ports for Exchange and Outlook Client Connections Through a Firewall

Q148732 XADM: Setting TCP/IP Port Numbers for Internet Firewalls

Q176466 XGEN: TCP Ports and Microsoft Exchange: In-depth Discussion

Regards,

Maxwell

This discussion is closed to new replies.