S
Smart Workplaces
Sorry this is a bit long for a post, but it provides the details needed to
(hopefully) identify the solution. Surely someone else who develops
solutions for MS Office has encountered this situation recently with the
introduction of Visual Studio 2005 and its Tools for Office development
add-in designers.
IF NOT, THEN PERHAPS SOMEONE FROM MS HAS THE ANSWER ???
I have a completely rebuilt pc running Windows XP SP2 and Office 2003 SP2
Professional Enterprise edition with all of the latest updates / patches
available through Windows Update, Office Update and Microsoft Update applied.
Also have the Small Business Accounting 2006 and Outlook BCM apps installed
with the latest updates (called BCM v2 in the Business Contact Manager
forum). Lastly, it is a development machine with Visual Studio 6.0, Visual
Studio .NET 2003 and Visual Studio 2005 installed. Both Visual Studio .NET
2003 and Visual Studio 2005 have the respective Visual Studio Tools for
Office designer components installed.
Everything was working great and the Event Log was totally clean ... until
the .NET Framework 2.0 and SQL Server 2005 were installed. The .NET
Framework 2.0 and SQL Server 2005 Express Edition are installed as a part of
the Visual Studio 2005 Tools for Office installation process.
After installing the 2005 version of VSTO along with .NET Framework 2.0 and
SQL Server 2005 Express, Outlook crashes on launch with the following
critical error:
---------------------------
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).
(hopefully) identify the solution. Surely someone else who develops
solutions for MS Office has encountered this situation recently with the
introduction of Visual Studio 2005 and its Tools for Office development
add-in designers.
IF NOT, THEN PERHAPS SOMEONE FROM MS HAS THE ANSWER ???
I have a completely rebuilt pc running Windows XP SP2 and Office 2003 SP2
Professional Enterprise edition with all of the latest updates / patches
available through Windows Update, Office Update and Microsoft Update applied.
Also have the Small Business Accounting 2006 and Outlook BCM apps installed
with the latest updates (called BCM v2 in the Business Contact Manager
forum). Lastly, it is a development machine with Visual Studio 6.0, Visual
Studio .NET 2003 and Visual Studio 2005 installed. Both Visual Studio .NET
2003 and Visual Studio 2005 have the respective Visual Studio Tools for
Office designer components installed.
Everything was working great and the Event Log was totally clean ... until
the .NET Framework 2.0 and SQL Server 2005 were installed. The .NET
Framework 2.0 and SQL Server 2005 Express Edition are installed as a part of
the Visual Studio 2005 Tools for Office installation process.
After installing the 2005 version of VSTO along with .NET Framework 2.0 and
SQL Server 2005 Express, Outlook crashes on launch with the following
critical error:
---------------------------
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).