Microsoft Outlook Fails to Load in Sandbox

[dlguild]

MS Outlook 2003 will run only once in the sandbox after reconfiguring Sandboxie to force Outlook. After the first successful open, once Outlook is closed, when attempting to reopen I get 'Unable to open your default e-mail folder. The information store could not be opened.' After I reconfigured Sandboxie to remove the Outlook force, Outlook opens fine again. I can repeat this process with identical results each time.

The only difference between my installation and the majority of Outlook installations is that the MS Exchange server resides (in a different Domain) on my LAN. Therefore, I run Outlook in the Cached Exchange Mode. I have a feeling I need to open something else up in the .ini file to allow the 2-way synchronization to occur. Any insights will be most appreciated.

Thanks!

[tzuk]

First can you run your Outlook in normal mode, to make sure this is in fact the problem?

[dlguild]

Hi tzuk,

Outlook runs fine in the sandbox in normal mode. Tried numerous times, restarted, tried numerous times again. All OK. Problem exists only when running in the cached exchange mode.

[SnDPhoenix]

I remember someone else having a similar problem, only difference is that it was a different program (i think it was a browser), maybe i should find that thread.

*edit* i did a quick search and found this which might be of some help to you guys (also take note of what i have bolded. seems useful to this particular problem, especially being that this problem only happens after the first time the program is run.):

When an Outlook account is configured to use Cached Exchange Mode, Outlook works from a local copy of a user's Exchange mailbox stored in an Offline Folder file (OST file) on the user's computer, along with the Offline Address Book (OAB). The cached mailbox and OAB are updated periodically from the Exchange server.

When a user starts Outlook for the first time with Cached Exchange Mode configured, Outlook creates a local copy of the user's mailbox by creating an OST file (unless one already exists), synchronizing the OST with the user's mailbox on the Exchange server, and creating an OAB. (If a user is already configured for offline use with an OST and an OAB, Outlook can typically download just the new information from the server, not the whole mailbox and OAB.)

[tzuk]

Thanks, SnDPhoenix.

Alright, dlguild, we can run a trace, to see if these OST/OAB files are in a location that Sandboxie doesn't set in an OpenFilePath yet. Or if it's something else.

Or . . . maybe you could run your Outlook in normal mode?

[SnDPhoenix]

Hey just thought of something else too, when he runs Outlook in Cached Exchange Mode in Sandboxie for the first time, the ost/oab files are created right, and because a sandboxed app (in this case outlook 2003) is creating files they would end up in the sandbox which means that wouldnt he have to not openfilepath, but instead openpipepath? so i dont think he even needs to run a trace, all he has to do is explore sandbox, and just look and find where the ost/oab files are created and then just OpenPipePath to that folder. right?

[dlguild]

Thanks, Tzuk & SnDPhoenix.

I have followed up on both your suggestions. SnDPhoenix, I have no ost or oab files in the sandbox explorer at all. The closest file name (not even an extension) that shows up at all is:

"C:\Documents and Settings\Dan\Application Data\Sandbox\DefaultBox\user\all\Application Data\Microsoft\Office\Data\opa11.dat"

Tzuk, I took the time to learn how do do a trace and installed the sysinternals viewer. Loading Outlook into Sandboxie produced 492 lines; too much for here. It did reveal that Kaspersky is trying to attach to Outlook. I suspect it is their spam scanner. It does this even when I disabled KIS protection (odd). Perhaps the spam filtering is causing the grief. I saved the output of DebugView to a text file, but thought it was a bit large to post. It you would find it useful, I will send it to you.

[SnDPhoenix]

Yeah, you can just email him the logfile and he'll investigate it. Btw alot of other ppl having problems and just happen to have KIS on their system find out that KIS is usally the Culpit, so im pretty sure it is kaspersky's spam filter causing the problem, it would make sense, although why does it work the first time without problems... oh well, the debug log should answer that.

[tzuk]

Yeah, you can just email him the logfile and he'll investigate it.

What the hell is this? Do you think I work for you?

[dlguild]

Hi Tzuk,

Not to worry, I won't send you anything without your OK. I have been analyzing the trace myself. Your onsite instructions are very good! With all 4 traces on I find only 1 entry (appears several times) which seems to be denied access (*D):

0.00000000 (001700) SBIE (KD) 00000003 \REGISTRY\MACHINE\System\CurrentControlSet\Control\SafeBoot\Option

Putting either of the following in the .ini file did not help:

OpenKeyPath=outlook.exe,HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot
OpenKeyPath=outlook.exe,HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot\Options

If you see some error I made here, let me know. Otherwise, I will run in the normal mode and periodically switch to cached exchange mode to sync my local database.

Thanks!

[tzuk]

These particular KD's lines are fine. All (or almost all) programs will show them. And it occurs very much near the start of the program. So it shouldn't have anything to do with the problem you're seeing.

But if you found an easy workaround solution for now, it's probably the best way to deal with it.

And thanks for registering!