OUTLOOK CLOSES PERIODICALLY AFTER INSTALLING CRM 3.0 CLIENT

[808STATE]

We have noticed that on several XP clients, after installing the 3.0
outlook client, when closing message or search windows in Outlook, the
entire Outlook application closes without warning. We have also
noticed that Outlook will sometimes hang indefinitely and need to be
forced down and reopened. Some of the client-side errors are as
follows:

Event Type: Error
Event Source: MSCRMAddin
Event Category: None
Event ID: 5972
Date: 3/1/2006
Time: 11:34:43 AM
User: N/A
Computer: <computername>
Description:
An error occurred retrieving data from the Microsoft CRM server for
processing Microsoft CRM-related e-mail messages. Not all CRM-related
e-mail messages may be marked appropriately. Verify that the current
user has appropriate permissions and server connectivity and try the
action again. HR=0x80040e4d. Context=. Function=CEmailTagger::Run.
Line=313.

___
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 2/28/2006
Time: 2:04:53 PM
User: N/A
Computer: <computername>
Description:
Hanging application OUTLOOK.EXE, version 11.0.8000.0, hang module
hungapp, version 0.0.0.0, hang address 0x00000000.

____
Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 3/1/2006
Time: 10:23:05 AM
User: N/A
Computer: <computername>
Description:
Faulting application outlook.exe, version 11.0.8000.0, stamp 43599e06,
faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4,
debug? 0, fault address 0x000111de.

____
Event Type: Error
Event Source: MSCRMAddressBook
Event Category: None
Event ID: 6408
Date: 2/27/2006
Time: 3:10:21 PM
User: N/A
Computer: <computername>
Description:
An error occurred in the Microsoft CRM Address Book. Restart Microsoft
Outlook and try again. HR=0x800c0006. Context=

XML document parsing error
lErrorCode 0x800c0006
lFilePos 0
lLine 0
lLinePos 0
bstrReason The system cannot locate the object specified.

bstrUrl
. Function=LogXmlError. Line=368.

Does anyone think these errors are related to the outlook-closing issue
we are experiencing?