-----Original Message-----
Bill--
There may be issues with Outlook and the Powertoy that developers keep up
with, and people like those at
http://www.mapilab.com/ (thanks Diane for
this link), and then as Diane says, BCM Version The First has its own
collection of issues--and possibly some of those issues may be difficult to
distinguish as to whether they are separate OL or BCM issues. BCM will
proably be more stable if MSFT throws support to it in the future, and I
guess gets enough feedback that it has marketing legs or demand.
But I wonder if you are still having bugs with Outlook or with BCM without
the PT (as I understand when you fire up Outlook you are getting that
"Operation failed error"), and I don't know how often or how annoying the
Outlook hang issue is.
1) I wonder if you can help yourself with running Detect and Repair for
Office from any Office app's Help or Add/Remove.
2)You also have the option of course to go to Add/Remove and run a repair
install of Office.
Differences Between Repair and Reinstall
http://support.microsoft.com/default.aspx?scid=kb;EN- US;298027
3) Have you used the Windows Installer Cleanup Utility?
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en- us;290301
My idea is that if you are willing to use it for One Note and Office, then
go to Add/Remove and uninstall Office, One Note and One Note SP1 and
reinstall them, that will get rid of this. You may not want to do this and
I understand that. Here's the context for the WICU- which is a more user
friendly gui version of MSIZap that zaps installer registry info to repair
some corrupted install information. Using this tool and uninstalling
reinstalling Office and One Note and One Note SP1 might square things away
for you. I am pasting an a description of this from Sloan Crayton [MS]
"I think I can clarify the use of the Windows Installer Cleanup Utility a
bit. 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.
Sloan Crayton
Microsoft
_________________________________________________________ __________
Chad,
Thank again for the info. I checked, and all these
services are running, and the only error event showing is
for the hang in Outlook when the pop up alert (The
operation failed") appears:
Hanging application OUTLOOK.EXE, version 11.0.6353.0,
hang module hungapp, version 0.0.0.0, hang address
0x00000000.
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 4f 55 54 4c 4f 4f OUTLOO
0018: 4b 2e 45 58 45 20 31 31 K.EXE 11
0020: 2e 30 2e 36 33 35 33 2e .0.6353.
0028: 30 20 69 6e 20 68 75 6e 0 in hun
0030: 67 61 70 70 20 30 2e 30 gapp 0.0
0038: 2e 30 2e 30 20 61 74 20 .0.0 at
0040: 6f 66 66 73 65 74 20 30 offset 0
0048: 30 30 30 30 30 30 30 0000000
Thanks especially for the path to SP1 for BCM. I've been
looking all over for it.
Cheers,
Bill probably
been altered, but box
and typing in 00
/security/winxpsp2faq.asp __
__
.