Office 2007 Beta2 and then BCM install trouble

[Jacun01]

Just installed Office 2007 Beta2 and then BCM. Office activated successfully
but for some reason BCM fail during registration with message "Business
Contact Manager for Outlook could not complete you last action or actions.
Please try again".
Program is creating database, then goes to “Introduction†and error message
pops put.
During express installation I have already several “MSSmallBusiness#†created.
After finishing or closing second message shows “Business Contact Manager
for Outlook encountered critical error during strtup and will be removed from
this profileâ€.
Anyone have an idea or know where I could find the bcm installation log or
registration log on my machine to see if there is further info?

Thanks in advance

 

[SusanG]

I'm having a helluva time installing the 2007 BCM Beta to a functional Office
2007, but for different reasons than you. I had two instances of Outlook
installed, 2003 and 2007, and I can't run the 2007 BCM installer to
completion.

However, I did figure out that:
You can check to see if the BCM folder installed, my path was supposed to
be: C:\Program Files\Microsoft Small Business\Business Contact Manager. Mine
did not.

I used Explorer Search to look for all *.log files modified on same day as
each failed attempted install. I got a file called SBSClientApps.log, which
seems to indicate that my BCM install bombed when apps.dat was not found:
6/22/2006 2:10 PM
-- Starting AppLnch.exe --
DoAlwaysRun() - strString []
DoAlwaysRun() -- modified the DNSQueryTimeouts value
DoAlwaysRun() -- set the DumpsterAlwaysOn value
DoAlwaysRun() -- skipping the RestrictAnonymous value setting, not on 2K
Platform
CheckOutlookVersions() - found a 'newer' version [Outlook.Application.12]
GetDatFilePath() -- apps.dat not found. path
[\\ServerName\Clients\Response\COMPUTERNAME\apps.dat]
-- GetDatFilePath() returned FALSE -- Exiting AppLnch.exe --

Each time I try to run the 2007 BCM Installer, each time the file is amended
with more of the same error msg, just different date/time. So that is a
critical logfile, IMO.

I also checked that SQL Server installed and the instance needed for the BCM
is running - (from another post)

Is MSSQL$MicrosoftSmlBiz running? (Start, Run, Services.msc, OK)

This is where I'm stuck. I've got a working Office 2007 Beta install
alongside a working Office 2003 install, with SQL installed and the service
running, but no BCM and can't seem to get it.

 

[Patrick]

I am having serious problems with outlook also. I installed the 2007 Pro
Beta 2 and the rest of the applications installed just fine. They all open
and work normally. I did not uninstall Office Pro 2003. I selected the
"upgrade" installation.

Unfortunately, Outlook 2007 will not open, it gives me an OLMAPI32.dll
error. The how to prevent this from happening again link sends me to message
that says I need the latest Adobe Reader. Adobe reader won't install because
I already have the latest version.

Needless to say, Outlook 2003 will not start either. I get "Cannot start
Microsoft Office Outlook. MAPI32.dll is corrupt or the wrong version. This
could have been caused by installing other messaging software. Please
reinstall Outlook."

Can anyone help???

I'm having a helluva time installing the 2007 BCM Beta to a functional Office
2007, but for different reasons than you. I had two instances of Outlook
installed, 2003 and 2007, and I can't run the 2007 BCM installer to
completion.

However, I did figure out that:
You can check to see if the BCM folder installed, my path was supposed to
be: C:\Program Files\Microsoft Small Business\Business Contact Manager. Mine
did not.

I used Explorer Search to look for all *.log files modified on same day as
each failed attempted install. I got a file called SBSClientApps.log, which
seems to indicate that my BCM install bombed when apps.dat was not found:
6/22/2006 2:10 PM
-- Starting AppLnch.exe --
DoAlwaysRun() - strString []
DoAlwaysRun() -- modified the DNSQueryTimeouts value
DoAlwaysRun() -- set the DumpsterAlwaysOn value
DoAlwaysRun() -- skipping the RestrictAnonymous value setting, not on 2K
Platform
CheckOutlookVersions() - found a 'newer' version [Outlook.Application.12]
GetDatFilePath() -- apps.dat not found. path
[\\ServerName\Clients\Response\COMPUTERNAME\apps.dat]
-- GetDatFilePath() returned FALSE -- Exiting AppLnch.exe --

