Printable View
I stopped our messenger service on our new Windows 2000 Advanced server and now can't get it started again. I've rebooted the server twice mid-day and then immediately tried to restart it - I get a 1053 error stating that it could not restart it in a timely fashion or something like that.
http://www.computing.net/windowsxp/w...rum/75622.html maybe this can help ya ..if not ..tell us
Well - that didn't really help - i've tried some of that stuff - but they don't talk about the error I'm getting -
I'm getting a message that says that it cannot start the messenger service - error 1053 - the service did not respond in a timely fashion. I had originally turned it to manual start - and have tried getting it back to automatic - but when I change it to automatic on the properties and click Apply - it locks up the services menu and I have to ctrl alt delete and end the task to get it to go away....its very strange...
You don't have Exchange on there by any chance do you?
One thing you can do is boot to the recovery console and change it to automatic using the CLI. Works every time ;)
If you need step by step instructions, let me know.
Nope - no exchange on it at all - just a few bank programs....and a backup program - vertias to be exact - and that won't start becuase it requires the messenger service to be running - which I can't get to restarat - hence the whole dilemna....
This might be your issue: http://support.microsoft.com/default...b;en-us;278712
Actually tried that exact thing earlier - searching MS help - came across that exact article without any help.
Is it logging anything in the event log? If so, what is the source?
It's actually not logging anything except for something about a printer not being able to be installed - which was a problem from yesterday - but its logging something about that today - think that is related?
No but it is easier to search http://www.eventid.net with a source.Quote:
Originally posted here by elrey103
It's actually not logging anything except for something about a printer not being able to be installed - which was a problem from yesterday - but its logging something about that today - think that is related?
I would try thehorse's suggestion. I cannot find anything else relating to the topic.
Thanks for the tip - I've heard a lot about Lan guard lately - but that doesn't help my problem...haha.
Try booting from the install CD and go into the recovery console and set the service to automatic using the CLI. Then, when the server boots, go ahead and post the event log entries so we can get a closer look. Clean em up for anonymity if you have to.
Not sure what you mean by that - I'd need a little bit more detailed instruction - plus that would mean a trip to that branch - to put the CD in - I'm remoting into it....
Yes, you'd have to boot from the install cd and choose recovery console. Once you get into the console, you'll have to enter some commands to get it to start automatically.
Here is some info on the Recovery Console(taken from the MS Website)
The Recovery Console is a text-mode command interpreter that is separate from the Windows 2000 command prompt and allows the system administrator to gain access to the hard disk of a computer running Windows 2000, regardless of the file format used, for basic troubleshooting and system maintenance. Since starting Windows 2000 is not a prerequisite for using the Recovery Console, it can help you recover when your Windows 2000–based computer does not start properly or at all. The Recovery Console allows you to obtain limited access to NTFS, file allocation table (FAT), (FAT16 and FAT32) volumes without starting the graphical interface. The Recovery Console allows administrators and Microsoft Product Support Services technicians to start and stop services, and repair the system in a very granular way. It can also be used to repair the master boot record (MBR) and boot sector and to format volumes. The Recovery Console prevents unauthorized access to volumes by requiring the user to enter the system administrator password.
To start the Recovery Console, start the computer from the Windows 2000 Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup floppy disks and your computer cannot start from the Windows 2000 Setup CD, use another Windows 2000–based computer to create the Setup floppy disks. For more information about creating the Windows 2000 Setup floppy disks, see “Planning a Reliable Configuration” in this book or Windows 2000 Server Help.
If the Recovery Console was installed on the local hard disk, it can also be accessed from the Windows 2000 startup menu. However, if the MBR or the system volume boot sector has been damaged, you need to start the computer using either the Windows 2000 Setup floppy disks or the Windows 2000 Setup CD to access the Recovery Console.
To add the Recovery Console to existing installations of Windows 2000, on the Start menu, click Run, and then type:
F:\I386\Winnt32.exe /cmdcons
where F is the CD-ROM drive letter.
This installation requires approximately 7 megabytes (MB) of disk space on your system partition.
This is the command you are interested in:
enable Enables a Windows system service or driver.
enable servicename [start_type]
servicename Name of the service or driver to be enabled.
start_type How the service or driver is scheduled to be
started. Valid start-type values are:
SERVICE_BOOT_START
SERVICE_SYSTEM_START
SERVICE_AUTO_START
SERVICE_DEMAND_START
Enable prints the old start_type of the service before resetting it to the new value. Note the old value, in case it is necessary to restore the start_type of the service. If you do not specify a new start_type, enable prints the old start_type.
Hope this helps.
Were you referring to my post? Eventid.net is where you go to search for descriptions of errors in your event log. Not a site for Languard, although they do run ads for them all the time.Quote:
Originally posted here by elrey103
Thanks for the tip - I've heard a lot about Lan guard lately - but that doesn't help my problem...haha.
I thought Event ID was a place where you post your Event ID errors and others repsond to try and help resolve them. Am I wrong? Out of the loop? Just plain insane?
:)
Clearly insane. ;) j/k You are correct, but I mainly use it when I cannot find information about a certain error that one of my servers is reporting.Quote:
Originally posted here by thehorse13
I thought Event ID was a place where you post your Event ID errors and others repsond to try and help resolve them. Am I wrong? Out of the loop? Just plain insane?
:)
Have you tried (from the command prompt):
net start messenger
I had some similar problems with a few other services (including the cryptographic service and a few others). Try it... see if you get the same error.
AJ