I recently removed every Nokia PC Suite item from my computer, as the programme, following an update, failed to connect to my Nokia 'phones. Reinstalled, the programme now works fine for the telephones and sychronising with Outlook.
However, it is producing a quantity of errors in Windows Search, as seen in Event Viewer under Applications, when Outlook is booting up or running. The error message reads as follows:
"The protocol handler MDatastorePH.MDatastoreProtocol.1 cannot be loaded. Error description: Class not registered." This occurs within the category Gatherer.
The handler in question can be found in the registry here:
I have tried deleting the whole Nokia key, including in Safe Mode, but cannot (I use Search ONLY for Outlook, nothing else). I have tried setting the "Included" and "ExtExclusionsUsed" values to zero. No effect. I have tried booting up the comp (XP, SP3, home) with all available services enabled. Nix.
The error first appears one or two seconds before Outlook's starting-up is acknowledged by Events, and then repeats a few minutes later. The errors then continue at intervals of half-an-hour or so (it varies). Within Protocols exist also Outlook, Outlook Express, IE8 History and a few others - all with the same types of value settings. I presume Nokia is there, also, to enable Search if required to catalogue Nokia items not viewable conventionally in the computer's main filing system. However, frankly, I don't know.
The functioning of Search, which only catalogues Outlook as stated, does not appear to be impaired by these errors. However, I have had a series of difficulties with Nokia on this comp these last several years (misbehaving drivers, etc.), so prefer either to have nothing installed from them or, if it must be, at least working correctly.
A solution may be to unravel the Registry's indecipherable child/parent settings so that I can do what I will with the key. So far, any changes I have made have been thrown back to default, either immediately or after an interval (including an interval after a reboot).
Any ideas will be warmly appreciated!