Each time I try to run the 2007 BCM Installer, each time the file is amended
with more of the same error msg, just different date/time. So that is a
critical logfile, IMO.

I also checked that SQL Server installed and the instance needed for the BCM
is running - (from another post)

Is MSSQL$MicrosoftSmlBiz running? (Start, Run, Services.msc, OK)

This is where I'm stuck. I've got a working Office 2007 Beta install
alongside a working Office 2003 install, with SQL installed and the service
running, but no BCM and can't seem to get it.

Just installed Office 2007 Beta2 and then BCM. Office activated successfully
but for some reason BCM fail during registration with message "Business
Contact Manager for Outlook could not complete you last action or actions.
Please try again".
Program is creating database, then goes to “Introduction†and error message
pops put.
During express installation I have already several “MSSmallBusiness#†created.
After finishing or closing second message shows “Business Contact Manager
for Outlook encountered critical error during strtup and will be removed from
this profileâ€.
Anyone have an idea or know where I could find the bcm installation log or
registration log on my machine to see if there is further info?

Thanks in advance

 

[Leonid S. Knyshov]

I am having serious problems with outlook also. I installed the 2007 Pro
Beta 2 and the rest of the applications installed just fine. They all
open
and work normally. I did not uninstall Office Pro 2003. I selected the
"upgrade" installation.

Unfortunately, Outlook 2007 will not open, it gives me an OLMAPI32.dll
error. The how to prevent this from happening again link sends me to
message
that says I need the latest Adobe Reader. Adobe reader won't install
because
I already have the latest version.

Needless to say, Outlook 2003 will not start either. I get "Cannot start
Microsoft Office Outlook. MAPI32.dll is corrupt or the wrong version.
This
could have been caused by installing other messaging software. Please
reinstall Outlook."

Can anyone help???

What's the URL for that Howto?

Running two versions of Outlook would probably require the trick that we use
to make it run on SBS servers without killing Exchange, which is to create a
folder Outlook.exe.local and to copy its old MAPI support files into it.
That trick breaks on Outlook 2007, by the way.

It's a little complicated. I'd uninstall Outlook 2003.
--
Leonid S. Knyshov, CEO
Crashproof Solutions, LLC - http://www.crashproofsolutions.com
MCP Exchange 2003/Small Business Server 2003
Microsoft Small Business Specialist Partner
See the tips and tricks section on my website for video tutorials on BCM

 

[SusanG]

I think now, like a poster today, that this problem occurred after I applied
all the security patches to the Beta installation. Shoot! Last week I applied
the patches, then my user logged onto my Beta machine to check her email and
that's when it broke. Probaby less to do with having Office 2003 running
alongside Office 2007 Beta.

 

[Patrick]

Actually Patrick Schmid helped me out on this. I had to uninstall all of the
Office 2007 Beta 2 release. I then fixed the 2003 (I had already tried the
MAPI32 fix with both still installed-should not have worked, but I was
running a registry mechanic that fixed all the things I broke installing
both). After I made sure I had 2003 working again (reboot between each
step), I did a custom install that deleted Outlook 2003 and installed Outlook
2007 with the rest of the Office 2007 components. I still had to reset the
IMAP services I had, but now Outlook 2007 works for me (no 2003 anymore).

I had only selected "upgrade" and not custom install originally.

Patrick W.

 

[Blueskat]

Actually Patrick Schmid helped me out on this. I had to uninstall all of the
Office 2007 Beta 2 release. I then fixed the 2003 (I had already tried the
MAPI32 fix with both still installed-should not have worked, but I was
running a registry mechanic that fixed all the things I broke installing
both). After I made sure I had 2003 working again (reboot between each
step), I did a custom install that deleted Outlook 2003 and installed Outlook
2007 with the rest of the Office 2007 components. I still had to reset the
IMAP services I had, but now Outlook 2007 works for me (no 2003 anymore).

I had only selected "upgrade" and not custom install originally.

Patrick W.

 

[Blueskat]

Sorry about the misfire.

