H
Hi-Tek-Nut
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
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