Outlook w/ Business Contact Manager

-- I'm trying to install Office 2003 with BCM on my Dell with XP Pro. Office
has installed fine, but the Business Contact Mgr install attempt results in
error messages: "command line option syntax error", then "requires .net
framework 1.1. Dectect and Install?" (Yes) then "cannot access Windows
Installer components". Install attempt series ends with a "install failed"
message. HELP ! ! !

mark Finney

Mark--

You might want to go to the run box and type in "eventvwr.msc" and see if
you are getting any errors with numbers assigned that can offer any
additional information--you may or may not--the time of the problem by
clicking on Application and also any with MsiInstaller as the source at that
time.

Check to see that you have the latest Windows installer for your version of
Windows XP (whichever it is) SP1 2+ and SP2 3+ by typing in the run box
"msiexec help."

You can repair an MSI Windows Installer Service) via whether you are
actually getting Error 1719 or not. You can't hurt yourself by
reregistering the MSI.

"Error 1719. The Windows Installer service could not be accessed" error
message when you try to add or remove a program
http://support.microsoft.com/default.aspx?scid=kb;[LN];315346

If you do end up uninstalling Office as below, I would use the Windows
Installer Clean Up Utility. A description and the download package are
here.

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;[LN];290301

I like this explanation of the Cleanup Utility by Sloan Crayton of MSFT the
best--I think it is the clearest I've seen, so I'm quoting it here:

"When the Windows Installer was first being created, a tool called
MSIZap was created that would be able to 'zap' an application's Installer
registry information. Later it was included in the Windows Installer SDK
products. That tool is a command line utility that must be used via command
prompt; so it's not the most user friendly utility.

To answer a need for a utility that could more easily be used by the
majority of users that need a way to recover a corrup installation, the
Windows Installer Cleanup Utility was created that leverages the
functionality of MSIZap but provides nice wizard-like UI.

The function of the utility is to remove the remove the corrupted Windows
Installer registry information for an application that was installed via the
Windows Installer. There are several things that it does not do ...
- It does not uninstall any applications
- It does not delete the Windows Installer

After using this utility, the application should then be installed again so
that Setup will function (otherwise, the Windows Installer has no
information that it was ever installed). If the real objective is to remove
a product, it can be uninstalled after this reinstall has occurred."

*Tips For Installing and Running BCM*

Some people have found that you need to do the following to get BCM
installed.

1) Some people may have to enable File and Print Sharing at the three places
below to get BCM either in or once in to get the add-in associated properly
with Outlook when you fire up Outlook. I'd check and see if the first two
work and then go to these if you're either having BCM install problems or
getting BCM started with Outlook.

Enabled at Lan Properties
Enabled at the Printer
Enabled via the Server Entry in Services Started and On (See Below)

2) Type "services.msc" in your run box. I want you to turn on two
entries to at least manual (automatic means they'll always start up on and
start them.

Make sure the Server service is started. (Supports file, print, and pipe
sharing over the network)

3) Turn off Auto Protect, Script Blocking, and Office Plugins if present on
any Antivirus app such as Norton for example before trying to install.

4) Make sure that another application like an RSS feeder or any beta
application is *not using a .net framework beyond 1.1 plus.*
That's the native one required for BCM, and if you are using others you are
going to need a special patch.
BCM does need the 1.1 .net framework, but on the install it should prompt
you to install it automatically.
http://msdn.microsoft.com/netframework/

Alexander Gorlach has posted along these lines on this groupand he keeps a
blog that has his patches and expertise on this at :

http://blogs.officezealot.com/gorla...ves/000858.html

Alexander Gorlach,
MAPILab Ltd.
http://www.mapilab.com/


5) I have *never* found this necessary, but some people with SQL expertise
have found they have to go here and do this: Run box>type
"compmgt.msc">Local Users>Click Groups >Click BCM users Rt. Pane> or you can
get there this way *Check your BCMUsergroup and make sure you have this user
added (logged onas Administrator): Start>Control Panel>Administrative Tools
(or type"lusrmgr.msc" in the run box)>ComputerManagement>Open Local Users
and GroupsDouble Click Groups>(Then in Rt. PaneDouble Click
BCMUsersGroup)>On Botttom of General Tab>Add Button>in the boxenter
"Authenticated Users" so that NT Authority\Authenticated users will be
added to this group.* This profile may be necessary even if you aren't
seeing the error message addressed in this KB #830318:

