B2TR Outlook with BCM -- BCM will not run, uninstall, or repair

[DABrownCA]

I was running Outlook with BCM 2007 without problems. I installed the TR and
ran into trouble with the BCM TR. Now, I have B2TR Outlook installed and
some form of BCM on my system. The uninstaller for Beta does not recognize
the BCM version. Outlook B2TR issues an error at startup saying that the BCM
version is incompatible. The uninstaller for B2TR BCM also fails. BCM B2TR
is in a strange state. BCM will not run, will not uninstall, will not
reinstall, and will not repair.

What can I do to get this feature running?

 

[Leonid S. Knyshov]

I was running Outlook with BCM 2007 without problems. I installed the TR
and
ran into trouble with the BCM TR. Now, I have B2TR Outlook installed and
some form of BCM on my system. The uninstaller for Beta does not
recognize
the BCM version. Outlook B2TR issues an error at startup saying that the
BCM
version is incompatible. The uninstaller for B2TR BCM also fails. BCM
B2TR
is in a strange state. BCM will not run, will not uninstall, will not
reinstall, and will not repair.

What can I do to get this feature running?

When I ran into this with SBA 2007, I had to manually recreate the install
folder structure.

Check your %temp% folder (start, Run, %temp%, OK) for log files as they
should offer additionaal clues. It sounds like B2TR did not get installed
and an uninstall of B2 original BCM is in order.
--
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
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[DABrownCA]

I have been working on this for some time, now. The failure point has moved
from SQL to msiexec (progress, I think?!). Now, the logfile reports
<MainEngineThread is returning 1605>.

Any thoughts? All suggestions and work-arounds are appreciated.

 

[Leonid S. Knyshov]

I have been working on this for some time, now. The failure point has
moved
from SQL to msiexec (progress, I think?!). Now, the logfile reports
<MainEngineThread is returning 1605>.

Any thoughts? All suggestions and work-arounds are appreciated.

Please post the entire log file, and not as an attachment. Let's see where
it's stopping in reality.

I probably can make it work for you remotely, but we charge for that
service.
--
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
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[DABrownCA]

The following comprises the complete log file. If I am interpreting this
correctly, the installer is attempting to find a previously installed GUID.
Since the present number for Outlook 2007 differs from that of my prior 2003
installation (or a file is corrupted), it cannot uninstall potentially
conflicting files; so, the program is forced to terminate.

Let me know what you think. If a little guidance will get this feature
running, then I shall be grateful for your input. If it proves more
difficult, then we should discuss what it would take to complete the
recovery. --Thank you for your comments and insights.


