BCM startup exception - Attempted to read or write protected memor

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hopefully someone at MS can direct everyone to a patch that fixes this. Had
BCM installed with integration to SBA on a developer machine with VS2003,
VS2005 and VSTO2003 and VSTO2005. Everything was working fantastic until
latest updates with .NET Framework 2.0 and installation of SQL2005 Developer
Edtion.

Now get a fata error at Outlook launch stating:

---------------------------
Business Contact Manager
---------------------------
Attempted to read or write protected memory. This is often an indication
that other memory is corrupt. Contact Business Contact Manager Support. You
can find contact information in the "Contact Us" topic in the Business
Contact Manager Help(Help Menu, Business Contact Manager Help).
---------------------------
OK
---------------------------

Only ways to make Outlook itself function is either to:

1) Uninstall Business Contact Manager completely (not acceptable)

2) Change the DWORD setting for the LoadBehavior setting from "3" to "2" in
the Windows Registry for the BCM AddIn for Outlook found in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\Microsoft.BusinessSolutions.eCRM.OutlookAddIn.Connect.1

While neither option 1 nor 2 above are acceptable (especially since I
develop addins for Outlook/Office and am targeting enhancing the BCM / SBA
functionality and interoperation), at least option 2 will allow Outlook to
continue functioning without uninstalling BCM entirely.

However, the LoadBehavior = 2 setting instructs Outlook to not load the BCM
addin, and therefore BCM does not function within Outlook. Any attempt to
access BCM data or functionality causes the LoadBehavior to be reset to 3
(i.e. Load at startup) and the fatal crash and error message appears again
the next time Outlook is launched.

Can anyone from Microsoft, or for that matter any other developers or
participants in this forum, point the multitude of users who are (or will be)
experiencing this problem to a patch or instructions on how to FIX this
WITHOUT UNINSTALLING ANYTHING ON THE COMPUTER.

In the case of a developer, such as myself, uninstalling the .NET Framework
2.0 and/or SQL Server 2005 is NOT AN OPTION.

Thanks for all reasonable suggestions that work toward a fix without
removing or disabling any other functionality on the computer (i.e.
Development Tools, .NET Framework 2.0, VSTO 200x or any instance of SQL
Server 200x).

Hi-Tek-Nut
 
Oh, I forgot to include some information in the Application log of the Event
Viewer. Perhaps this will help the folks at MS diagnose and suggest a fix /
workaround for this issue....

Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 5000
Date: 2/5/2006
Time: 11:47:43 AM
User: N/A
Computer: {COMPUTERNAME}
Description:
EventType bcm, P1 addin, P2 accessviolationexception, P3 1.0.2002.8, P4
11.0.8002, P5 onstartupcomplete, P6 getexplorer, P7 64852e2e, P8 NIL, P9 NIL,
P10 NIL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 62 00 63 00 6d 00 2c 00 b.c.m.,.
0008: 20 00 61 00 64 00 64 00 .a.d.d.
0010: 69 00 6e 00 2c 00 20 00 i.n.,. .
0018: 61 00 63 00 63 00 65 00 a.c.c.e.
0020: 73 00 73 00 76 00 69 00 s.s.v.i.
0028: 6f 00 6c 00 61 00 74 00 o.l.a.t.
0030: 69 00 6f 00 6e 00 65 00 i.o.n.e.
0038: 78 00 63 00 65 00 70 00 x.c.e.p.
0040: 74 00 69 00 6f 00 6e 00 t.i.o.n.
0048: 2c 00 20 00 31 00 2e 00 ,. .1...
0050: 30 00 2e 00 32 00 30 00 0...2.0.
0058: 30 00 32 00 2e 00 38 00 0.2...8.
0060: 2c 00 20 00 31 00 31 00 ,. .1.1.
0068: 2e 00 30 00 2e 00 38 00 ..0...8.
0070: 30 00 30 00 32 00 2c 00 0.0.2.,.
0078: 20 00 6f 00 6e 00 73 00 .o.n.s.
0080: 74 00 61 00 72 00 74 00 t.a.r.t.
0088: 75 00 70 00 63 00 6f 00 u.p.c.o.
0090: 6d 00 70 00 6c 00 65 00 m.p.l.e.
0098: 74 00 65 00 2c 00 20 00 t.e.,. .
00a0: 67 00 65 00 74 00 65 00 g.e.t.e.
00a8: 78 00 70 00 6c 00 6f 00 x.p.l.o.
00b0: 72 00 65 00 72 00 2c 00 r.e.r.,.
00b8: 20 00 36 00 34 00 38 00 .6.4.8.
00c0: 35 00 32 00 65 00 32 00 5.2.e.2.
00c8: 65 00 2c 00 20 00 4e 00 e.,. .N.
00d0: 49 00 4c 00 2c 00 20 00 I.L.,. .
00d8: 4e 00 49 00 4c 00 20 00 N.I.L. .
00e0: 4e 00 49 00 4c 00 0d 00 N.I.L...
00e8: 0a 00 ..
 
