Outlook 2007 crashes after upgrade to ZCO 6.0.6

[centrex]

6.0.5 was working OK (no crashes) but that version had issues with BB Desktop Manager.

Upgraded to 6.0.6 and now Outlook crashes when closed. This happens on all of the systems where ZCO 6.0.6 was installed. They are all running Windows 7, 64 bit.

Outlook crash shows this data:

Problem signature:
Problem Event Name: APPCRASH
Application Name: OUTLOOK.EXE
Application Version: 12.0.6514.5000
Application Timestamp: 4a89dc70
Fault Module Name: StackHash_809e
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdb3b
Exception Code: c0000374
Exception Offset: 000cdcbb
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 809e
Additional Information 2: 809e6d200701d884ba80371735158695
Additional Information 3: 99f3
Additional Information 4: 99f30eb69662c1c5f9f95c02de32288c

[k3rmit]

Same situation here. Windows Vista 64 bit, Outlook 2007 SP2, latest OS & Office patches installed.

[fsiegel]

If you have a crash file (in %TMP%\zco-cores), please post it. Thanks

[CinnyB]

Same problem here. Win7 x64, Office 2k7 SP2. Looking to move away from Exch 2k7 and testing all features. I've searched my entire local disk and \zco-cores anywhere. Please assist.

[k3rmit]

Originally Posted by fsiegel

If you have a crash file (in %TMP%\zco-cores), please post it. Thanks

attached dmp files.

[fsiegel]

k3rmit's log looks different -- the first crash looks like a crash on logon, not close. And it's hard to see where the crash is -- looks like it's trying to open a profile, but everything looks ok. Have you tried creating a new profile? The second crash 17 seconds later is in Office code.

As for the crashes on close, if there is no zco-cores directory (%TMP\zco-cores), perhaps a ZCO log file might help.

[k3rmit]

thanks for the feedback. actually the crash on open did happen a couple of times lately, mostly related to outlook profile switching blocked by Vista's search indexer.
i thought that the zco-cores contained info also about the closure crashes, but it seems like that's not the case.
i'm still getting a crash EVERY time i close office.
since i have an open support ticket for another issue with the latest connector, i will provide the logs in that discussion.

thanks again.

[k3rmit]

btw, i can confirm that it happens also on 32bits Vista/7.
i had several reports from users in these regards.

i didn't have the chance to log the crashes yet. as soon as i have meaningful logs, i will send them to you.

[GCamp]

Originally Posted by fsiegel

k3rmit's log looks different -- the first crash looks like a crash on logon, not close. And it's hard to see where the crash is -- looks like it's trying to open a profile, but everything looks ok. Have you tried creating a new profile? The second crash 17 seconds later is in Office code.

As for the crashes on close, if there is no zco-cores directory (%TMP\zco-cores), perhaps a ZCO log file might help.

I am having the same type of problem. I am running v6.0.6 with Windows 7 and Office 2007 on a 64 bit Dell platform.

What I get is one of two scenarios 1. When I exit Outlook, Outlook starts back up again. I am assuming that it is restarting as a result of a crash; or 2. The Gui portion is no longer visable but Task Manager shows that it is still running. (We had this same kind of problem when Outlook 2007 first came out)

I looked in %TMP%\zco-cores for the log that you say should have been generated but there is nothing that starts with a "z".

Has there been any further developments since the last posting?

There are features that v6.0.6 has that we want to utilize but cannot because of this problem.

[fsiegel]

Bug 46728. Just fixed for 6.0.7 which should be coming out soon. Most likely, it's comment #14 that affects you. You could tell by seeing if it doesn't happen if you don't create a new mail. If you just went into Outlook and exited, etc., it might not happen. Or if you just did a sync without getting a new window up.

There was also another crash that has been around since 6.0.0. These are generally not seen by the users, especially on XP. Vista is a lot less forgiving.

Basically for both these issues, we were freeing (or trying) things twice.