R
Rose
I'm not sure if this is a network_web issue but I do have a home network for
a laptop linked to the desktop. Laptop does not go on web.
My event log is listing this sequence.
TCPIP starts up (successful event)
1 minute later the DCOM error is listed with the red X
This service cannot be started-disabled or no enabled devices
associated-attempting to start IMAPI Service with arguement"-Service" in
order to run service 520CCA63-51A3-11D3-9144-001090AHC5E
After that is Event 7023
Human Interface Device Access service terminated module could not be found
The Human Interface Device thing has existed since the computer arrived a
year ago. Eventually I disabled it in services but this record continues to
show. This DCOM error listing has started since September. The pattern on
the event list appears to be in conjunction with the dial up connection.
There are no crashes or operational problems but the dial up requires 2 or 3
tries and often is disconnected soon after a connection has been
established. This started before the 2 October sessions of critical updates.
I had assumed it to be at the server end since the message will be 'no
answer at the other end in a timely fashion' or various other obscure
messages including NoCarrier in the log and then it finally connects after 5
minutes of this routine.
A firewall exists, antivirus (up to date)and pest patrol in place. I did the
test at Shields up and all ports were closed. My Server provides anti spam
and virus filter which works effectively-no stuff arriving here such as the
attachment mail. All scans result in no 'invaders' present.
The intellipoint mouse software kept attempting to connect to the internet
(point.exe ?) I disabled it out of the start up but never could find exactly
where that command was coming from. The mouse software is up to date for Xp.
I see I have had the IMAPI service disabled and I just turned it to manual.
There has been no problem burning cds or using the Nero Incd in the past
year.
Is it a coincidence that the DCOM error shows up just after the TCP starts
up? Why would the 'drag and drop' Cd burn capability service have a problem
with the connection to the internet?
a laptop linked to the desktop. Laptop does not go on web.
My event log is listing this sequence.
TCPIP starts up (successful event)
1 minute later the DCOM error is listed with the red X
This service cannot be started-disabled or no enabled devices
associated-attempting to start IMAPI Service with arguement"-Service" in
order to run service 520CCA63-51A3-11D3-9144-001090AHC5E
After that is Event 7023
Human Interface Device Access service terminated module could not be found
The Human Interface Device thing has existed since the computer arrived a
year ago. Eventually I disabled it in services but this record continues to
show. This DCOM error listing has started since September. The pattern on
the event list appears to be in conjunction with the dial up connection.
There are no crashes or operational problems but the dial up requires 2 or 3
tries and often is disconnected soon after a connection has been
established. This started before the 2 October sessions of critical updates.
I had assumed it to be at the server end since the message will be 'no
answer at the other end in a timely fashion' or various other obscure
messages including NoCarrier in the log and then it finally connects after 5
minutes of this routine.
A firewall exists, antivirus (up to date)and pest patrol in place. I did the
test at Shields up and all ports were closed. My Server provides anti spam
and virus filter which works effectively-no stuff arriving here such as the
attachment mail. All scans result in no 'invaders' present.
The intellipoint mouse software kept attempting to connect to the internet
(point.exe ?) I disabled it out of the start up but never could find exactly
where that command was coming from. The mouse software is up to date for Xp.
I see I have had the IMAPI service disabled and I just turned it to manual.
There has been no problem burning cds or using the Nero Incd in the past
year.
Is it a coincidence that the DCOM error shows up just after the TCP starts
up? Why would the 'drag and drop' Cd burn capability service have a problem
with the connection to the internet?