2007 setup/ Remove '03 first?

B

Beth Melton

I'm not 100% certain it will work, since I haven't tried it myself,
but all the Windows Installer Cleanup does is zap the installer
entries in the Registry - it doesn't remove any application files.

In your error log it has: "MSI(INFO): 'This patch package could not be
opened" which indicates the issue lies in the Windows Installer
entries. Here's another KB if you want to take a look at it as well:
http://support.microsoft.com/kb/295823

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
M

Milhouse Van Houten

I was leery of of the collateral damage of using the Cleanup utility,
particularly with the warning in the Readme ("NOTE: The Windows Installer
Clean Up Utility should not be used to remove the 2007 Microsoft Office
System installation information), so I tried some last-ditch efforts before
resorting to it (my first-ditch efforts are too numerous to mention).

I noticed that even right-clicking one of the individual MSIs and clicking
Uninstall yielded the same "patch package could not be opened...", so that
wasn't an option, either.

Then I found this post:
http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3

The key part of it was this:
1) you might want to try deleting the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid for
office 2000}\Patches

I tested it on the two OneNote instances first to see if it had any effect
(OneNote was a separate install), and remarkably, deleting the two 'Patches'
branches for OneNote allowed the uninstall to actually get off the ground
and work.

I then did the same for the 10 (or so) remaining 'Patches' entries for the
rest of Office, then ran the main uninstall, and that worked, too.

Remarkable. This may have been much the same thing the Cleanup utility would
have done, but at least this way I knew what was happening. There was a
little bit of mop-up work to do afterwards, but nothing that significant.

I truly hope that MS doesn't try one of these massive "Refresh" patches with
the next beta, as they've done with the betas for 2003 and 2007 (at least).
When it works it works, when it doesn't it's a spectacular mess. They should
just release a fresh build (as they supplied the press: they could install
B2TR fresh), not a patch.

Thanks
 
M

Milhouse Van Houten

I was leery of of the collateral damage of using the Cleanup utility,
particularly with the warning in the Readme ("NOTE: The Windows Installer
Clean Up Utility should not be used to remove the 2007 Microsoft Office
System installation information), so I tried some last-ditch efforts before
resorting to it (my first-ditch efforts are too numerous to mention).

I noticed that even right-clicking one of the individual MSIs and clicking
Uninstall yielded the same "patch package could not be opened...", so that
wasn't an option, either.

Then I found this post:
http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3

The key part of it was this:
1) you might want to try deleting the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid for
office 2000}\Patches

I tested it on the two OneNote instances first to see if it had any effect
(OneNote was a separate install), and remarkably, deleting the two 'Patches'
branches for OneNote allowed the uninstall to actually get off the ground
and work.

I then did the same for the 10 (or so) remaining 'Patches' entries for the
rest of Office, then ran the main uninstall, and that worked, too.

Remarkable. This may have been much the same thing the Cleanup utility would
have done, but at least this way I knew what was happening. There was a
little bit of mop-up work to do afterwards, but nothing that significant.

I truly hope that MS doesn't try one of these massive "Refresh" patches with
the next beta, as they've done with the betas for 2003 and 2007 (at least).
When it works it works, when it doesn't it's a spectacular mess. They should
just release a fresh build (as they supplied the press: they could install
B2TR fresh), not a patch.

Thanks
 
M

Milhouse Van Houten

I was leery of of the collateral damage of using the Cleanup utility,
particularly with the warning in the Readme ("NOTE: The Windows Installer
Clean Up Utility should not be used to remove the 2007 Microsoft Office
System installation information), so I tried some last-ditch efforts before
resorting to it (my first-ditch efforts are too numerous to mention).

I noticed that even right-clicking one of the individual MSIs and clicking
Uninstall yielded the same "patch package could not be opened...", so that
wasn't an option, either.

Then I found this post:
http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3

The key part of it was this:
1) you might want to try deleting the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid for
office 2000}\Patches

I tested it on the two OneNote instances first to see if it had any effect
(OneNote was a separate install), and remarkably, deleting the two 'Patches'
branches for OneNote allowed the uninstall to actually get off the ground
and work.

I then did the same for the 10 (or so) remaining 'Patches' entries for the
rest of Office, then ran the main uninstall, and that worked, too.

Remarkable. This may have been much the same thing the Cleanup utility would
have done, but at least this way I knew what was happening. There was a
little bit of mop-up work to do afterwards, but nothing that significant.

I truly hope that MS doesn't try one of these massive "Refresh" patches with
the next beta, as they've done with the betas for 2003 and 2007 (at least).
When it works it works, when it doesn't it's a spectacular mess. They should
just release a fresh build (as they supplied the press: they could install
B2TR fresh), not a patch.

Thanks
 
M

Milhouse Van Houten

I was leery of of the collateral damage of using the Cleanup utility,
particularly with the warning in the Readme ("NOTE: The Windows Installer
Clean Up Utility should not be used to remove the 2007 Microsoft Office
System installation information), so I tried some last-ditch efforts before
resorting to it (my first-ditch efforts are too numerous to mention).

I noticed that even right-clicking one of the individual MSIs and clicking
Uninstall yielded the same "patch package could not be opened...", so that
wasn't an option, either.

Then I found this post:
http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3

The key part of it was this:
1) you might want to try deleting the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid for
office 2000}\Patches

I tested it on the two OneNote instances first to see if it had any effect
(OneNote was a separate install), and remarkably, deleting the two 'Patches'
branches for OneNote allowed the uninstall to actually get off the ground
and work.

I then did the same for the 10 (or so) remaining 'Patches' entries for the
rest of Office, then ran the main uninstall, and that worked, too.

