Hello,

we do encounter some problems downloading the OAB from an Exchange 2007 SP1
CAS using Outlook 2007 SP2 on domain member computers.

The problem can be reproduced on different systems and is as follows:

The "first" user who logs on to the computer does not encounter any problems
using Outlook 2007 in Cache mode and does not have any problems downloading
the OAB.

The "second" user cannot download the OAB and a sync error 0X80004005 occurs.

While checking the event log first, Outlook does generate two Event ID 27
entries for starting and successfully downloading the OAB for the "first"
user.

When the "second" user logs on and starts Outlook only one Event ID 27 is
being written, which states "An error has occurred"

After monitoring the Outlook startup sequence using Process Monitor, I did
find out that the "second" does not have a
"HKCU\Software\Microsoft\Exchange\Exchange Provider" key. Outlook does check
the following two keys during startup:
HKCU\Software\Microsoft\Exchange\Exchange Provider
HKLM\Software\Microsoft\Exchange\Exchange Provider

When Outlook tried to open the users oab files, the error was pretty
obvious. The system is a Windows XP SP3 German. Outlook tried to open the
file:
C:\Dokumente und Einstellungen\USER2\local settings\application
data\microsoft\outlook\browse.oab

This resulted in a PATH NOT FOUND error, as "local settings\application
data" is not a valid path on the local system.

The correct path, as being used by Outlook when the first user is logged on
is:
C:\Dokumente und Einstellungen\USER1\Lokale
Einstellungen\Anwendungsdaten\Microsoft\Outlook\ub rowse.oab

The local system variable %APPDATA% is being resolved correctly to the
localized application path.

The interesting questions a
Where does the file path come from, when Outlook tries to create the OAB
files?
And why does Outlook not create the requested HKCU reg keys, when they are
not available?

Does anyone know those secrets?

Best regards,
Thomas

--
Thomas Stensitzki
MCITP, MCTS, MCSA, MCSA:Messaging