Monthly Archives: May 2009

Exchange Server

Outlook Web Access: There was an unknown error accessing the directory

Leave a comment

While troubleshooting message delivery between two email systems, I received this error from Outlook Web Access:

—————————
Message from webpage
—————————
There was an unknown error accessing the directory.  If the problem continues, contact technical support for your organization.

I was trying to send a message to contact in my Exchange organization representing a user on the other messaging system. This particular contact was hidden from the address list so I was manually typing the address. I was sending to the targetAddress, or External E-Mail Address, of the contact, not the local address.

A quick web search did not reveal an answer. The only KB from Microsoft regarding the error, http://support.microsoft.com/kb/945917, was not the solution in my case.

First I had a look at the email addresses of the contact. It had only one; userx@sub.domain.com. (domain.com is a shared domain between the two messaging systems.) The address was both in the proxyAddresses and targetAddress attributes. Since sub.domain.com is a sub-domain of the shared SMTP domain I figured I would try adding an address from domain.com. That is when the solution presented itself, because Exchange Management Console (EMC) displayed this error:

——————————————————–
Microsoft Exchange Error
——————————————————–
The following error(s) occurred while saving changes:

set-mailcontact
Failed
Error:
The proxy address “SMTP:userx@sub.domain.com” is already being used by “domain.com/Users/userx”. Please choose another proxy address.

Turns out that there was already a mail enabled user in the directory using the address. That meant that when OWA tried to resolve the address the directory returned two matches. That is one too many. After I resolved this conflict the error disappeared from OWA.

Windows

Want to see the contents of the system partition on Windows 7?

1 Comment

On Windows 7 the system partition, the partition the computer boots from (I know, I know, the names are messed up.), is hidden from the user. It isn’t really hidden, it just isn’t mounted to a drive letter or directory. Windows really doesn’t need drive letters or mount points. It is just as happy to use the volume GUID (see a previous post about Volume GUIDs here). It is just for our benefit that the various volumes on a computer has drive letters. It is a very good idea to not mount the system volume, that keeps users from messing with the boot critical files required for computer startup. It also makes it easy to enable BitLocker since the small unencrypted volume that loads the BitLocker driver is already in place. So in shot, good work Microsoft. But what if you’re a geek and really want to see what is on that volume? Fear not, it is quite easy.

The first thing we need to do is find the GUID of the system volume. The easiest way I know to do that is to run mountvol.exe. On a Windows 7 machine you will se one volume that has no mount points. That is probably your system volume. Just copy the GUID from the command prompt window and past it into the Run box. Windows will open a new explorer window with the contents of the system volume displayed, just like any other volume on the system. If you do not like the Run box, you can just type start.exe <Volume GUID> directly from the command prompt.

Here is the output from mountvol.exe on a test system:

Possible values for VolumeName along with current mount points are:

\?Volume{540a0153-2083-11de-9315-806e6f6e6963}
*** NO MOUNT POINTS ***

\?Volume{540a0155-2083-11de-9315-806e6f6e6963}
D:

\?Volume{540a0156-2083-11de-9315-806e6f6e6963}
E:

\?Volume{540a0157-2083-11de-9315-806e6f6e6963}
F:

\?Volume{540a0154-2083-11de-9315-806e6f6e6963}
C:

To open the system volume I just run this from the same command line:

start.exe \?Volume{540a0153-2083-11de-9315-806e6f6e6963}

And here is the result with the complete contents of the system volume:

systemvolume_windows7_thumb_635BF9B8

But please remember to be careful when you poke around in here. Chances are your computer will not start if you do.