Remarkable. This may have been much the same thing the Cleanup utility would
have done, but at least this way I knew what was happening. There was a
little bit of mop-up work to do afterwards, but nothing that significant.

I truly hope that MS doesn't try one of these massive "Refresh" patches with
the next beta, as they've done with the betas for 2003 and 2007 (at least).
When it works it works, when it doesn't it's a spectacular mess. They should
just release a fresh build (as they supplied the press: they could install
B2TR fresh), not a patch.

Thanks
 
B

Beth Melton

Now I understand why you referenced the KB - I skimmed it and must
have missed the warning at the end. Sorry about that - all of this is
new territory right now. :)

Actually, I think I picked up on: "Therefore, if you cannot remove
2007 Office suites, check the Microsoft Office newsgroups for
information about how to manually remove 2007 Office suites from the
computer." and overlooked the warning. (I won't share my thoughts on
reading the note - but it was definitely a distraction. lol)

Anyway, I suspect it's due to B2TR getting delivered as a patch and
the Windows Installer would only remove B2 and the B2TR references
would remain. I'll have to ask around to make sure for future
reference, though.

Prior to the creation of the Windows Installer Cleanup utility I
experimented with manually deleing the entries. While it worked I
wasn't sure it would be that easy! What I wasn't considering were the
other references to the GUID in the Registry. So manual removal can be
done but all references should be deleted as well - the Windows
Installer Cleanup utility will remove all of them. So...right now
that's the only thing I wonder about on removing the references
manually - that others may have been left behind.

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
B

Beth Melton

Now I understand why you referenced the KB - I skimmed it and must
have missed the warning at the end. Sorry about that - all of this is
new territory right now. :)

Actually, I think I picked up on: "Therefore, if you cannot remove
2007 Office suites, check the Microsoft Office newsgroups for
information about how to manually remove 2007 Office suites from the
computer." and overlooked the warning. (I won't share my thoughts on
reading the note - but it was definitely a distraction. lol)

Anyway, I suspect it's due to B2TR getting delivered as a patch and
the Windows Installer would only remove B2 and the B2TR references
would remain. I'll have to ask around to make sure for future
reference, though.

Prior to the creation of the Windows Installer Cleanup utility I
experimented with manually deleing the entries. While it worked I
wasn't sure it would be that easy! What I wasn't considering were the
other references to the GUID in the Registry. So manual removal can be
done but all references should be deleted as well - the Windows
Installer Cleanup utility will remove all of them. So...right now
that's the only thing I wonder about on removing the references
manually - that others may have been left behind.

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
B

Beth Melton

Now I understand why you referenced the KB - I skimmed it and must
have missed the warning at the end. Sorry about that - all of this is
new territory right now. :)

Actually, I think I picked up on: "Therefore, if you cannot remove
2007 Office suites, check the Microsoft Office newsgroups for
information about how to manually remove 2007 Office suites from the
computer." and overlooked the warning. (I won't share my thoughts on
reading the note - but it was definitely a distraction. lol)

Anyway, I suspect it's due to B2TR getting delivered as a patch and
the Windows Installer would only remove B2 and the B2TR references
would remain. I'll have to ask around to make sure for future
reference, though.

Prior to the creation of the Windows Installer Cleanup utility I
experimented with manually deleing the entries. While it worked I
wasn't sure it would be that easy! What I wasn't considering were the
other references to the GUID in the Registry. So manual removal can be
done but all references should be deleted as well - the Windows
Installer Cleanup utility will remove all of them. So...right now
that's the only thing I wonder about on removing the references
manually - that others may have been left behind.

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
B

Beth Melton

Now I understand why you referenced the KB - I skimmed it and must
have missed the warning at the end. Sorry about that - all of this is
new territory right now. :)

Actually, I think I picked up on: "Therefore, if you cannot remove
2007 Office suites, check the Microsoft Office newsgroups for
information about how to manually remove 2007 Office suites from the
computer." and overlooked the warning. (I won't share my thoughts on
reading the note - but it was definitely a distraction. lol)

Anyway, I suspect it's due to B2TR getting delivered as a patch and
the Windows Installer would only remove B2 and the B2TR references
would remain. I'll have to ask around to make sure for future
reference, though.

Prior to the creation of the Windows Installer Cleanup utility I
experimented with manually deleing the entries. While it worked I
wasn't sure it would be that easy! What I wasn't considering were the
other references to the GUID in the Registry. So manual removal can be
done but all references should be deleted as well - the Windows
Installer Cleanup utility will remove all of them. So...right now
that's the only thing I wonder about on removing the references
manually - that others may have been left behind.

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
M

Milly Staples [MVP - Outlook]