=== Verbose logging started: 10/31/2006 12:12:47 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (38:20) [12:12:47:359]: Resetting cached policy values
MSI (c) (38:20) [12:12:47:359]: Machine policy value 'Debug' is 0
MSI (c) (38:20) [12:12:47:359]: ******* RunEngine:
******* Product: {B32C4059-6E7A-41EF-AD20-56DF1872B923}
******* Action:
******* CommandLine: **********
MSI (c) (38:20) [12:12:47:375]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (38:20) [12:12:47:375]: Grabbed execution mutex.
MSI (c) (38:20) [12:12:47:375]: Cloaking enabled.
MSI (c) (38:20) [12:12:47:375]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (38:20) [12:12:47:390]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (34:48) [12:12:47:390]: Grabbed execution mutex.
MSI (s) (34:0C) [12:12:47:390]: Resetting cached policy values
MSI (s) (34:0C) [12:12:47:390]: Machine policy value 'Debug' is 0
MSI (s) (34:0C) [12:12:47:390]: ******* RunEngine:
******* Product: {B32C4059-6E7A-41EF-AD20-56DF1872B923}
******* Action:
******* CommandLine: **********
MSI (s) (34:0C) [12:12:47:390]: Machine policy value 'DisableUserInstalls'
is 0
MSI (s) (34:0C) [12:12:47:406]: MainEngineThread is returning 1605
MSI (c) (38:20) [12:12:47:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (38:20) [12:12:47:406]: MainEngineThread is returning 1605
=== Verbose logging stopped: 10/31/2006 12:12:47 ===

 

[Luther]

The mysteries of msiexec....

It appears that the main setup program launched a second setup package
(sql server? accounting connectivity? BCM itself?) which did not log
any errors itself but failed, and the main setup program then stopped
when it got the failure code.

This analysis is based entirely on the abscene of any useful (1605?)
information in the log and my own experience with msiexec.

I would remove all pertinent software (including the office interop
assemblies, which gave me grief last month; the sql 2005 small business
instance--the sql uninstall will ask if you want to remove this
instance) and start from scratch.

The following comprises the complete log file. If I am interpreting this
correctly, the installer is attempting to find a previously installed GUID.
Since the present number for Outlook 2007 differs from that of my prior 2003
installation (or a file is corrupted), it cannot uninstall potentially
conflicting files; so, the program is forced to terminate.

Let me know what you think. If a little guidance will get this feature
running, then I shall be grateful for your input. If it proves more
difficult, then we should discuss what it would take to complete the
recovery. --Thank you for your comments and insights.


=== Verbose logging started: 10/31/2006 12:12:47 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (38:20) [12:12:47:359]: Resetting cached policy values
MSI (c) (38:20) [12:12:47:359]: Machine policy value 'Debug' is 0
MSI (c) (38:20) [12:12:47:359]: ******* RunEngine:
******* Product: {B32C4059-6E7A-41EF-AD20-56DF1872B923}
******* Action:
******* CommandLine: **********
MSI (c) (38:20) [12:12:47:375]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (38:20) [12:12:47:375]: Grabbed execution mutex.
MSI (c) (38:20) [12:12:47:375]: Cloaking enabled.
MSI (c) (38:20) [12:12:47:375]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (38:20) [12:12:47:390]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (34:48) [12:12:47:390]: Grabbed execution mutex.
MSI (s) (34:0C) [12:12:47:390]: Resetting cached policy values
MSI (s) (34:0C) [12:12:47:390]: Machine policy value 'Debug' is 0
MSI (s) (34:0C) [12:12:47:390]: ******* RunEngine:
******* Product: {B32C4059-6E7A-41EF-AD20-56DF1872B923}
******* Action:
******* CommandLine: **********
MSI (s) (34:0C) [12:12:47:390]: Machine policy value 'DisableUserInstalls'
is 0
MSI (s) (34:0C) [12:12:47:406]: MainEngineThread is returning 1605
MSI (c) (38:20) [12:12:47:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (38:20) [12:12:47:406]: MainEngineThread is returning 1605
=== Verbose logging stopped: 10/31/2006 12:12:47 ===

Please post the entire log file, and not as an attachment. Let's see where
it's stopping in reality.

I probably can make it work for you remotely, but we charge for that
service.
--
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
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[Leonid S. Knyshov]

The following comprises the complete log file. If I am interpreting this
correctly, the installer is attempting to find a previously installed
GUID.
Since the present number for Outlook 2007 differs from that of my prior
2003
installation (or a file is corrupted), it cannot uninstall potentially
conflicting files; so, the program is forced to terminate.

Let me know what you think. If a little guidance will get this feature
running, then I shall be grateful for your input. If it proves more
difficult, then we should discuss what it would take to complete the
recovery. --Thank you for your comments and insights.

Looks like that log is incomplete.

There are other logs. Windows Installer cleanup tool may help to clean up
this mess. Or perhaps restoring the LSI for the previous version of office.

I posted a technique how to install the SQL server instance in case like
this before. I think I have a copy of that article on my site.
--
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
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[DABrownCA]

Thank you for your reply. You are correct, there are other logs; however,
the posting above is the complete text of the last log created. Moreover,
all of the previous logs indicate a successful installation and termination
of the installer.

The data seem to suggest that the sought GUID is different from the one
actually installed. If this is true, then one must ask, how can I break-out
of this seemingly intractable situation? All attempts to install,
re-install, uninstall and repair have produced an error message showing a
failed installation.

Does anyone know how to force the unsinstall? Are there specfic files that
one could remove manually that would allow the un-installation to succeed?

 

[Leonid S. Knyshov]

Thank you for your reply. You are correct, there are other logs; however,
the posting above is the complete text of the last log created. Moreover,
all of the previous logs indicate a successful installation and
termination
of the installer.

The data seem to suggest that the sought GUID is different from the one
actually installed. If this is true, then one must ask, how can I
break-out
of this seemingly intractable situation? All attempts to install,
re-install, uninstall and repair have produced an error message showing a
failed installation.

Does anyone know how to force the unsinstall? Are there specfic files
that
one could remove manually that would allow the un-installation to succeed?

There is a tool called Windows Install Cleanup

http://support.microsoft.com/kb/555175 - techniques for troubleshooting MSI
http://support.microsoft.com/kb/290301 - MSI cleanup tool

The issue I foresee is fixing the .NET framework issues after using the
cleanup tool.
--
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
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy

 

[DABrownCA]

Thanks. I will try the tool. It should help with at least part of the
problem.

I also think you are right about the .net situation. I have encountered one
or two other things that suggest not all is well in the .net Framework.

 

[Leonid S. Knyshov]

Thanks. I will try the tool. It should help with at least part of the
problem.

I also think you are right about the .net situation. I have encountered
one
or two other things that suggest not all is well in the .net Framework.

Yeah we suggest to run .NET Repair usually. It is in the add/remove
programs, highlight .Net framework, click change, click repair. I doubt that
will fix the whole situation though.
--
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
Send a smile to Microsoft (Office 2007 Beta feedback tool)!
http://tinyurl.com/m4omy