Cannot start Intersite Message Service

[Guest]

I have a Windows 2000 Active Directory Domain Controller. This server is
running Service Pack 2 and the client does not want to upgrade to the latest
service pack. The Intersite Message service will not start. In the System
Event Log there is an event logged with the ID of 7023. The text reads "The
Intersite Messaging Service terminated with the following error: A device
attached to the system is not functioning." Upon trying to start the service
manually I receive the error "Could not start the Intersite Messaging service
on Local Computer. Error 31: A device attached to the system is not
functioning." I cannot find any devices that are not functioning correctly.
I tried running dcdiag and all it tells me is that the service is stopped.
(No Kidding, as if I didn't know that). I cannot find any info leading me
anywhere on this problem. Does anyone out there have any ideas?

 

[Ace Fekay [MVP]]

In

I have a Windows 2000 Active Directory Domain Controller. This
server is running Service Pack 2 and the client does not want to
upgrade to the latest service pack. The Intersite Message service
will not start. In the System Event Log there is an event logged
with the ID of 7023. The text reads "The Intersite Messaging Service
terminated with the following error: A device attached to the system
is not functioning." Upon trying to start the service manually I
receive the error "Could not start the Intersite Messaging service on
Local Computer. Error 31: A device attached to the system is not
functioning." I cannot find any devices that are not functioning
correctly. I tried running dcdiag and all it tells me is that the
service is stopped. (No Kidding, as if I didn't know that). I cannot
find any info leading me anywhere on this problem. Does anyone out
there have any ideas?

SP2? Hmm. There's been alot of updates for vulnerabilities and functionality
fixes in the past 3 years.

Anyway, is there any other errors in the Event logs such as with AD, DNS,
FRS, Netlogon, etc? Is their machine only using the internal DNS in it's IP
properties (not an ISP's)?

Here's a link on that error, but it doesn't seem to be much help.
http://www.eventid.net/display.asp?eventid=7023&eventno=345&source=Service Control Manager&phase=1

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Ace Fekay [MVP]]

In

Ace,

Thanks for the info. I finally talked the customer into upgrading
to Service Pack 4. Upon applying Service Pack 4 the problem was
resolved. Thanks for your reply.

Jarrod

Good job in talking your customer into it!




Ace