Here's another event in the Application Log in the Event Viewer that is
related. And please note that absolutely ALL available updates for Windows
XP, Office 2003, BCM and Small Business Accounting have been applied.
Windows Update, Office Update and Microsoft Update report that there are no
updates available. I have not applied any other "hotfix" packages other than
what can be downloaded through the 3 update services listed above.

Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 2/5/2006
Time: 11:47:52 AM
User: N/A
Computer: DILBERT
Description:
Faulting application outlook.exe, version 11.0.8000.0, stamp 43599e06,
faulting module outllib.dll, version 11.0.8002.0, stamp 437304bc, debug? 0,
fault address 0x00014c90.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 6f 00 75 00 74 00 .o.u.t.
0030: 6c 00 6f 00 6f 00 6b 00 l.o.o.k.
0038: 2e 00 65 00 78 00 65 00 ..e.x.e.
0040: 20 00 31 00 31 00 2e 00 .1.1...
0048: 30 00 2e 00 38 00 30 00 0...8.0.
0050: 30 00 30 00 2e 00 30 00 0.0...0.
0058: 20 00 34 00 33 00 35 00 .4.3.5.
0060: 39 00 39 00 65 00 30 00 9.9.e.0.
0068: 36 00 20 00 69 00 6e 00 6. .i.n.
0070: 20 00 6f 00 75 00 74 00 .o.u.t.
0078: 6c 00 6c 00 69 00 62 00 l.l.i.b.
0080: 2e 00 64 00 6c 00 6c 00 ..d.l.l.
0088: 20 00 31 00 31 00 2e 00 .1.1...
0090: 30 00 2e 00 38 00 30 00 0...8.0.
0098: 30 00 32 00 2e 00 30 00 0.2...0.
00a0: 20 00 34 00 33 00 37 00 .4.3.7.
00a8: 33 00 30 00 34 00 62 00 3.0.4.b.
00b0: 63 00 20 00 66 00 44 00 c. .f.D.
00b8: 65 00 62 00 75 00 67 00 e.b.u.g.
00c0: 20 00 30 00 20 00 61 00 .0. .a.
00c8: 74 00 20 00 6f 00 66 00 t. .o.f.
00d0: 66 00 73 00 65 00 74 00 f.s.e.t.
00d8: 20 00 30 00 30 00 30 00 .0.0.0.
00e0: 31 00 34 00 63 00 39 00 1.4.c.9.
00e8: 30 00 0d 00 0a 00 0.....
 
OK, troubleshooting this issue a little further now. I will post all of the
Application Event Log entries created when the error is encountered below my
comments. Clicked on the option to send an error report to MS, and received
a page stating that a hotfix is available to resolve the issue. The KB
article for the hotfix is http://support.microsoft.com/?kbid=913707. I will
apply it and test to see if it indeed solves this issue and will report back
on the results of the testing.

Here are the various errors recorded in the Application Log in the Event
Viewer that are associated with this issue:

Event Type: Error
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1000
Date: 2/5/2006
Time: 2:22:43 PM
User: N/A
Computer: WORKSTATION
Description:
Faulting application outlook.exe, version 11.0.8000.0, stamp 43599e06,
faulting module outllib.dll, version 11.0.8002.0, stamp 437304bc, debug? 0,
fault address 0x006ae63b.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 6f 00 75 00 74 00 .o.u.t.
0030: 6c 00 6f 00 6f 00 6b 00 l.o.o.k.
0038: 2e 00 65 00 78 00 65 00 ..e.x.e.
0040: 20 00 31 00 31 00 2e 00 .1.1...
0048: 30 00 2e 00 38 00 30 00 0...8.0.
0050: 30 00 30 00 2e 00 30 00 0.0...0.
0058: 20 00 34 00 33 00 35 00 .4.3.5.
0060: 39 00 39 00 65 00 30 00 9.9.e.0.
0068: 36 00 20 00 69 00 6e 00 6. .i.n.
0070: 20 00 6f 00 75 00 74 00 .o.u.t.
0078: 6c 00 6c 00 69 00 62 00 l.l.i.b.
0080: 2e 00 64 00 6c 00 6c 00 ..d.l.l.
0088: 20 00 31 00 31 00 2e 00 .1.1...
0090: 30 00 2e 00 38 00 30 00 0...8.0.
0098: 30 00 32 00 2e 00 30 00 0.2...0.
00a0: 20 00 34 00 33 00 37 00 .4.3.7.
00a8: 33 00 30 00 34 00 62 00 3.0.4.b.
00b0: 63 00 20 00 66 00 44 00 c. .f.D.
00b8: 65 00 62 00 75 00 67 00 e.b.u.g.
00c0: 20 00 30 00 20 00 61 00 .0. .a.
00c8: 74 00 20 00 6f 00 66 00 t. .o.f.
00d0: 66 00 73 00 65 00 74 00 f.s.e.t.
00d8: 20 00 30 00 30 00 36 00 .0.0.6.
00e0: 61 00 65 00 36 00 33 00 a.e.6.3.
00e8: 62 00 0d 00 0a 00 b.....


