Drew Moreland
07-09-2005, 09:17 PM
I have recently begun to receive warnings in my applications event log that
I do not understand. They always come in pairs, Event ID #1001 and #1004,
and they always occur three times in rapid succession, but seem to have no
apparent effect on my system.
The "properties" dialog box for #1001 reads: "Detection of product
'{43DCF766-6838-4F9A-8C91-D92DA586DFA7}' feature 'DefaultFeature' failed
during request for component '{A4AD656D-72E9-43A7-9DDO-E5F6AF438E72}' "
The "properties" dialog box for #1004 reads: "Detection of product
'{43DCF766-6838-4F9A-8C91-D92DA586DFA7}' feature 'DefaultFeature', component
'{9747ECA8-A740-EC80-1AE2-C48048D83AA4}' failed. The resource
'HKEY_CURRENT_USER\Software\Microsoft\JournalViewer' does not exist. "
I have located the folder named "Journal Viewer" in C:\\Program Files
although I have never knowingly used it. I do not know what actions I take
that causes these warnings to appear as they do not appear every day.
Is this a matter that needs correction (and if so, how?), or can I simply
allow Windows to continue to complain about this without resolution.
--
'Drew Moreland
I do not understand. They always come in pairs, Event ID #1001 and #1004,
and they always occur three times in rapid succession, but seem to have no
apparent effect on my system.
The "properties" dialog box for #1001 reads: "Detection of product
'{43DCF766-6838-4F9A-8C91-D92DA586DFA7}' feature 'DefaultFeature' failed
during request for component '{A4AD656D-72E9-43A7-9DDO-E5F6AF438E72}' "
The "properties" dialog box for #1004 reads: "Detection of product
'{43DCF766-6838-4F9A-8C91-D92DA586DFA7}' feature 'DefaultFeature', component
'{9747ECA8-A740-EC80-1AE2-C48048D83AA4}' failed. The resource
'HKEY_CURRENT_USER\Software\Microsoft\JournalViewer' does not exist. "
I have located the folder named "Journal Viewer" in C:\\Program Files
although I have never knowingly used it. I do not know what actions I take
that causes these warnings to appear as they do not appear every day.
Is this a matter that needs correction (and if so, how?), or can I simply
allow Windows to continue to complain about this without resolution.
--
'Drew Moreland