R
rwsjr
I had a persistent problem with this error which caused my computer to boot
up very slowly.
None of the suggestions in this McAfee forum or the intervention of a McAfee
Technician solved the problem.
I thought there might be a conflict between mcagent.exe and the Kontiki
program kservice because the same error message occured with both programs.
However I recently discovered, inadvertently, that the problem is related to
the way a Windows XP user logs on.
When I was logging on automatically through the Windows Welcome sreen, the
problem always occurred.
When I changed the way I logged on to disable the Welcome screen, which
required me to enter a user name and/or password, the problem completely
disappeared and the time to log in was cut in half. Mcagent and Kservice
loaded immediately.
Thus, the DCOM error appears to be connected to the Windows logon process.
Anyone having this problem might try logging in by disabling the automatic
Welcome screen process and entering their account name.
I am the only user on my computer, so I cannot say if this solution will
apply to systems with multiple users. I suspect forcing all users to log on
with their user names and/or passwords may help.
up very slowly.
None of the suggestions in this McAfee forum or the intervention of a McAfee
Technician solved the problem.
I thought there might be a conflict between mcagent.exe and the Kontiki
program kservice because the same error message occured with both programs.
However I recently discovered, inadvertently, that the problem is related to
the way a Windows XP user logs on.
When I was logging on automatically through the Windows Welcome sreen, the
problem always occurred.
When I changed the way I logged on to disable the Welcome screen, which
required me to enter a user name and/or password, the problem completely
disappeared and the time to log in was cut in half. Mcagent and Kservice
loaded immediately.
Thus, the DCOM error appears to be connected to the Windows logon process.
Anyone having this problem might try logging in by disabling the automatic
Welcome screen process and entering their account name.
I am the only user on my computer, so I cannot say if this solution will
apply to systems with multiple users. I suspect forcing all users to log on
with their user names and/or passwords may help.