Have you checked Patrick Schmid's blogs for this error? I seem to recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Now I understand why you referenced the KB - I skimmed it and must
| have missed the warning at the end. Sorry about that - all of this is
| new territory right now. :)
|
| Actually, I think I picked up on: "Therefore, if you cannot remove
| 2007 Office suites, check the Microsoft Office newsgroups for
| information about how to manually remove 2007 Office suites from the
| computer." and overlooked the warning. (I won't share my thoughts on
| reading the note - but it was definitely a distraction. lol)
|
| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
|
| Prior to the creation of the Windows Installer Cleanup utility I
| experimented with manually deleing the entries. While it worked I
| wasn't sure it would be that easy! What I wasn't considering were the
| other references to the GUID in the Registry. So manual removal can be
| done but all references should be deleted as well - the Windows
| Installer Cleanup utility will remove all of them. So...right now
| that's the only thing I wonder about on removing the references
| manually - that others may have been left behind.
|
| Please post all follow-up questions to the newsgroup. Requests for
| assistance by email can not be acknowledged.
|
| ~~~~~~~~~~~~~~~
| Beth Melton
| Microsoft Office MVP
|
| TechTrax eZine: http://mousetrax.com/techtrax/
| MVP FAQ site: http://mvps.org/
|
| || I was leery of of the collateral damage of using the Cleanup utility,
|| particularly with the warning in the Readme ("NOTE: The Windows
|| Installer Clean Up Utility should not be used to remove the 2007
|| Microsoft Office System installation information), so I tried some
|| last-ditch efforts before resorting to it (my first-ditch efforts are
|| too numerous to mention).
||
|| I noticed that even right-clicking one of the individual MSIs and
|| clicking Uninstall yielded the same "patch package could not be
|| opened...", so that wasn't an option, either.
||
|| Then I found this post:
|| http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3
||
|| The key part of it was this:
|| 1) you might want to try deleting the key:
|| HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid
|| for office 2000}\Patches
||
|| I tested it on the two OneNote instances first to see if it had any
|| effect (OneNote was a separate install), and remarkably, deleting
|| the two 'Patches' branches for OneNote allowed the uninstall to
|| actually get off the ground and work.
||
|| I then did the same for the 10 (or so) remaining 'Patches' entries
|| for the rest of Office, then ran the main uninstall, and that
|| worked, too.
||
|| Remarkable. This may have been much the same thing the Cleanup
|| utility would have done, but at least this way I knew what was
|| happening. There was a little bit of mop-up work to do afterwards,
|| but nothing that significant.
||
|| I truly hope that MS doesn't try one of these massive "Refresh"
|| patches with the next beta, as they've done with the betas for 2003
|| and 2007 (at least). When it works it works, when it doesn't it's a
|| spectacular mess. They should just release a fresh build (as they
|| supplied the press: they could install B2TR fresh), not a patch.
||
|| Thanks
||
|| ||| I'm not 100% certain it will work, since I haven't tried it myself,
||| but all the Windows Installer Cleanup does is zap the installer
||| entries in the Registry - it doesn't remove any application files.
|||
||| In your error log it has: "MSI(INFO): 'This patch package could not
||| be opened" which indicates the issue lies in the Windows Installer
||| entries. Here's another KB if you want to take a look at it as
||| well:
||| http://support.microsoft.com/kb/295823
|||
||| Please post all follow-up questions to the newsgroup. Requests for
||| assistance by email can not be acknowledged.
|||
||| ~~~~~~~~~~~~~~~
||| Beth Melton
||| Microsoft Office MVP
|||
||| TechTrax eZine: http://mousetrax.com/techtrax/
||| MVP FAQ site: http://mvps.org/
|||
||| |||| Is that good to use with Office 2007?
|||| http://support.microsoft.com/default.aspx/kb/923718/en-us
||||
|||| ||||| If I'm not mistaken, if you turn on "Show Updates" then B2TR is
||||| listed separately.
|||||
||||| If the installer files are missing then see if Windows Installer
||||| Cleanup utility works for you. Use it to remove only the
||||| references to the Office 2007 beta version. Once that is complete
||||| then you'll need to reinstall the beta to point the Windows
||||| Installer to your installation CD so you can then uninstall
||||| Office:
||||| http://support.microsoft.com/?kbid=290301
|||||
||||| Please post all follow-up questions to the newsgroup. Requests
||||| for assistance by email can not be acknowledged.
|||||
||||| ~~~~~~~~~~~~~~~
||||| Beth Melton
||||| Microsoft Office MVP
|||||
||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||| MVP FAQ site: http://mvps.org/
|||||
||||| |||||| I chose "Microsoft Office Professional Plus 2007 (Beta)" from
|||||| Add/Remove -- I don't think there's a way to uninstall just the
|||||| patch, since it replaces the B2 files wholesale.
||||||
|||||| Forgot about the log, but now that I look at it, the key part
|||||| seems to be this section. It's apparently looking for the Beta 2
|||||| files in a
|||||| "D:\WINDOWS\Installer\$PatchCache$\Managed\30120000-0011-0000-0000-0000000FF1CE"
|||||| directory, which isn't there for me. I do still have the B2 CD,
|||||| so it's too bad that it can't draw from that. I'm not sure what
|||||| should go in the directory, however, to get the uninstall to
|||||| work.
||||||
|||||| Catalyst Package Uninstall...
|||||| Package: ProWW
|||||| Package Code: {30120000-0011-0000-0000-0000000FF1CE}
|||||| Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1
|||||| SETUPEXEINSTALLUILANGUAGE=1033
|||||| SETUPINTLDLLDIRECTORY="D:\DOCUME~1\Home\LOCALS~1\Temp\Setup0000044c\"
|||||| Cannot locate any local install source for package
|||||| {30120000-0011-0000-0000-0000000FF1CE}. Original source will be
|||||| required for roll back on uninstall
|||||| MSI(INITIALIZE): '(null)'
|||||| MSI(COMMONDATA): '1: 0 2: 0 3: 1252 '
|||||| MSI(INFO): 'This patch package could not be opened. Verify that
|||||| the patch package exists and that you can access it, or contact
|||||| the application vendor to verify that this is a valid Windows
|||||| Installer patch package.
|||||| D:\WINDOWS\Installer\193596.msi'
|||||| MSI(TERMINATE): '(null)'
|||||| Log level changed from: Standard to: Verbose
|||||| Error: Failed to configure: ErrorCode: 1635(0x663).
||||||
|||||| ||||||| Did you try uninstalling the B2TR patch or did you try
||||||| uninstalling B2? Make sure you are uninstalling B2 rather than
||||||| the patch.
|||||||
||||||| If that's not it then check your error log and see if you can
||||||| determine the cause of the failure.
|||||||
||||||| Please post all follow-up questions to the newsgroup. Requests
||||||| for assistance by email can not be acknowledged.
|||||||
||||||| ~~~~~~~~~~~~~~~
||||||| Beth Melton
||||||| Microsoft Office MVP
|||||||
||||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||||| MVP FAQ site: http://mvps.org/
|||||||
||||||| |||||||| Any advice on what to do if Office 2007 B2TR uninstall fails?
|||||||| About a minute after starting, it just quits and says that the
|||||||| uninstall was not completed.
||||||||
|||||||| I have quite a tidy XP SP2 system, my Temp directory is clear,
|||||||| and I've just rebooted as well.
||||||||
|||||||| What's the next step?
||||||||
|||||||| message ||||||||| No. You need to remove all Office 2007 beta versions before
||||||||| installing 2007 RTM.
 
