Service Control Manager Event 7024 (2270)Last reviewed: November 5, 1997Article ID: Q101355 |
The information in this article applies to:
SYMPTOMSDuring boot, the following message is displayed in a dialog box:
At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.Event Viewer shows a Service Control Manager event number 7024. This is explained as: "The Messenger service terminated with service- specific error 2270." Further information can be obtained by using the NET HELPMSG command. Error message 2270 is explained by the following:
The computer name could not be added as a message alias. The name may already exist on the network.If you are running Microsoft Windows for Workgroups version 3.11 and running WINPOPUP.EXE, and if you are logged in with the same login name, the same error occurs. WinPopUp uses the login name and does not let the Windows NT messenger service start.
CAUSEThis occurs when the name given to the computer is not unique on the network. Sometimes a computer will be given a name that is also a user name. The messenger functions by listening to the network for messages 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 added via the NET NAME command. If there are no users logged on, the only alias that messenger can listen to is the computer name. Therefore, the messenger always expects to be able to add the computer name, during startup, as an alias to listen to. If this name already exists on the network (because it was added on another machine), the messenger is unsuccessful in adding that name, and fails to start.
RESOLUTIONRename the computer to a unique name by choosing the Network icon in Control Panel. The next time you start Windows NT, the error message should not appear.
|
Additional query words: wfw wfwg prodnt
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |