This error is pretty repeatable, it happens 100% of the time on the machines that the Outlook hotfix was installed on. Here is the complete error output.

Event Type:    Error
Event Source:    Application Error
Event Category:    None
Event ID:    1000
Date:        4/13/2009
Time:        9:13:31 AM
User:        N/A
Computer:    DHILL-VM-XP
Description:
Faulting application dloclientu.exe, version 3.1.338.6101, faulting module unknown, version 0.0.0.0, fault address 0x52202920.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 64 6c 6f   ure  dlo
0018: 63 6c 69 65 6e 74 75 2e   clientu.
0020: 65 78 65 20 33 2e 31 2e   exe 3.1.
0028: 33 33 38 2e 36 31 30 31   338.6101
0030: 20 69 6e 20 75 6e 6b 6e    in unkn
0038: 6f 77 6e 20 30 2e 30 2e   own 0.0.
0040: 30 2e 30 20 61 74 20 6f   0.0 at o
0048: 66 66 73 65 74 20 35 32   ffset 52
0050: 32 30 32 39 32 30 0d 0a   202920..

In addition, I have posted the same problem on the MS Exchange blog, where the hotfix was released. Here is the URL.

http://msexchangeteam.com/archive/2009/03/24/45088...

http://seer.entsupport.symantec.com/docs/323991.htm

They write "products applied version 12,5". Version 12,0 is also applied.
"If you feel this issue has a direct business impact for you and your continued use of the product" Answer is YES, what they think?

Rgds, Jyrki

Ofcourse this affect business.
SP2 would definitely increase productivity compared to current sluggishness. This bug is preventing us from rolling it out.
I hope the Symantec guys are close to a fix.

I have to concur that this is definately an issue. We are rolling out the hotfix/SP2 in any case as the Outlook performance is the big winner here. I do hope that Symantec releases a hotfix for the DLO agent to address this very quickly.

I agree that this is a major concern. A speedy response to this issue would be of great value.

The Office Service Pack is a much anticipated update that organisations are eagre to reap the benefits from. A slow progress on resolving this issue and a lack of understanding of the need for a speedy response from Symantec's side would be a nusiance.

Regards,
DKarlen

Btw, I take contact to Enterprise support first time 27 mar, second time 2 apr.

I emailed them: "But anyway if you are interested to develop your product to work with upcoming Office 2007 SP2, I send more debugging information" (C:\Documents and Settings\%username%\Local Settings\Application Data\Symantec\DLO\.settings\DLOClient.log and \DLOClient.dmp*).

But because of we have OEM version of BE12, they don't give any support or response.

-Jyrki

Currently their are two workarounds to this issue.

Remove SP2 using the The Microsoft Service Pack Uninstall Tool for the 2007 Microsoft Office Suite (KB 954914).
Change in the Profile turning off incremental backups of Outlook PST files

I think it will be released soon..

Sounds pretty similar to an issue we were having yesterday after installing an update for Outlook (KB969907), if someone logged a job two months ago it's pretty bad that Symantec don't yet have a fix.

Ben

been waiting for the hotfix and hope it is out soon

After getting caught by KB969907. Can't believe this issuse has been going months.

 And so are we - the KB969907 update just started installing on some of our machines - we haven't gone to SP2 yet - were are also in the middle of rolling out the DLO so this is really bad timing for us...  And you cannot uninstall KB969907 so the hotfix for the DLO is a must.

The above Symantec article - seer.entsupport.symantec.com/docs/323991.htm - lists two workarounds:

1. Uninstall SP 2 \ Hotfix - this maybe an option, but some of the hotfixes (like KB969907) do not allow uninstallation.
2. Turn off "incremental backups of Outlook PST files" in the DLO profile.  I have done this on our network and tested it and it has resolved the issue of the DLO agent crashing.  I'd still like a hotfix so that we can enable this feature though... 

This workarround  works,  but the real hofix its not present...as Jackie L says

"I think it will be released soon.."

mvg, See the above post from Jyrki.  The hot fix is available - the url is the same as for the workaround - seer.entsupport.symantec.com/docs/323991.htm - when I first visited the page after the hotfix had been released I had to manually refresh the page....

For some reason When I install the hotfix, it says that the upgrade terminated unexpectedly and that I have to see the installation log for details. Where can I find the installation log?

Hi,

I have downloaded the hotfix for 32 bit Windows computers (not the servers version), but it won't install.

I've downloaded and installed the hotfix but the error still comes up. What is the resolution here? What am I missing?

my desktop version is DLO 338B61a
The server version is 12.0 Rev. 1364
DLO server version is 3.1 Rev. 3.38.61a

server installed updates
service pack 3
hot fixes:
317974
319698
317908
324963
323893 <- this is supposed to fix the issue
318576
329863
329505
329072
334733
336718

after reading the article, my file dates in my DLOAgent share are all wrong.
http://seer.entsupport.symantec.com/docs/323893.htm
I guess the install share hasn't been updated, all the file dates should say 6/16/2009, mine are all 1/9/2009
how do you update the install share? its not working no matter how I install this hotfix.