M

Milly Staples [MVP - Outlook]

Have you checked Patrick Schmid's blogs for this error? I seem to recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Now I understand why you referenced the KB - I skimmed it and must
| have missed the warning at the end. Sorry about that - all of this is
| new territory right now. :)
|
| Actually, I think I picked up on: "Therefore, if you cannot remove
| 2007 Office suites, check the Microsoft Office newsgroups for
| information about how to manually remove 2007 Office suites from the
| computer." and overlooked the warning. (I won't share my thoughts on
| reading the note - but it was definitely a distraction. lol)
|
| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
|
| Prior to the creation of the Windows Installer Cleanup utility I
| experimented with manually deleing the entries. While it worked I
| wasn't sure it would be that easy! What I wasn't considering were the
| other references to the GUID in the Registry. So manual removal can be
| done but all references should be deleted as well - the Windows
| Installer Cleanup utility will remove all of them. So...right now
| that's the only thing I wonder about on removing the references
| manually - that others may have been left behind.
|
| Please post all follow-up questions to the newsgroup. Requests for
| assistance by email can not be acknowledged.
|
| ~~~~~~~~~~~~~~~
| Beth Melton
| Microsoft Office MVP
|
| TechTrax eZine: http://mousetrax.com/techtrax/
| MVP FAQ site: http://mvps.org/
|
| || I was leery of of the collateral damage of using the Cleanup utility,
|| particularly with the warning in the Readme ("NOTE: The Windows
|| Installer Clean Up Utility should not be used to remove the 2007
|| Microsoft Office System installation information), so I tried some
|| last-ditch efforts before resorting to it (my first-ditch efforts are
|| too numerous to mention).
||
|| I noticed that even right-clicking one of the individual MSIs and
|| clicking Uninstall yielded the same "patch package could not be
|| opened...", so that wasn't an option, either.
||
|| Then I found this post:
|| http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3
||
|| The key part of it was this:
|| 1) you might want to try deleting the key:
|| HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid
|| for office 2000}\Patches
||
|| I tested it on the two OneNote instances first to see if it had any
|| effect (OneNote was a separate install), and remarkably, deleting
|| the two 'Patches' branches for OneNote allowed the uninstall to
|| actually get off the ground and work.
||
|| I then did the same for the 10 (or so) remaining 'Patches' entries
|| for the rest of Office, then ran the main uninstall, and that
|| worked, too.
||
|| Remarkable. This may have been much the same thing the Cleanup
|| utility would have done, but at least this way I knew what was
|| happening. There was a little bit of mop-up work to do afterwards,
|| but nothing that significant.
||
|| I truly hope that MS doesn't try one of these massive "Refresh"
|| patches with the next beta, as they've done with the betas for 2003
|| and 2007 (at least). When it works it works, when it doesn't it's a
|| spectacular mess. They should just release a fresh build (as they
|| supplied the press: they could install B2TR fresh), not a patch.
||
|| Thanks
||
|| ||| I'm not 100% certain it will work, since I haven't tried it myself,
||| but all the Windows Installer Cleanup does is zap the installer
||| entries in the Registry - it doesn't remove any application files.
|||
||| In your error log it has: "MSI(INFO): 'This patch package could not
||| be opened" which indicates the issue lies in the Windows Installer
||| entries. Here's another KB if you want to take a look at it as
||| well:
||| http://support.microsoft.com/kb/295823
|||
||| Please post all follow-up questions to the newsgroup. Requests for
||| assistance by email can not be acknowledged.
|||
||| ~~~~~~~~~~~~~~~
||| Beth Melton
||| Microsoft Office MVP
|||
||| TechTrax eZine: http://mousetrax.com/techtrax/
||| MVP FAQ site: http://mvps.org/
|||
||| |||| Is that good to use with Office 2007?
|||| http://support.microsoft.com/default.aspx/kb/923718/en-us
||||
|||| ||||| If I'm not mistaken, if you turn on "Show Updates" then B2TR is
||||| listed separately.
|||||
||||| If the installer files are missing then see if Windows Installer
||||| Cleanup utility works for you. Use it to remove only the
||||| references to the Office 2007 beta version. Once that is complete
||||| then you'll need to reinstall the beta to point the Windows
||||| Installer to your installation CD so you can then uninstall
||||| Office:
||||| http://support.microsoft.com/?kbid=290301
|||||
||||| Please post all follow-up questions to the newsgroup. Requests
||||| for assistance by email can not be acknowledged.
|||||
||||| ~~~~~~~~~~~~~~~
||||| Beth Melton
||||| Microsoft Office MVP
|||||
||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||| MVP FAQ site: http://mvps.org/
|||||
||||| |||||| I chose "Microsoft Office Professional Plus 2007 (Beta)" from
|||||| Add/Remove -- I don't think there's a way to uninstall just the
|||||| patch, since it replaces the B2 files wholesale.
||||||
|||||| Forgot about the log, but now that I look at it, the key part
|||||| seems to be this section. It's apparently looking for the Beta 2
|||||| files in a
|||||| "D:\WINDOWS\Installer\$PatchCache$\Managed\30120000-0011-0000-0000-0000000FF1CE"
|||||| directory, which isn't there for me. I do still have the B2 CD,
|||||| so it's too bad that it can't draw from that. I'm not sure what
|||||| should go in the directory, however, to get the uninstall to
|||||| work.
||||||
|||||| Catalyst Package Uninstall...
|||||| Package: ProWW
|||||| Package Code: {30120000-0011-0000-0000-0000000FF1CE}
|||||| Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1
|||||| SETUPEXEINSTALLUILANGUAGE=1033
|||||| SETUPINTLDLLDIRECTORY="D:\DOCUME~1\Home\LOCALS~1\Temp\Setup0000044c\"
|||||| Cannot locate any local install source for package
|||||| {30120000-0011-0000-0000-0000000FF1CE}. Original source will be
|||||| required for roll back on uninstall
|||||| MSI(INITIALIZE): '(null)'
|||||| MSI(COMMONDATA): '1: 0 2: 0 3: 1252 '
|||||| MSI(INFO): 'This patch package could not be opened. Verify that
|||||| the patch package exists and that you can access it, or contact
|||||| the application vendor to verify that this is a valid Windows
|||||| Installer patch package.
|||||| D:\WINDOWS\Installer\193596.msi'
|||||| MSI(TERMINATE): '(null)'
|||||| Log level changed from: Standard to: Verbose
|||||| Error: Failed to configure: ErrorCode: 1635(0x663).
||||||
|||||| ||||||| Did you try uninstalling the B2TR patch or did you try
||||||| uninstalling B2? Make sure you are uninstalling B2 rather than
||||||| the patch.
|||||||
||||||| If that's not it then check your error log and see if you can
||||||| determine the cause of the failure.
|||||||
||||||| Please post all follow-up questions to the newsgroup. Requests
||||||| for assistance by email can not be acknowledged.
|||||||
||||||| ~~~~~~~~~~~~~~~
||||||| Beth Melton
||||||| Microsoft Office MVP
|||||||
||||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||||| MVP FAQ site: http://mvps.org/
|||||||
||||||| |||||||| Any advice on what to do if Office 2007 B2TR uninstall fails?
|||||||| About a minute after starting, it just quits and says that the
|||||||| uninstall was not completed.
||||||||
|||||||| I have quite a tidy XP SP2 system, my Temp directory is clear,
|||||||| and I've just rebooted as well.
||||||||
|||||||| What's the next step?
||||||||
|||||||| message ||||||||| No. You need to remove all Office 2007 beta versions before
||||||||| installing 2007 RTM.
 
M

Milly Staples [MVP - Outlook]

Have you checked Patrick Schmid's blogs for this error? I seem to recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Now I understand why you referenced the KB - I skimmed it and must
| have missed the warning at the end. Sorry about that - all of this is
| new territory right now. :)
|
| Actually, I think I picked up on: "Therefore, if you cannot remove
| 2007 Office suites, check the Microsoft Office newsgroups for
| information about how to manually remove 2007 Office suites from the
| computer." and overlooked the warning. (I won't share my thoughts on
| reading the note - but it was definitely a distraction. lol)
|
| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
|
| Prior to the creation of the Windows Installer Cleanup utility I
| experimented with manually deleing the entries. While it worked I
| wasn't sure it would be that easy! What I wasn't considering were the
| other references to the GUID in the Registry. So manual removal can be
| done but all references should be deleted as well - the Windows
| Installer Cleanup utility will remove all of them. So...right now
| that's the only thing I wonder about on removing the references
| manually - that others may have been left behind.
|
| Please post all follow-up questions to the newsgroup. Requests for
| assistance by email can not be acknowledged.
|
| ~~~~~~~~~~~~~~~
| Beth Melton
| Microsoft Office MVP
|
| TechTrax eZine: http://mousetrax.com/techtrax/
| MVP FAQ site: http://mvps.org/
|
| || I was leery of of the collateral damage of using the Cleanup utility,
|| particularly with the warning in the Readme ("NOTE: The Windows
|| Installer Clean Up Utility should not be used to remove the 2007
|| Microsoft Office System installation information), so I tried some
|| last-ditch efforts before resorting to it (my first-ditch efforts are
|| too numerous to mention).
||
|| I noticed that even right-clicking one of the individual MSIs and
|| clicking Uninstall yielded the same "patch package could not be
|| opened...", so that wasn't an option, either.
||
|| Then I found this post:
|| http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3
||
|| The key part of it was this:
|| 1) you might want to try deleting the key:
|| HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid
|| for office 2000}\Patches
||
|| I tested it on the two OneNote instances first to see if it had any
|| effect (OneNote was a separate install), and remarkably, deleting
|| the two 'Patches' branches for OneNote allowed the uninstall to
|| actually get off the ground and work.
||
|| I then did the same for the 10 (or so) remaining 'Patches' entries
|| for the rest of Office, then ran the main uninstall, and that
|| worked, too.
||
|| Remarkable. This may have been much the same thing the Cleanup
|| utility would have done, but at least this way I knew what was
|| happening. There was a little bit of mop-up work to do afterwards,
|| but nothing that significant.
||
|| I truly hope that MS doesn't try one of these massive "Refresh"
|| patches with the next beta, as they've done with the betas for 2003
|| and 2007 (at least). When it works it works, when it doesn't it's a
|| spectacular mess. They should just release a fresh build (as they
|| supplied the press: they could install B2TR fresh), not a patch.
||
|| Thanks
||
|| ||| I'm not 100% certain it will work, since I haven't tried it myself,
||| but all the Windows Installer Cleanup does is zap the installer
||| entries in the Registry - it doesn't remove any application files.
|||
||| In your error log it has: "MSI(INFO): 'This patch package could not
||| be opened" which indicates the issue lies in the Windows Installer
||| entries. Here's another KB if you want to take a look at it as
||| well:
||| http://support.microsoft.com/kb/295823
|||
||| Please post all follow-up questions to the newsgroup. Requests for
||| assistance by email can not be acknowledged.
|||
||| ~~~~~~~~~~~~~~~
||| Beth Melton
||| Microsoft Office MVP
|||
||| TechTrax eZine: http://mousetrax.com/techtrax/
||| MVP FAQ site: http://mvps.org/
|||
||| |||| Is that good to use with Office 2007?
|||| http://support.microsoft.com/default.aspx/kb/923718/en-us
||||
|||| ||||| If I'm not mistaken, if you turn on "Show Updates" then B2TR is
||||| listed separately.
|||||
||||| If the installer files are missing then see if Windows Installer
||||| Cleanup utility works for you. Use it to remove only the
||||| references to the Office 2007 beta version. Once that is complete
||||| then you'll need to reinstall the beta to point the Windows
||||| Installer to your installation CD so you can then uninstall
||||| Office:
||||| http://support.microsoft.com/?kbid=290301
|||||
||||| Please post all follow-up questions to the newsgroup. Requests
||||| for assistance by email can not be acknowledged.
|||||
||||| ~~~~~~~~~~~~~~~
||||| Beth Melton
||||| Microsoft Office MVP
|||||
||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||| MVP FAQ site: http://mvps.org/
|||||
||||| |||||| I chose "Microsoft Office Professional Plus 2007 (Beta)" from
|||||| Add/Remove -- I don't think there's a way to uninstall just the
|||||| patch, since it replaces the B2 files wholesale.
||||||
|||||| Forgot about the log, but now that I look at it, the key part
|||||| seems to be this section. It's apparently looking for the Beta 2
|||||| files in a
|||||| "D:\WINDOWS\Installer\$PatchCache$\Managed\30120000-0011-0000-0000-0000000FF1CE"
|||||| directory, which isn't there for me. I do still have the B2 CD,
|||||| so it's too bad that it can't draw from that. I'm not sure what
|||||| should go in the directory, however, to get the uninstall to
|||||| work.
||||||
|||||| Catalyst Package Uninstall...
|||||| Package: ProWW
|||||| Package Code: {30120000-0011-0000-0000-0000000FF1CE}
|||||| Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1
|||||| SETUPEXEINSTALLUILANGUAGE=1033
|||||| SETUPINTLDLLDIRECTORY="D:\DOCUME~1\Home\LOCALS~1\Temp\Setup0000044c\"
|||||| Cannot locate any local install source for package
|||||| {30120000-0011-0000-0000-0000000FF1CE}. Original source will be
|||||| required for roll back on uninstall
|||||| MSI(INITIALIZE): '(null)'
|||||| MSI(COMMONDATA): '1: 0 2: 0 3: 1252 '
|||||| MSI(INFO): 'This patch package could not be opened. Verify that
|||||| the patch package exists and that you can access it, or contact
|||||| the application vendor to verify that this is a valid Windows
|||||| Installer patch package.
|||||| D:\WINDOWS\Installer\193596.msi'
|||||| MSI(TERMINATE): '(null)'
|||||| Log level changed from: Standard to: Verbose
|||||| Error: Failed to configure: ErrorCode: 1635(0x663).
||||||
|||||| ||||||| Did you try uninstalling the B2TR patch or did you try
||||||| uninstalling B2? Make sure you are uninstalling B2 rather than
||||||| the patch.
|||||||
||||||| If that's not it then check your error log and see if you can
||||||| determine the cause of the failure.
|||||||
||||||| Please post all follow-up questions to the newsgroup. Requests
||||||| for assistance by email can not be acknowledged.
|||||||
||||||| ~~~~~~~~~~~~~~~
||||||| Beth Melton
||||||| Microsoft Office MVP
|||||||
||||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||||| MVP FAQ site: http://mvps.org/
|||||||
||||||| |||||||| Any advice on what to do if Office 2007 B2TR uninstall fails?
|||||||| About a minute after starting, it just quits and says that the
|||||||| uninstall was not completed.
||||||||
|||||||| I have quite a tidy XP SP2 system, my Temp directory is clear,
|||||||| and I've just rebooted as well.
||||||||
|||||||| What's the next step?
||||||||
|||||||| message ||||||||| No. You need to remove all Office 2007 beta versions before
||||||||| installing 2007 RTM.
 
M

Milly Staples [MVP - Outlook]

Have you checked Patrick Schmid's blogs for this error? I seem to recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Now I understand why you referenced the KB - I skimmed it and must
| have missed the warning at the end. Sorry about that - all of this is
| new territory right now. :)
|
| Actually, I think I picked up on: "Therefore, if you cannot remove
| 2007 Office suites, check the Microsoft Office newsgroups for
| information about how to manually remove 2007 Office suites from the
| computer." and overlooked the warning. (I won't share my thoughts on
| reading the note - but it was definitely a distraction. lol)
|
| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
|
| Prior to the creation of the Windows Installer Cleanup utility I
| experimented with manually deleing the entries. While it worked I
| wasn't sure it would be that easy! What I wasn't considering were the
| other references to the GUID in the Registry. So manual removal can be
| done but all references should be deleted as well - the Windows
| Installer Cleanup utility will remove all of them. So...right now
| that's the only thing I wonder about on removing the references
| manually - that others may have been left behind.
|
| Please post all follow-up questions to the newsgroup. Requests for
| assistance by email can not be acknowledged.
|
| ~~~~~~~~~~~~~~~
| Beth Melton
| Microsoft Office MVP
|
| TechTrax eZine: http://mousetrax.com/techtrax/
| MVP FAQ site: http://mvps.org/
|
| || I was leery of of the collateral damage of using the Cleanup utility,
|| particularly with the warning in the Readme ("NOTE: The Windows
|| Installer Clean Up Utility should not be used to remove the 2007
|| Microsoft Office System installation information), so I tried some
|| last-ditch efforts before resorting to it (my first-ditch efforts are
|| too numerous to mention).
||
|| I noticed that even right-clicking one of the individual MSIs and
|| clicking Uninstall yielded the same "patch package could not be
|| opened...", so that wasn't an option, either.
||
|| Then I found this post:
|| http://groups.google.com/group/micr...f9db3?lnk=st&q=&rnum=2&hl=en#f23fa4fcd93f9db3
||
|| The key part of it was this:
|| 1) you might want to try deleting the key:
|| HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\{product guid
|| for office 2000}\Patches
||
|| I tested it on the two OneNote instances first to see if it had any
|| effect (OneNote was a separate install), and remarkably, deleting
|| the two 'Patches' branches for OneNote allowed the uninstall to
|| actually get off the ground and work.
||
|| I then did the same for the 10 (or so) remaining 'Patches' entries
|| for the rest of Office, then ran the main uninstall, and that
|| worked, too.
||
|| Remarkable. This may have been much the same thing the Cleanup
|| utility would have done, but at least this way I knew what was
|| happening. There was a little bit of mop-up work to do afterwards,
|| but nothing that significant.
||
|| I truly hope that MS doesn't try one of these massive "Refresh"
|| patches with the next beta, as they've done with the betas for 2003
|| and 2007 (at least). When it works it works, when it doesn't it's a
|| spectacular mess. They should just release a fresh build (as they
|| supplied the press: they could install B2TR fresh), not a patch.
||
|| Thanks
||
|| ||| I'm not 100% certain it will work, since I haven't tried it myself,
||| but all the Windows Installer Cleanup does is zap the installer
||| entries in the Registry - it doesn't remove any application files.
|||
||| In your error log it has: "MSI(INFO): 'This patch package could not
||| be opened" which indicates the issue lies in the Windows Installer
||| entries. Here's another KB if you want to take a look at it as
||| well:
||| http://support.microsoft.com/kb/295823
|||
||| Please post all follow-up questions to the newsgroup. Requests for
||| assistance by email can not be acknowledged.
|||
||| ~~~~~~~~~~~~~~~
||| Beth Melton
||| Microsoft Office MVP
|||
||| TechTrax eZine: http://mousetrax.com/techtrax/
||| MVP FAQ site: http://mvps.org/
|||
||| |||| Is that good to use with Office 2007?
|||| http://support.microsoft.com/default.aspx/kb/923718/en-us
||||
|||| ||||| If I'm not mistaken, if you turn on "Show Updates" then B2TR is
||||| listed separately.
|||||
||||| If the installer files are missing then see if Windows Installer
||||| Cleanup utility works for you. Use it to remove only the
||||| references to the Office 2007 beta version. Once that is complete
||||| then you'll need to reinstall the beta to point the Windows
||||| Installer to your installation CD so you can then uninstall
||||| Office:
||||| http://support.microsoft.com/?kbid=290301
|||||
||||| Please post all follow-up questions to the newsgroup. Requests
||||| for assistance by email can not be acknowledged.
|||||
||||| ~~~~~~~~~~~~~~~
||||| Beth Melton
||||| Microsoft Office MVP
|||||
||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||| MVP FAQ site: http://mvps.org/
|||||
||||| |||||| I chose "Microsoft Office Professional Plus 2007 (Beta)" from
|||||| Add/Remove -- I don't think there's a way to uninstall just the
|||||| patch, since it replaces the B2 files wholesale.
||||||
|||||| Forgot about the log, but now that I look at it, the key part
|||||| seems to be this section. It's apparently looking for the Beta 2
|||||| files in a
|||||| "D:\WINDOWS\Installer\$PatchCache$\Managed\30120000-0011-0000-0000-0000000FF1CE"
|||||| directory, which isn't there for me. I do still have the B2 CD,
|||||| so it's too bad that it can't draw from that. I'm not sure what
|||||| should go in the directory, however, to get the uninstall to
|||||| work.
||||||
|||||| Catalyst Package Uninstall...
|||||| Package: ProWW
|||||| Package Code: {30120000-0011-0000-0000-0000000FF1CE}
|||||| Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1
|||||| SETUPEXEINSTALLUILANGUAGE=1033
|||||| SETUPINTLDLLDIRECTORY="D:\DOCUME~1\Home\LOCALS~1\Temp\Setup0000044c\"
|||||| Cannot locate any local install source for package
|||||| {30120000-0011-0000-0000-0000000FF1CE}. Original source will be
|||||| required for roll back on uninstall
|||||| MSI(INITIALIZE): '(null)'
|||||| MSI(COMMONDATA): '1: 0 2: 0 3: 1252 '
|||||| MSI(INFO): 'This patch package could not be opened. Verify that
|||||| the patch package exists and that you can access it, or contact
|||||| the application vendor to verify that this is a valid Windows
|||||| Installer patch package.
|||||| D:\WINDOWS\Installer\193596.msi'
|||||| MSI(TERMINATE): '(null)'
|||||| Log level changed from: Standard to: Verbose
|||||| Error: Failed to configure: ErrorCode: 1635(0x663).
||||||
|||||| ||||||| Did you try uninstalling the B2TR patch or did you try
||||||| uninstalling B2? Make sure you are uninstalling B2 rather than
||||||| the patch.
|||||||
||||||| If that's not it then check your error log and see if you can
||||||| determine the cause of the failure.
|||||||
||||||| Please post all follow-up questions to the newsgroup. Requests
||||||| for assistance by email can not be acknowledged.
|||||||
||||||| ~~~~~~~~~~~~~~~
||||||| Beth Melton
||||||| Microsoft Office MVP
|||||||
||||||| TechTrax eZine: http://mousetrax.com/techtrax/
||||||| MVP FAQ site: http://mvps.org/
|||||||
||||||| |||||||| Any advice on what to do if Office 2007 B2TR uninstall fails?
|||||||| About a minute after starting, it just quits and says that the
|||||||| uninstall was not completed.
||||||||
|||||||| I have quite a tidy XP SP2 system, my Temp directory is clear,
|||||||| and I've just rebooted as well.
||||||||
|||||||| What's the next step?
||||||||
|||||||| message ||||||||| No. You need to remove all Office 2007 beta versions before
||||||||| installing 2007 RTM.
 
