Service Control Manager Event 7024 (2270) (
Download Repair Tools and Fix it Instantly)
Feb-16-2010
Don't Worry - I'm here to help you fix it!
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 PC 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 was the PC name. Therefore, Messenger always expects to be able to add the PC name, during the startup process, as an alias to listen to. If the name already exists on the network (because it was added on another computer), Messenger was unsuccessful on adding that name, and does not start.
Common Symptoms
During the startup process, you may see the bellowing unrecoverable error message:At least 1 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. the is described as: "The Messenger service terminated to service-specific unrecoverable error 2270." Further instructions was available by using the net helpmsg command. unrecoverable error symptoms 2270 was described as:The PC name could not be added as a symptoms alias. The name may already exist on the network.
To Fix the problem you need to follow the steps below:
Step 1:
Download & Install RegistryEasy for Free.
Note:If the download link doesn't work you may need to Download it Directly from RegistryEasy Site Here
Step 2:
Click the "Scan" button.
Step 3:
Click the 'Fix Errors' Button to Repair Your PC!
Scott Johnson Feb 16,2010
For Experts Only
Cause of the Problem
the behavior occurs at the computer's name was not unique on the network. Sometimes a PC will be given a name that was 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 PC 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 was the PC name. Therefore, Messenger always expects to be able to add the PC name, during the startup process, as an alias to listen to. If the name already exists on the network (because it was added on another computer), Messenger was unsuccessful on adding that name, and does not start.
Resolution method 1
Rename the PC to a unique name by using the Network tool in Control Panel. The next time you start the computer, the unrecoverable error symptoms should not appear.More Information
If you are running MS Win for Workgroups version 3.11 and you are running Winpopup.exe, and if you are logged on to the same logon name, the same unrecoverable error symptoms occurs. Winpopup uses the logon name and does not let the Win NT Messenger service start.Releated Articles:
- MS-DOS Err Msg: DoubleSpace Has Used All the Memory...
- PRJ: Unwanted Blank Tasks Printed in Task View
- WFWG Err Msg: STOP! You Must Type a Full Path Including...
- PC Win DOS: Windows and MS-DOS Client Folders
- DOCERR: How CN_RECEIVE Events Are Generated
- Command Prompt Does Not Reflect Code Page Change
- Configuring COM1 and COM2 via Control Panel
- Display Problems in Mouse Demo with 640x480 256-Color Drivers
- Mac Srv: Mail Data File Compression Is Lowest Priority
- Windows/MS-DOS for PS/2 Not Supported on IBM ValuePoint
Saved me times.thanks..
It can scan and repair your computer fast! Many thanks!
And about the RegistryEasy program, using vista I've had some problems with Vista taking up to much space and memory usage. I had task managers up before and after using this program looking at my CPU usage and memory. My CPU usage went from a constant 13% to 3% and my memory went from 1.43GB to 1.13GB. This program checks more things then most system clean ups and gives a resuly 10x more effective then optimizing my computer.
*RegEasy Will Repair Errors on Your PC