BCM account history view in discussion mode fails

[John7]

Hi

For test I created 1 account with 4 business contacts and had
BCM auto-link their emails.
The emails show up in the account history pane.
I can categorizes the view by all criteria except by Discussion.
This fails for unknown reasons.
Error msg "Restart Outlook or if the error remains to reinstall Outlook".
Windows XP pro, Office 2003 and BCM are installed from fresh.
I provided technical details below (BCM log file).

Any suggestions ?

TIA,
John7


System state:
------------
Office 2003 fresh install 4 wks ago
BCM last week.
Windows & Office fully updated
BCM SP1
BCM SP2 and SP3 ##NOT## installed, not available for my language.


BCM trace log part (BCMlLog_V2.txt)
--------------------------------------------------
Text between *** ... *** is a translation, hope it comes close.
[V] [19:18:08.2968750]Iris.Mapi.MessageStore:
IMAPITable::GetCollapseState:Enter: 0x01f7a6a0
[E] [19:18:08.2968750]Iris.Mapi.MessageStore:
*** Cannot obtain the collapse state of an instance key of a row without
header.***
[E] [19:18:08.2968750]Iris.Mapi.MessageStore: at
Microsoft.BusinessSolutions.eCRM.Mapi.MessageStore.MapiTableImpl.GetCollapseState(Guid
instanceKey, Int32 collapseStateVersion)
at
Microsoft.BusinessSolutions.eCRM.Mapi.MessageStore.MapiTable.GetCollapseState(Byte[]
InstanceKey)
[V] [19:18:08.2968750]Iris.Mapi.MessageStore: MAPIException:
hresult=0xffffffff80000003, message:
[V] [19:18:08.2968750]Iris.Mapi.MessageStore:
*** Cannot obtain the collapse state of an instance key of a row without
header. ***
[V] [19:18:08.2968750]Iris.Mapi.MessageStore: at
Microsoft.BusinessSolutions.eCRM.Mapi.MessageStore.MapiTableImpl.GetCollapseState(Guid
instanceKey, Int32 collapseStateVersion)

 

[John7]

John7

 

[Luther]

Definately looks like a bug in BCM, but perhaps just in your locale.
Not that that should make you feel any better...

This bit "Cannot obtain the collapse state of an instance key of a row
without header" may indicate that the name of a type got replaced by
blank in your locale. You should definately forward this to Microsoft.
I don't think there's much the people on this newsgroup can do to help
you out, but Microsoft can probably fix something like this in the next
SP. And since SP3 is not out for your locale yet, they may even be able
to fix before they release that.