I thought that I would be using Outlook with BCM on a regular basis by now. But my plans got derailed when I ran into difficulties installing it in my own Small Business Server environment and when I got nervous about the impact it might have on synchronizing my contacts with my Windows Mobile 5 phone. So I’m afraid I can’t tell you whether this marketing move is a good, bad, or inconsequential thing for small businesses. If I hear more, I’ll pass it along.

This is still not a wizard-driven process by any means and the average user of BCM is not going to want to attempt this alone. I hope the BCM development team is still working on a way to make this setup process easier.

When I click Details, I get the text below. I’ve clicked Continue and Close (X) multiple times with no effect. I have to Ctrl-Alt-Del to quit Outlook. Sigh ….

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipDrawRectangleI(HandleRef graphics, HandleRef pen, Int32 x, Int32 y, Int32 width, Int32 height)
at System.Drawing.Graphics.DrawRectangle(Pen pen, Int32 x, Int32 y, Int32 width, Int32 height)
at System.Windows.Forms.Control.PaintException(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.DataGridView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.190 (QFE.050727-1900)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
—————————————-
Microsoft.BusinessSolutions.eCRM.OutlookAddIn
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.BusinessSolutions.eCRM.OutlookAddIn/3.0.0.0__31bf3856ad364e35/Microsoft.BusinessSolutions.eCRM.OutlookAddIn.dll
—————————————-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
Iris.Mapi.MessageStore
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Iris.Mapi.MessageStore/3.0.0.0__31bf3856ad364e35/Iris.Mapi.MessageStore.dll
—————————————-
Microsoft.Interop.Mapi.Interfaces
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.Interop.Mapi.Interfaces/3.0.0.0__31bf3856ad364e35/Microsoft.Interop.Mapi.Interfaces.dll
—————————————-
BusinessLayer
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/BusinessLayer/3.0.0.0__31bf3856ad364e35/BusinessLayer.dll
—————————————-
BCMRes
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/BCMRes/3.0.0.0__31bf3856ad364e35/BCMRes.dll
—————————————-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
—————————————-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
—————————————-
office
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1014
CodeBase: file:///C:/WINDOWS/assembly/GAC/office/12.0.0.0__71e9bce111e9429c/office.dll
—————————————-
BCMCommon
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/BCMCommon/3.0.0.0__31bf3856ad364e35/BCMCommon.dll
—————————————-
Microsoft.Office.Interop.Outlook
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1014
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.Office.Interop.Outlook/12.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Outlook.dll
—————————————-
Microsoft.Interop.Mapi.PropTags
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.Interop.Mapi.PropTags/3.0.0.0__31bf3856ad364e35/Microsoft.Interop.Mapi.PropTags.dll
—————————————-
Microsoft.BusinessSolutions.eCRM.DataSync
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.BusinessSolutions.eCRM.DataSync/3.0.0.0__31bf3856ad364e35/Microsoft.BusinessSolutions.eCRM.DataSync.dll
—————————————-
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd/msvcm80.dll
—————————————-
Microsoft.Interop.Mapi.Impl
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.Interop.Mapi.Impl/3.0.0.0__31bf3856ad364e35/Microsoft.Interop.Mapi.Impl.dll
—————————————-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
—————————————-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
—————————————-
BusinessLayer.resources
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/Program%20Files/Microsoft%20Small%20Business/Business%20Contact%20Manager/en-US/BusinessLayer.resources.DLL
—————————————-
BCMRes.resources
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/Program%20Files/Microsoft%20Small%20Business/Business%20Contact%20Manager/en-US/BCMRes.resources.DLL
—————————————-
Microsoft.Interop.Mapi.Interfaces.resources
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/Program%20Files/Microsoft%20Small%20Business/Business%20Contact%20Manager/en-US/Microsoft.Interop.Mapi.Interfaces.resources.DLL
—————————————-
Extensibility
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase: file:///C:/WINDOWS/assembly/GAC/Extensibility/7.0.3300.0__b03f5f7f11d50a3a/Extensibility.dll
—————————————-
Microsoft.BusinessSolutions.eCRM.OutlookAddIn.CSUtils
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.BusinessSolutions.eCRM.OutlookAddIn.CSUtils/3.0.0.0__31bf3856ad364e35/Microsoft.BusinessSolutions.eCRM.OutlookAddIn.CSUtils.dll
—————————————-
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
—————————————-
stdole
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase: file:///C:/WINDOWS/assembly/GAC/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
—————————————-
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
—————————————-
Microsoft.Interop.eCRM.Ole
Assembly Version: 1.0.0.3
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Interop.eCRM.Ole/1.0.0.3__31bf3856ad364e35/Microsoft.Interop.eCRM.Ole.dll
—————————————-
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.190 (QFE.050727-1900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
—————————————-
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
—————————————-
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
—————————————-
Microsoft.Interop.eCRM.msforms
Assembly Version: 2.0.0.3
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Interop.eCRM.msforms/2.0.0.3__31bf3856ad364e35/Microsoft.Interop.eCRM.msforms.dll
—————————————-
Microsoft.Interop.eCRM.MSComCtl
Assembly Version: 2.0.0.3
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Interop.eCRM.MSComCtl/2.0.0.3__31bf3856ad364e35/Microsoft.Interop.eCRM.MSComCtl.dll
—————————————-
Microsoft.Vbe.Interop.Forms
Assembly Version: 11.0.0.0
Win32 Version: 12.0.4518.1014
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.Vbe.Interop.Forms/11.0.0.0__71e9bce111e9429c/Microsoft.Vbe.Interop.Forms.dll
—————————————-
Microsoft.BusinessSolutions.eCRM.OutlookAddIn.CSUtils.resources
Assembly Version: 3.0.0.0
Win32 Version: 3.0.5828.0
CodeBase: file:///C:/Program%20Files/Microsoft%20Small%20Business/Business%20Contact%20Manager/en-US/Microsoft.BusinessSolutions.eCRM.OutlookAddIn.CSUtils.resources.DLL
—————————————-

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging=”true” />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

As more and more people start sending BCM customers to that document, there are going to be more and more frustrated BCM customers. The typo is acknowledged in a comment on the BCM FAQ, but as of today the whitepaper has not been updated.

Come on, guys. A couple minutes of effort now is going to save you hours of support calls later on.

Before you go through the rest of these steps, you probably want to check to see who the database owner is. To do that, use these menu items in Outlook with BCM:

You’ll see the database owner displayed:

In the screen shot above, you’ll see that I’ve already successfully changed the owner to my regular user account. It used to have the domain administrator account there. If you’ve already got the name of the user who is supposed to be the owner, then you should be all set and you can skip the rest. If not, read on.

I am decidedly not a SQL maven, but I do know how to do a Google search for SQL 2005 change database owner. That search led me to the SQL Server 2005 Books Online at MSDN. I was able to muddle my way through a series of commands that enabled me to change the database owner from SCHRAG\administrator to SCHRAG\david. (Note to SBS gurus: Yes, I have actually renamed my administrator account, but if I told you what it is here, that would be defeating the purpose, wouldn’t it?)

I’m sure that any serious SQL admin would laugh at the ugliness of the instructions I’m about to give, but they worked for me. Log into the server as the domain admin, get to a command prompt, and do the following [do not include the stuff in brackets; that's my own commentary]:

>sqlcmd -S .\mssmallbiz [where mssmallbiz is the name of your SQL instance; mssmallbiz is recommended]

1>use bcm_db [where bcm_db is the name of your BCM database; you named it during setup]

2>go

Changed database context to ‘BCM_DB’.

1>sp_dropuser @name_in_db = ‘DOMAIN\user’ [where DOMAIN is your Windows domain and user is the name of the user who will eventually be the owner; if you don't drop this user first, you can't make him or her the owner; I think the DROP USER command ought to work instead of sp_dropuser, but it didn't work for me]

2>go

1>sp_changedbowner @loginame = ‘DOMAIN\user’ [note that there's only one n in loginame]

2>go

1>exit

Now go back into Outlook and go to the Manage Database screen. Is the new owner’s name shown there? Great!

With the help of Vikas Madan at Microsoft, I finally found the problem. I had created the shared database with a beta version of Outlook 2007 with BCM. In the meantime, though, I had started using the final version of Outlook 2007 on my PC. It turns out the final version of Outlook won’t talk to a beta-version database.

After I used the correct SQL script from the whitepaper to migrate the database from beta to final AND ran the db_sharedusers.sql script – don’t overlook that second step!! – I was able to connect my Outlook client to the shared database.

Now I just have to learn how to use the program. No sweat. 8^)

First, you need to understand that the way the document is formatted, it looks like there are a series of commands here, several of which start on a new line. That is not right. The command needs to be given all at once, with nothing but spaces where it looks like you need carriage returns.

Second, you will notice that the command ends with a double-quote (“), but there is no double-quote earlier in the command so the statement is invalid. There should be a double-quote before the word CREATE right at the beginning of the command.

So here’s what the command actually looks like for me, run from a command prompt on my Small Business Server:

C:\>sqlcmd -S .\MSSMLBIZ -E -Q “CREATE DATABASE [BCM_DB] ON (NAME = N’BCM_DB_dat’, FILENAME = N’F:\BCM2007\BCM_DB.mdf’, SIZE = 25, FILEGROWTH = 50%) LOG ON (NAME = N’BCM_DB_log’, FILENAME = N’F:\BCM2007\BCM_DB.ldf’, SIZE = 10,FILEGROWTH = 50%) Collate SQL_Latin1_General_CP1_CI_AS exec sp_dboption N’BCM_DB’, N’autoclose’, N’false’ exec sp_dboption N’BCM_DB’, N’bulkcopy’, N’true’ exec sp_dboption N’BCM_DB’, N’trunc. log’, N’true’ exec sp_dboption N’BCM_DB’, N’torn page detection’, N’true’ exec sp_dboption N’BCM_DB’, N’read only’, N’false’ exec sp_dboption N’BCM_DB’, N’dbo use’, N’false’ exec sp_dboption N’BCM_DB’, N’single’, N’false’ exec sp_dboption N’BCM_DB’, N’autoshrink’, N’false’ exec sp_dboption N’BCM_DB’, N’ANSI null default’, N’false’ exec sp_dboption N’BCM_DB’, N’recursive triggers’, N’false’ exec sp_dboption N’BCM_DB’, N’ANSI nulls’, N’false’ exec sp_dboption N’BCM_DB’, N’concat null yields null’, N’false’ exec sp_dboption N’BCM_DB’, N’cursor close on commit’, N’false’ exec sp_dboption N’BCM_DB’, N’default to local cursor’, N’false’ exec sp_dboption N’BCM_DB’, N’quoted identifier’, N’false’ exec sp_dboption N’BCM_DB’, N’ANSI warnings’, N’false’ exec sp_dboption N’BCM_DB’, N’auto create statistics’, N’true’ exec sp_dboption N’BCM_DB’, N’auto update statistics’, N’true’”

To modify this command for your own use, you’ll need to change the variables MSSMLBIZ, BCM_DB, and F:\BCM2007 to fit your particular environment. This will make more sense once you read pages 9 and 10 of the instructions.

Thanks to Mehul Shah at Microsoft for working with me to find the typo in the document and giving me the correct information.

There may be additional roadblocks later in the document. If I come across any, I’ll let you know.

Office 2007, which is just now hitting the market, is available in about as many different varieties as Starbucks coffee. Unfortunately, Microsoft is making it very difficult for folks like me to figure out which variety to recommend to small businesses that might want Business Contact Manager. Take a look at this product grid. You’ll notice that Business Contact Manager is not included in the two suites at the upper end of the spectrum: Professional Plus and Enterprise.

But now read this language from Microsoft’s December 2006 Product List (emphasis added):

Microsoft Office 2007 Professional Plus
A License for Microsoft Office 2007 Professional Plus consists of the following: Microsoft Access 2007, Microsoft Office Communicator 2007, Microsoft Excel 2007, Microsoft InfoPath 2007, Microsoft Outlook 2007, Microsoft Outlook 2007 with Microsoft Business Contact manager, Microsoft PowerPoint 2007, Microsoft Publisher 2007, Microsoft Word 2007, Microsoft Publisher 2007, Microsoft InfoPath 2007, Microsoft Office Communicator 2005.

Microsoft Office 2007 Enterprise
A License for Microsoft Office 2007 Enterprise consists of the following: Microsoft Office Access 2007, Microsoft Office Communicator 2007, Microsoft Office Excel 2007, Microsoft Office Groove 2007, Microsoft Office InfoPath 2007, Microsoft OneNote 2007, Microsoft Office Outlook 2007, Microsoft Office Outlook 2007 with Microsoft Business Contact manager, Microsoft Office PowerPoint 2007, Microsoft Office Publisher 2007, Microsoft Office Word 2007.

I believe that the Product List carries more legal authority than any marketing document that might appear on a Microsoft web site, so I think that businesses who own one of these two suites will be safe in installing BCM. If I get further clarification from MS, I’ll let you know.

Meanwhile, stay tuned for another post soon about the real problem with the Office 2007 suites for small businesses.