I also have installed Office Pro 2007 beta without any trouble ... except
that BCM will not integrate with Outlook.

BCM installer runs to completion, but I am not prompted to create a
database. Seems to be a problem with the SQL server, which is not running.

Any ideas?

 

[Mukesh]

It is possible that BCM add-in somehow got disabled. Goto Tools->Trust Center
in Outlook and see if BCM add-in is in list of disabled add-in. Enable it if
so. Restart Outlook and hopefully you should see BCM configuration wizard.

If that doesn't work, Start->Control Panel->Mail-Profile. Click Outlook
profile that you want to have BCM in. Click Data Files and Create New data
file. In follow up dialog, you should see Business Contact Manager databae as
one of the option. Selecting that will bring up screen for creating BCM
database or selecting existing database.

 

[Kalikitty]

I also received this error. It turned out to be two things... Outlook 2003
was conflicting, and then it was an installation error. I uninstalled Outlook
2007 Beta, then uninstalled 2003. Re-booted. Then re-installed 2007 Beta, ran
Office Diagnogstics and the problem was fixed. I am back up and running
perfectly. All my setting were saved, accounts and all. I did make a backup
just in case. Good luck all.

I am having serious problems with outlook also. I installed the 2007 Pro
Beta 2 and the rest of the applications installed just fine. They all open
and work normally. I did not uninstall Office Pro 2003. I selected the
"upgrade" installation.

Unfortunately, Outlook 2007 will not open, it gives me an OLMAPI32.dll
error. The how to prevent this from happening again link sends me to message
that says I need the latest Adobe Reader. Adobe reader won't install because
I already have the latest version.

Needless to say, Outlook 2003 will not start either. I get "Cannot start
Microsoft Office Outlook. MAPI32.dll is corrupt or the wrong version. This
could have been caused by installing other messaging software. Please
reinstall Outlook."

Can anyone help???

I'm having a helluva time installing the 2007 BCM Beta to a functional Office
2007, but for different reasons than you. I had two instances of Outlook
installed, 2003 and 2007, and I can't run the 2007 BCM installer to
completion.

However, I did figure out that:
You can check to see if the BCM folder installed, my path was supposed to
be: C:\Program Files\Microsoft Small Business\Business Contact Manager. Mine
did not.

I used Explorer Search to look for all *.log files modified on same day as
each failed attempted install. I got a file called SBSClientApps.log, which
seems to indicate that my BCM install bombed when apps.dat was not found:
6/22/2006 2:10 PM
-- Starting AppLnch.exe --
DoAlwaysRun() - strString []
DoAlwaysRun() -- modified the DNSQueryTimeouts value
DoAlwaysRun() -- set the DumpsterAlwaysOn value
DoAlwaysRun() -- skipping the RestrictAnonymous value setting, not on 2K
Platform
CheckOutlookVersions() - found a 'newer' version [Outlook.Application.12]
GetDatFilePath() -- apps.dat not found. path
[\\ServerName\Clients\Response\COMPUTERNAME\apps.dat]
-- GetDatFilePath() returned FALSE -- Exiting AppLnch.exe --

Each time I try to run the 2007 BCM Installer, each time the file is amended
with more of the same error msg, just different date/time. So that is a
critical logfile, IMO.

I also checked that SQL Server installed and the instance needed for the BCM
is running - (from another post)

Is MSSQL$MicrosoftSmlBiz running? (Start, Run, Services.msc, OK)

This is where I'm stuck. I've got a working Office 2007 Beta install
alongside a working Office 2003 install, with SQL installed and the service
running, but no BCM and can't seem to get it.

Just installed Office 2007 Beta2 and then BCM. Office activated successfully
but for some reason BCM fail during registration with message "Business
Contact Manager for Outlook could not complete you last action or actions.
Please try again".
Program is creating database, then goes to “Introduction†and error message
pops put.
During express installation I have already several “MSSmallBusiness#†created.
After finishing or closing second message shows “Business Contact Manager
for Outlook encountered critical error during strtup and will be removed from
this profileâ€.
Anyone have an idea or know where I could find the bcm installation log or
registration log on my machine to see if there is further info?

Thanks in advance