Event Type: Information
Event Source: Microsoft Office 11
Event Category: None
Event ID: 1001
Date: 2/5/2006
Time: 2:22:49 PM
User: N/A
Computer: WORKSTATION
Description:
Bucket 257961953, bucket table 1, faulting application outlook.exe, version
11.0.8000.0, stamp 43599e06, faulting module outllib.dll, version
11.0.8002.0, stamp 437304bc, debug? 0, fault address 0x006ae63b.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 00 75 00 63 00 6b 00 B.u.c.k.
0008: 65 00 74 00 3a 00 20 00 e.t.:. .
0010: 32 00 35 00 37 00 39 00 2.5.7.9.
0018: 36 00 31 00 39 00 35 00 6.1.9.5.
0020: 33 00 0d 00 0a 00 42 00 3.....B.
0028: 75 00 63 00 6b 00 65 00 u.c.k.e.
0030: 74 00 54 00 61 00 62 00 t.T.a.b.
0038: 6c 00 65 00 20 00 31 00 l.e. .1.
0040: 0d 00 0a 00 ....
 
I downloaded the hotfix package and extracted the msp (patch installer)
files. I tried both the "optimized" and the "full file" versions of the
patch installer. They both abort installation with error messages. Again
the Application Log in the Event Viewer recorded an error message which is
not very helpful ...

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 1024
Date: 2/5/2006
Time: 2:41:19 PM
User: WORKSTATION\UserName
Computer: WORKSTATION
Description:
Product: Microsoft Office Professional Edition 2003 - Update 'Hotfix for
Office 2003 (KB913695): OUTLOOKff' could not be installed. Error code 1603.
Windows Installer can create logs to help troubleshoot issues with installing
software packages. Use the following link for instructions on turning on
logging support: http://go.microsoft.com/fwlink/?LinkId=23127

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 39 30 31 31 30 34 30 {9011040
0008: 39 2d 36 30 30 30 2d 31 9-6000-1
0010: 31 44 33 2d 38 43 46 45 1D3-8CFE
0018: 2d 30 31 35 30 30 34 38 -0150048
0020: 33 38 33 43 39 7d 20 7b 383C9} {
0028: 37 38 38 34 46 30 39 43 7884F09C
0030: 2d 46 38 37 31 2d 34 34 -F871-44
0038: 38 39 2d 39 43 44 32 2d 89-9CD2-
0040: 32 34 43 46 32 39 35 34 24CF2954
0048: 41 30 39 35 7d 20 31 36 A095} 16
0050: 30 33 03
 
Hi

The post was mention by Bob Watts dated Thursday, January 19, 2006 1:41 AM

btw would be great if you can send me a screen shot of the error to
(e-mail address removed)

I have encountered user with the error and will update the thread once i get
the info as well
 
Not sure if this will take, but I will try to insert a screen shot of the
error. What will work is doing a Ctrl+C on the error dialog to copy its
text. That I know I can post here and will in just a second.

By the way, there are no posts that I can locate in any of the discussion
threads on this site from Bob Watts dated January 19, 2006. Do you have the
URL or thread name you could share?

As I thought. Cannot post a screen shot into the forum thread. Here is the
error message detail -- it is a dialog with the title Business Contact
Manager and has a red 'X' circle icon on it. It offers only the 'OK' button.
The text reads ....


---------------------------
Business Contact Manager
---------------------------
Attempted to read or write protected memory. This is often an indication
that other memory is corrupt. Contact Business Contact Manager Support. You
can find contact information in the "Contact Us" topic in the Business
Contact Manager Help(Help Menu, Business Contact Manager Help).
 
Just posting back to let everyone know the solution to this problem. The
main issue was that this was an ID10T error. While I thought the v2 update
was installed, it was not. A few rebuilds later, I got the order of
installation correct and all of the updates in place. Now SBA SP2, BCM v2
SP2, .NET Framework 2.0, Visual Studio 2005 and VSTO 2005 all co-exist nicely
together.

SQL 2005 Express co-exists well, but I have not been able to make the SQL
Server 2005 Developer Edition co-exist with it -- the machine starts
generating blue screens. Finally I gave up on the idea of having SQL 2005
Developer edition on the machine and will just install that on a separate
computer.

Thanks to Dimitry from MS and on the BCM Product Development Team for his
email and tips pointing me in the right direction! Folks, the people at MS
really do listen and monitor these posts.
 
Back
Top