B

Beth Melton

I know the Windows Cleanup Utility was used for similar issues when
trying to get B2TR installed and folks were successful using it which
is why I'm wondering if there are new issues with it for uninstalling
B2TR.

Anyway, I'm hoping if Patrick has something he'll be along to post
it - he's usually good about letting us know when he has something on
his blog. :) (I've yet to master the ability to quickly search a
blog to find what I'm looking for - even with Google and the Google
toolbar to help me. <grin>)

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

"Milly Staples [MVP - Outlook]"
Have you checked Patrick Schmid's blogs for this error? I seem to
recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
 
B

Beth Melton

I know the Windows Cleanup Utility was used for similar issues when
trying to get B2TR installed and folks were successful using it which
is why I'm wondering if there are new issues with it for uninstalling
B2TR.

Anyway, I'm hoping if Patrick has something he'll be along to post
it - he's usually good about letting us know when he has something on
his blog. :) (I've yet to master the ability to quickly search a
blog to find what I'm looking for - even with Google and the Google
toolbar to help me. <grin>)

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

"Milly Staples [MVP - Outlook]"
Have you checked Patrick Schmid's blogs for this error? I seem to
recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
 
B

Beth Melton

I know the Windows Cleanup Utility was used for similar issues when
trying to get B2TR installed and folks were successful using it which
is why I'm wondering if there are new issues with it for uninstalling
B2TR.