You Receive an Error Message When You Start Outlook with Business Contact
Manager 2003
http://support.microsoft.com/defaul...oduct=out200311

By the way, the KB has wrong instructions. It has type "the authenticated
users" in to add, and "the" just is not going to work. You need to type
"Authenticated users" only in. MSFT has been informed of this for six
months, but the group responsible for the BCM KBs has not taken the "the"
out. This is one situation where the meaning of "is" and the existence of
"the" is important.

6) If you have some type PDA in a cradle connected to your box, you might
need to disconnect the cradle. Some say it interferes. I have seen it run
OL in the background after you kill OL, some before and sometimes.

7)You may want to uninstall BCM and reinstall it turning off Auto Protect,
Script Blocking, and any Office Add-ins if present in your AV app. Then
delete any files and folders found here in these folders:
C:\ProgramFiles\Microsoft SQL and Server\MSSQL$MICROSOFTBCM and delete
the following registry keys:

HKLM\Software\ODBC\ODBC.INI\BCM
HKLM\System\ControlSet001\Services\MSSQL$MicrosoftBCM
HKLM\System\ControlSet001\Services\SQLAgent$MicrosoftBCM

Reinstall BCM

8) Check that this Registry D_Word value for Load Behavior is set to
3:HKLM\Software\Microsoft\Office\Outlook\Addins\Microsoft.BusinessSolutions.eCRM.OutlookAddin.Connect.1
key. If the value for LoadBehavior is somethingother than 3, make a backup
of the registry, edit LoadBehavior to set it to3, then restart Outlook


9) Once you get it in, to make sure it gets up and running, type
"services.msc" in your run box. I want you to turn on three entries to at
least manual (automatic means they'll always start up on and start them.
BCM uses a mini-MSDE SQL data base engine and it needs these services
started for it to run.

Turn on these 3 services:

1) MSSQL$MSFTBCM (Installed with BCM) Again make sure Office and then
BCM
are installed or this won't be listed.
2) SQLAGENT$MicrosoftBCM should be started if it's listed.
3) Server (Supports file, print, and pipe sharing over the network)

*Additional References for BCM*

*MSKBs on the First Version of the BCM .net Add-In To Outlook To Date*
http://tinyurl.com/53nxp

Cannot Hide or Show the Business Contact Manager Toolbar in Outlook 2003
http://support.microsoft.com/defaul...Product=out2003

Business Contact Manager menu items are missing in Outlook 2003
http://support.microsoft.com/defaul...Product=out2003

You cannot create a new database for Business Contact Manager when you
start Outlook 2003
http://support.microsoft.com/defaul...Product=out2003

You also might want to keep up with blogs like this one
http://blogs.officezealot.com/cardoza/
because Patricia Cordoza is keeping up with BCM developments for books and
articles, and also helping to liason with MSFT for the next version's
features.
hth,

Chad Harris
________________________________________________________________________________


"fynney1" <fynney1@discussions.microsoft.com> wrote in message
news:6301315C-3F52-4D09-8EC5-1E42777DBDAF@microsoft.com...

-- I'm trying to install Office 2003 with BCM on my Dell with XP Pro.
Office
has installed fine, but the Business Contact Mgr install attempt results in
error messages: "command line option syntax error", then "requires .net
framework 1.1. Dectect and Install?" (Yes) then "cannot access Windows
Installer components". Install attempt series ends with a "install failed"
message. HELP ! ! !

mark Finney

Fynnne--

There are two more points I should mention.

1) There may be some helpful updated information at the Office Website under
BCM Assistance here:

http://office.microsoft.com/assista...=HP010729111033

