Trying to install BCM 2010 x64, getting error

  • Thread starter Thread starter Steve Silverwood
  • Start date Start date
S

Steve Silverwood

At one point, months ago, I uninstalled the 32-bit version of Business
Contact Manager, along with the rest of the 32-bit Office 2010
software. I've now installed the 64-bit versions, but when I try to
install BCM 2010 x64, it says I have to uninstall the previous version
before installing this one. I can't find any entry in Programs and
Features where BCM exists, and the folder where it was installed
(c:\program files (x86)\Microsoft Small Business) doesn't exist.

I =presume= there's something in the Registry that still indicates BCM
x32 is still in there, but I didn't want to go tramping around in the
Registry without at least some guidance.

The operating system is Windows 7 Ultimate, 64-bit.

Any suggestions will be greatly appreciated. Thanks in advance.

-- //Steve//

Steve Silverwood, KB6OJS
Wildomar, California, USA

Email: (e-mail address removed)
Blog: http://stevesilverwood.blogspot.com
Twitter: http://twitter.com/kb6ojs
 
Check & deleted the registry the Business Solution eCRM key under HKLM >
Software > Microsoft and HKCU > Software > Microsoft

Also can you provided the entire error message ?

--
Regards

Rahul Thomas

MSFT
 
Check & deleted the registry the Business Solution eCRM key under HKLM >
Software > Microsoft and HKCU > Software > Microsoft

Also can you provided the entire error message ?

That fix didn't do the trick, sorry. Entire message is:

"You must uninstall other versions of Business Contact Manager before
installing this one."


//Steve//
 
Thanks for the update Steve.

Can you share a copy of the MBSSetup###.log file from the %temp%

--
Regards

Rahul Thomas

MSFT
 
Hi Steve

Apologizes , the name of the file would be BCMsetuptmp####

--
Regards

Rahul Thomas

MSFT
 
Hi Steve

Apologizes , the name of the file would be BCMsetuptmp####

--
Regards

Rahul Thomas

MSFT








- Show quoted text -

Steve,
Can you check this registry instead, since you once had the x86 build
of BCM on your x64 Win7 (thus in WOW mode)?
"HKLM > Software > Wow6432Node > Microsoft > Business Solutions eCRM",
and the matching key under HKCU.

Raul pointed the right direction. I am just double-checking this Wow
node with you.
If the "Business Solutions eCRM" key is found, try exporting it,
deleting it and then run BCM Setup again.
(Note: if you downloaded the .EXE, you can find the unpacked directory
"BCMSetup.en-US" at either C:\Temp or %temp% and run setup.exe
directly, so you don't need to unpack it every time)

Come to think about it... Can you try hard-deleting the "BCMSetup.en-
US" folder, and try unpacking the whole thing from the .EXE again?
I just don't want the files expanded from your old x86 download
pollute your x64 install, since there is a chance that they can be
expanded into the same "BCMSetup.en-US" folder.

Let me know which way works... :)
John
 
Can you check this registry instead, since you once had the x86 build
of BCM on your x64 Win7 (thus in WOW mode)?
"HKLM > Software > Wow6432Node > Microsoft > Business Solutions eCRM",
and the matching key under HKCU.

Raul pointed the right direction. I am just double-checking this Wow
node with you.
If the "Business Solutions eCRM" key is found, try exporting it,
deleting it and then run BCM Setup again.
(Note: if you downloaded the .EXE, you can find the unpacked directory
"BCMSetup.en-US" at either C:\Temp or %temp% and run setup.exe
directly, so you don't need to unpack it every time)

Come to think about it... Can you try hard-deleting the "BCMSetup.en-
US" folder, and try unpacking the whole thing from the .EXE again?
I just don't want the files expanded from your old x86 download
pollute your x64 install, since there is a chance that they can be
expanded into the same "BCMSetup.en-US" folder.

Let me know which way works... :)
John

THAT did the trick! It's installing now, thank you!

//Steve//
 
THAT did the trick!  It's installing now, thank you!

//Steve//- Hide quoted text -

- Show quoted text -

Cool! Good to know. :) Were you seeing the Wow6432Node regkey? I
just wanted to check "which" did the trick, since I kind of suggested
two things at once. :)
John
 
Back
Top