Anyway, I'm hoping if Patrick has something he'll be along to post
it - he's usually good about letting us know when he has something on
his blog. :) (I've yet to master the ability to quickly search a
blog to find what I'm looking for - even with Google and the Google
toolbar to help me. <grin>)

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

"Milly Staples [MVP - Outlook]"
Have you checked Patrick Schmid's blogs for this error? I seem to
recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
 
B

Beth Melton

I know the Windows Cleanup Utility was used for similar issues when
trying to get B2TR installed and folks were successful using it which
is why I'm wondering if there are new issues with it for uninstalling
B2TR.

Anyway, I'm hoping if Patrick has something he'll be along to post
it - he's usually good about letting us know when he has something on
his blog. :) (I've yet to master the ability to quickly search a
blog to find what I'm looking for - even with Google and the Google
toolbar to help me. <grin>)

Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

"Milly Staples [MVP - Outlook]"
Have you checked Patrick Schmid's blogs for this error? I seem to
recall that he posted some good info on this.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Beth Melton asked:

| Anyway, I suspect it's due to B2TR getting delivered as a patch and
| the Windows Installer would only remove B2 and the B2TR references
| would remain. I'll have to ask around to make sure for future
| reference, though.
 
J

Jeff

Beth,

From your; or Millies post in this thread; I went there;grabbed that
utility; and it did show some B2TR stuff still lingering about.
So I just highlighted the office stuff and said remove. Seems to have
worked; nothing else crashed!!
And since I heard Office 2007 just got released on Technet this afternoon,
gonna wait to try it; servers are probably really busy.
Just became a subscriber; so I'm waiting my turn.
That utility got stuff the uninstall missed.

Jeff
 
J

Jeff

Beth,

From your; or Millies post in this thread; I went there;grabbed that
utility; and it did show some B2TR stuff still lingering about.
So I just highlighted the office stuff and said remove. Seems to have
worked; nothing else crashed!!
And since I heard Office 2007 just got released on Technet this afternoon,
gonna wait to try it; servers are probably really busy.
Just became a subscriber; so I'm waiting my turn.
That utility got stuff the uninstall missed.

Jeff
 
J

Jeff

Beth,

From your; or Millies post in this thread; I went there;grabbed that
utility; and it did show some B2TR stuff still lingering about.
So I just highlighted the office stuff and said remove. Seems to have
worked; nothing else crashed!!
And since I heard Office 2007 just got released on Technet this afternoon,
gonna wait to try it; servers are probably really busy.
Just became a subscriber; so I'm waiting my turn.
That utility got stuff the uninstall missed.

Jeff
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top