2) Microsoft issued a new KB recently on BCM association with Outlook, but
in keeping with their MO of scattering tips among `5 or so Outlook and SQL
KBs and upholding the Redmond Raiders of the Lost Ark the SQL (no puns)
tradition, they mentioned one of my tips but did offer trying to *create a
new data base*: (One reason I made the tips list is because of my
frustration that MSFT scatters tips by stringing one at a time out via
different OL and SQL KBs and I very much appreciate prompt help I got in
finding some of the tips on this group including Patricia Cordoza and Sue
Mosher).

The Microsoft Business Contact Manager add-in for Microsoft Office Outlook
2003 does not associate with any Outlook profile: 870641 August 13, 2004
http://support.microsoft.com/defaul...kb;EN-US;870641

From the recent KB (the only item in it I didn't mention which I have not
found helpful but obviously enough people have for MSFT's BCM Team to put it
in the KB:


If you do not receive a prompt to use Business Contact Manager with your
current Outlook profile, follow these steps:
1.. On the File menu, click Data File Management.
2.. Click Add, click Business Contact Manager Database under Types of
storage, and then click OK.
3.. In the Associate Database Wizard, click Create a new database, and
then click Next.
4.. Under Type a name for the new database, type the name, and then click
Next.
5.. Click Finish, and then click Close.
6.. Quit, and then restart Office Outlook 2003.

Best,

Chad Harris
_____________________________________________________



"fynney1" <fynney1@discussions.microsoft.com> wrote in message
news:3214305B-628B-460E-A67D-29EC67322102@microsoft.com...
Thank you for the tips! I have not yet been able to check them all out, but
at least I have options to explore.

Thanks!

"Chad Harris" wrote:

> Mark--
>
> You might want to go to the run box and type in "eventvwr.msc" and see if
> you are getting any errors with numbers assigned that can offer any
> additional information--you may or may not--the time of the problem by
> clicking on Application and also any with MsiInstaller as the source at
> that
> time.
>
> Check to see that you have the latest Windows installer for your version
> of
> Windows XP (whichever it is) SP1 2+ and SP2 3+ by typing in the run box
> "msiexec help."
>
> You can repair an MSI Windows Installer Service) via whether you are
> actually getting Error 1719 or not. You can't hurt yourself by
> reregistering the MSI.
>
> "Error 1719. The Windows Installer service could not be accessed" error
> message when you try to add or remove a program
> http://support.microsoft.com/default.aspx?scid=kb;[LN];315346
>
> If you do end up uninstalling Office as below, I would use the Windows
> Installer Clean Up Utility. A description and the download package are
> here.
>
> Description of the Windows Installer CleanUp Utility
> http://support.microsoft.com/default.aspx?scid=kb;[LN];290301
>
> I like this explanation of the Cleanup Utility by Sloan Crayton of MSFT
> the
> best--I think it is the clearest I've seen, so I'm quoting it here:
>
> "When the Windows Installer was first being created, a tool called
> MSIZap was created that would be able to 'zap' an application's Installer
> registry information. Later it was included in the Windows Installer SDK
> products. That tool is a command line utility that must be used via
> command
> prompt; so it's not the most user friendly utility.
>
> To answer a need for a utility that could more easily be used by the
> majority of users that need a way to recover a corrup installation, the
> Windows Installer Cleanup Utility was created that leverages the
> functionality of MSIZap but provides nice wizard-like UI.
>
> The function of the utility is to remove the remove the corrupted Windows
> Installer registry information for an application that was installed via
> the
> Windows Installer. There are several things that it does not do ...
> - It does not uninstall any applications
> - It does not delete the Windows Installer
>
> After using this utility, the application should then be installed again
> so
> that Setup will function (otherwise, the Windows Installer has no
> information that it was ever installed). If the real objective is to
> remove
> a product, it can be uninstalled after this reinstall has occurred."
>
> *Tips For Installing and Running BCM*
>
> Some people have found that you need to do the following to get BCM
> installed.
>
> 1) Some people may have to enable File and Print Sharing at the three
> places
> below to get BCM either in or once in to get the add-in associated
> properly
> with Outlook when you fire up Outlook. I'd check and see if the first two
> work and then go to these if you're either having BCM install problems or
> getting BCM started with Outlook.
>
> Enabled at Lan Properties
> Enabled at the Printer
> Enabled via the Server Entry in Services Started and On (See Below)
>
> 2) Type "services.msc" in your run box. I want you to turn on two
> entries to at least manual (automatic means they'll always start up on and
> start them.
>
> Make sure the Server service is started. (Supports file, print, and pipe
> sharing over the network)
>
> 3) Turn off Auto Protect, Script Blocking, and Office Plugins if present
> on
> any Antivirus app such as Norton for example before trying to install.
>
> 4) Make sure that another application like an RSS feeder or any beta
> application is *not using a .net framework beyond 1.1 plus.*
> That's the native one required for BCM, and if you are using others you
> are
> going to need a special patch.
> BCM does need the 1.1 .net framework, but on the install it should prompt
> you to install it automatically.
> http://msdn.microsoft.com/netframework/
>
> Alexander Gorlach has posted along these lines on this groupand he keeps a
> blog that has his patches and expertise on this at :
>
> http://blogs.officezealot.com/gorla...ves/000858.html
>
> Alexander Gorlach,
> MAPILab Ltd.
> http://www.mapilab.com/
>
>
> 5) I have *never* found this necessary, but some people with SQL
> expertise
> have found they have to go here and do this: Run box>type
> "compmgt.msc">Local Users>Click Groups >Click BCM users Rt. Pane> or you
> can
> get there this way *Check your BCMUsergroup and make sure you have this
> user
> added (logged onas Administrator): Start>Control Panel>Administrative
> Tools
> (or type"lusrmgr.msc" in the run box)>ComputerManagement>Open Local Users
> and GroupsDouble Click Groups>(Then in Rt. PaneDouble Click
> BCMUsersGroup)>On Botttom of General Tab>Add Button>in the boxenter
> "Authenticated Users" so that NT Authority\Authenticated users will be
> added to this group.* This profile may be necessary even if you aren't
> seeing the error message addressed in this KB #830318:
>
> You Receive an Error Message When You Start Outlook with Business Contact
> Manager 2003
> http://support.microsoft.com/defaul...oduct=out200311
>
> By the way, the KB has wrong instructions. It has type "the authenticated
> users" in to add, and "the" just is not going to work. You need to type
> "Authenticated users" only in. MSFT has been informed of this for six
> months, but the group responsible for the BCM KBs has not taken the "the"
> out. This is one situation where the meaning of "is" and the existence of
> "the" is important.
>
> 6) If you have some type PDA in a cradle connected to your box, you might
> need to disconnect the cradle. Some say it interferes. I have seen it
> run
> OL in the background after you kill OL, some before and sometimes.
>
> 7)You may want to uninstall BCM and reinstall it turning off Auto
> Protect,
> Script Blocking, and any Office Add-ins if present in your AV app. Then
> delete any files and folders found here in these folders:
> C:\ProgramFiles\Microsoft SQL and Server\MSSQL$MICROSOFTBCM and delete
> the following registry keys:
>
> HKLM\Software\ODBC\ODBC.INI\BCM
> HKLM\System\ControlSet001\Services\MSSQL$MicrosoftBCM
> HKLM\System\ControlSet001\Services\SQLAgent$MicrosoftBCM
>
> Reinstall BCM
>
> 8) Check that this Registry D_Word value for Load Behavior is set to
> 3:HKLM\Software\Microsoft\Office\Outlook\Addins\Microsoft.BusinessSolutions.eCRM.OutlookAddin.Connect.1
> key. If the value for LoadBehavior is somethingother than 3, make a backup
> of the registry, edit LoadBehavior to set it to3, then restart Outlook
>
>
> 9) Once you get it in, to make sure it gets up and running, type
> "services.msc" in your run box. I want you to turn on three entries to
> at
> least manual (automatic means they'll always start up on and start them.
> BCM uses a mini-MSDE SQL data base engine and it needs these services
> started for it to run.
>
> Turn on these 3 services:
>
> 1) MSSQL$MSFTBCM (Installed with BCM) Again make sure Office and then
> BCM
> are installed or this won't be listed.
> 2) SQLAGENT$MicrosoftBCM should be started if it's listed.
> 3) Server (Supports file, print, and pipe sharing over the network)
>
> *Additional References for BCM*
>
> *MSKBs on the First Version of the BCM .net Add-In To Outlook To Date*
> http://tinyurl.com/53nxp
>
> Cannot Hide or Show the Business Contact Manager Toolbar in Outlook 2003
> http://support.microsoft.com/defaul...Product=out2003
>
> Business Contact Manager menu items are missing in Outlook 2003
> http://support.microsoft.com/defaul...Product=out2003
>
> You cannot create a new database for Business Contact Manager when you
> start Outlook 2003
> http://support.microsoft.com/defaul...Product=out2003
>
> You also might want to keep up with blogs like this one
> http://blogs.officezealot.com/cardoza/
> because Patricia Cordoza is keeping up with BCM developments for books and
> articles, and also helping to liason with MSFT for the next version's
> features.
> hth,
>
> Chad Harris
> ________________________________________________________________________________
>
>
> "fynney1" <fynney1@discussions.microsoft.com> wrote in message
> news:6301315C-3F52-4D09-8EC5-1E42777DBDAF@microsoft.com...
>
> -- I'm trying to install Office 2003 with BCM on my Dell with XP Pro.
> Office
> has installed fine, but the Business Contact Mgr install attempt results
> in
> error messages: "command line option syntax error", then "requires .net
> framework 1.1. Dectect and Install?" (Yes) then "cannot access Windows
> Installer components". Install attempt series ends with a "install
> failed"
> message. HELP ! ! !
>
> mark Finney
>
>
>

Jeez, wouldn't it be a lot easier to use Act! 2005 instead? Hell, why doesn't Bill just buy Act! and put it into Office? It would
make a lot more sense than One Note, which I suspect is used by about One User.

I'm not really being facetious; I've been contemplating a move to Office 2003 (from Word 97, no less!) just for Outlook 2003+BCM,
but the more research I do, the more I'm realizing that I'm being attracted by my *fantasy* of what Outlook 2003+BCM *could* be if
fully integrated with Office. But it seems like that dream has NOTHING to do with the reality, which sounds like a lame, kludgy,
straitjacketed nightmare. I mean, my God, all this trouble to install this DOG of an uncustomizable activity tracker that doesn't
even store its data in the same place as your contacts? Sheesh!

Why is Microsoft working on XML and animated help characters? There is no function more important than what BCM could be, if it
actually WORKED.

Anyway, I LOVE Word 97, and the Outlook 2003+BCM+tightly-integrated-Office workflow fantasy is the first time I ever thought of
upgrading. I'm so glad I did the research in time to keep myself from making that leap off the cliff. And thank God I found this
forum!

I have no doubt this will all work great in v.3.0, so I'll have another look in 2006.



"Chad Harris" <ddram32_nospam@yahoo.com> wrote in message news:u2W1MYgiEHA.3348@TK2MSFTNGP12.phx.gbl...
> Fynnne--
>
> There are two more points I should mention.
>
> 1) There may be some helpful updated information at the Office Website under BCM Assistance here:
>
> http://office.microsoft.com/assista...=HP010729111033
>
> 2) Microsoft issued a new KB recently on BCM association with Outlook, but in keeping with their MO of scattering tips among `5
> or so Outlook and SQL KBs and upholding the Redmond Raiders of the Lost Ark the SQL (no puns) tradition, they mentioned one of my
> tips but did offer trying to *create a new data base*: (One reason I made the tips list is because of my frustration that MSFT
> scatters tips by stringing one at a time out via different OL and SQL KBs and I very much appreciate prompt help I got in
> finding some of the tips on this group including Patricia Cordoza and Sue Mosher).
>
> The Microsoft Business Contact Manager add-in for Microsoft Office Outlook 2003 does not associate with any Outlook profile:
> 870641 August 13, 2004
> http://support.microsoft.com/defaul...kb;EN-US;870641
>
> From the recent KB (the only item in it I didn't mention which I have not found helpful but obviously enough people have for
> MSFT's BCM Team to put it in the KB:
>
>
> If you do not receive a prompt to use Business Contact Manager with your current Outlook profile, follow these steps:
> 1.. On the File menu, click Data File Management.
> 2.. Click Add, click Business Contact Manager Database under Types of storage, and then click OK.
> 3.. In the Associate Database Wizard, click Create a new database, and then click Next.
> 4.. Under Type a name for the new database, type the name, and then click Next.
> 5.. Click Finish, and then click Close.
> 6.. Quit, and then restart Office Outlook 2003.
>
> Best,
>
> Chad Harris
> _____________________________________________________
>
>
>
> "fynney1" <fynney1@discussions.microsoft.com> wrote in message news:3214305B-628B-460E-A67D-29EC67322102@microsoft.com...
> Thank you for the tips! I have not yet been able to check them all out, but
> at least I have options to explore.
>
> Thanks!
>
> "Chad Harris" wrote:
>
>> Mark--
>>
>> You might want to go to the run box and type in "eventvwr.msc" and see if
>> you are getting any errors with numbers assigned that can offer any
>> additional information--you may or may not--the time of the problem by
>> clicking on Application and also any with MsiInstaller as the source at that
>> time.
>>
>> Check to see that you have the latest Windows installer for your version of
>> Windows XP (whichever it is) SP1 2+ and SP2 3+ by typing in the run box
>> "msiexec help."
>>
>> You can repair an MSI Windows Installer Service) via whether you are
>> actually getting Error 1719 or not. You can't hurt yourself by
>> reregistering the MSI.
>>
>> "Error 1719. The Windows Installer service could not be accessed" error
>> message when you try to add or remove a program
>> http://support.microsoft.com/default.aspx?scid=kb;[LN];315346
>>
>> If you do end up uninstalling Office as below, I would use the Windows
>> Installer Clean Up Utility. A description and the download package are
>> here.
>>
>> Description of the Windows Installer CleanUp Utility
>> http://support.microsoft.com/default.aspx?scid=kb;[LN];290301
>>
>> I like this explanation of the Cleanup Utility by Sloan Crayton of MSFT the
>> best--I think it is the clearest I've seen, so I'm quoting it here:
>>
>> "When the Windows Installer was first being created, a tool called
>> MSIZap was created that would be able to 'zap' an application's Installer
>> registry information. Later it was included in the Windows Installer SDK
>> products. That tool is a command line utility that must be used via command
>> prompt; so it's not the most user friendly utility.
>>
>> To answer a need for a utility that could more easily be used by the
>> majority of users that need a way to recover a corrup installation, the
>> Windows Installer Cleanup Utility was created that leverages the
>> functionality of MSIZap but provides nice wizard-like UI.
>>
>> The function of the utility is to remove the remove the corrupted Windows
>> Installer registry information for an application that was installed via the
>> Windows Installer. There are several things that it does not do ...
>> - It does not uninstall any applications
>> - It does not delete the Windows Installer
>>
>> After using this utility, the application should then be installed again so
>> that Setup will function (otherwise, the Windows Installer has no
>> information that it was ever installed). If the real objective is to remove
>> a product, it can be uninstalled after this reinstall has occurred."
>>
>> *Tips For Installing and Running BCM*
>>
>> Some people have found that you need to do the following to get BCM
>> installed.
>>
>> 1) Some people may have to enable File and Print Sharing at the three places
>> below to get BCM either in or once in to get the add-in associated properly
>> with Outlook when you fire up Outlook. I'd check and see if the first two
>> work and then go to these if you're either having BCM install problems or
>> getting BCM started with Outlook.
>>
>> Enabled at Lan Properties
>> Enabled at the Printer
>> Enabled via the Server Entry in Services Started and On (See Below)
>>
>> 2) Type "services.msc" in your run box. I want you to turn on two
>> entries to at least manual (automatic means they'll always start up on and
>> start them.
>>
>> Make sure the Server service is started. (Supports file, print, and pipe
>> sharing over the network)
>>
>> 3) Turn off Auto Protect, Script Blocking, and Office Plugins if present on
>> any Antivirus app such as Norton for example before trying to install.
>>
>> 4) Make sure that another application like an RSS feeder or any beta
>> application is *not using a .net framework beyond 1.1 plus.*
>> That's the native one required for BCM, and if you are using others you are
>> going to need a special patch.
>> BCM does need the 1.1 .net framework, but on the install it should prompt
>> you to install it automatically.
>> http://msdn.microsoft.com/netframework/
>>
>> Alexander Gorlach has posted along these lines on this groupand he keeps a
>> blog that has his patches and expertise on this at :
>>
>> http://blogs.officezealot.com/gorla...ves/000858.html
>>
>> Alexander Gorlach,
>> MAPILab Ltd.
>> http://www.mapilab.com/
>>
>>
>> 5) I have *never* found this necessary, but some people with SQL expertise
>> have found they have to go here and do this: Run box>type
>> "compmgt.msc">Local Users>Click Groups >Click BCM users Rt. Pane> or you can
>> get there this way *Check your BCMUsergroup and make sure you have this user
>> added (logged onas Administrator): Start>Control Panel>Administrative Tools
>> (or type"lusrmgr.msc" in the run box)>ComputerManagement>Open Local Users
>> and GroupsDouble Click Groups>(Then in Rt. PaneDouble Click
>> BCMUsersGroup)>On Botttom of General Tab>Add Button>in the boxenter
>> "Authenticated Users" so that NT Authority\Authenticated users will be
>> added to this group.* This profile may be necessary even if you aren't
>> seeing the error message addressed in this KB #830318:
>>
>> You Receive an Error Message When You Start Outlook with Business Contact
>> Manager 2003
>> http://support.microsoft.com/defaul...oduct=out200311
>>
>> By the way, the KB has wrong instructions. It has type "the authenticated
>> users" in to add, and "the" just is not going to work. You need to type
>> "Authenticated users" only in. MSFT has been informed of this for six
>> months, but the group responsible for the BCM KBs has not taken the "the"
>> out. This is one situation where the meaning of "is" and the existence of
>> "the" is important.
>>
>> 6) If you have some type PDA in a cradle connected to your box, you might
>> need to disconnect the cradle. Some say it interferes. I have seen it run
>> OL in the background after you kill OL, some before and sometimes.
>>
>> 7)You may want to uninstall BCM and reinstall it turning off Auto Protect,
>> Script Blocking, and any Office Add-ins if present in your AV app. Then
>> delete any files and folders found here in these folders:
>> C:\ProgramFiles\Microsoft SQL and Server\MSSQL$MICROSOFTBCM and delete
>> the following registry keys:
>>
>> HKLM\Software\ODBC\ODBC.INI\BCM
>> HKLM\System\ControlSet001\Services\MSSQL$MicrosoftBCM
>> HKLM\System\ControlSet001\Services\SQLAgent$MicrosoftBCM
>>
>> Reinstall BCM
>>
>> 8) Check that this Registry D_Word value for Load Behavior is set to
>> 3:HKLM\Software\Microsoft\Office\Outlook\Addins\Microsoft.BusinessSolutions.eCRM.OutlookAddin.Connect.1
>> key. If the value for LoadBehavior is somethingother than 3, make a backup
>> of the registry, edit LoadBehavior to set it to3, then restart Outlook
>>
>>
>> 9) Once you get it in, to make sure it gets up and running, type
>> "services.msc" in your run box. I want you to turn on three entries to at
>> least manual (automatic means they'll always start up on and start them.
>> BCM uses a mini-MSDE SQL data base engine and it needs these services
>> started for it to run.
>>
>> Turn on these 3 services:
>>
>> 1) MSSQL$MSFTBCM (Installed with BCM) Again make sure Office and then
>> BCM
>> are installed or this won't be listed.
>> 2) SQLAGENT$MicrosoftBCM should be started if it's listed.
>> 3) Server (Supports file, print, and pipe sharing over the network)
>>
>> *Additional References for BCM*
>>
>> *MSKBs on the First Version of the BCM .net Add-In To Outlook To Date*
>> http://tinyurl.com/53nxp
>>
>> Cannot Hide or Show the Business Contact Manager Toolbar in Outlook 2003
>> http://support.microsoft.com/defaul...Product=out2003
>>
>> Business Contact Manager menu items are missing in Outlook 2003
>> http://support.microsoft.com/defaul...Product=out2003
>>
>> You cannot create a new database for Business Contact Manager when you
>> start Outlook 2003
>> http://support.microsoft.com/defaul...Product=out2003
>>
>> You also might want to keep up with blogs like this one
>> http://blogs.officezealot.com/cardoza/
>> because Patricia Cordoza is keeping up with BCM developments for books and
>> articles, and also helping to liason with MSFT for the next version's
>> features.
>> hth,
>>
>> Chad Harris
>> ________________________________________________________________________________
>>
>>
>> "fynney1" <fynney1@discussions.microsoft.com> wrote in message
>> news:6301315C-3F52-4D09-8EC5-1E42777DBDAF@microsoft.com...
>>
>> -- I'm trying to install Office 2003 with BCM on my Dell with XP Pro.
>> Office
>> has installed fine, but the Business Contact Mgr install attempt results in
>> error messages: "command line option syntax error", then "requires .net
>> framework 1.1. Dectect and Install?" (Yes) then "cannot access Windows
>> Installer components". Install attempt series ends with a "install failed"
>> message. HELP ! ! !
>>
>> mark Finney
>>
>>
>>
>
>