Service Control Manager Event 7024 (2270) (101355)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Advanced Server 3.5
- Microsoft Windows NT Advanced Server 3.51
- Microsoft Windows NT Advanced Server 4.0
- Microsoft Windows NT Server 3.1
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q101355 For a Microsoft Windows XP version of this article, see 314094.
SYMPTOMS
During the startup process, you may see the following error message:
At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
Event Viewer shows Service Control Manager event number 7024. This is
described as: "The Messenger service terminated with service-specific
error 2270."
Further information is available by using the net helpmsg command. Error message 2270 is described as:
The computer name could not be added as a message alias. The name may already exist on the network.
CAUSE
This behavior occurs when the computer's name is not unique on the
network. Sometimes a computer will be given a name that is also a user
name.
The Messenger service functions by listening to the network for messages that are directed to a set of aliases. The list of aliases consists of the computer name, the user name of the current user, and any aliases that are added by using the net name command. If there are no users logged on, the only alias that Messenger can listen to is the computer name. Therefore, Messenger always expects to be able to add the computer name, during the startup process, as an alias to listen to. If this name already exists on the network (because it was added on another
computer), Messenger is unsuccessful in adding that name, and does not
start.
RESOLUTION
Rename the computer to a unique name by using the Network tool in
Control Panel. The next time you start the computer, the error message should not appear.
MORE INFORMATION
If you are running Microsoft Windows for Workgroups version 3.11 and
you are running Winpopup.exe, and if you are logged on with the same logon name, the same error message occurs. Winpopup uses the logon name and does not let the Windows NT Messenger service start.
| Modification Type: | Major | Last Reviewed: | 5/6/2003 |
|---|
| Keywords: | kbnetwork kbprb KB101355 |
|---|
|