Kdservice Failed To Start
Paul
I have installed several other custom .Net windows services successfully. A new one I had recently written was very similar to the others and while it installed without error - on starting it with the service controller it failed to start with the error dialog: System error 2 ... system cannot find the file specified.
After time and consternation, the only thing I could think of that was significantly different about this service was that the path and executable name were at least 10 characters longer than any of my other services. On shortening both the path and .exe name and re-installing, the service ran fine: no error! I can only assume my previous path or service or .exe name was too long.
Also, It would be pertinent to mention I had used some borrowed "service driver" code built in to my exe to handle the install/uninstall of the service to the service controller via win API calls. It could be a character limit was hidden within that service driver module.
I could not find any windows related docs to confirm if there is a system bound character limit to a path or service name that I had exceeded. I will dig in to the service driver when time permits and see if that turns out to be the problem. Meanwhile I welcome any insights.
In my case, the problem was caused by a mistake in the service start routine. DriverEntry (in my case it was a kernel-mode driver) returns a bad status value. I think this situation applies to user mode too.
Another possible reason that the sys file is blocked. If your driver doesn't exit clearly (for example, you forget to clean up Device, Callouts etc), the sys file may be blocked. To check that you can try removing sys file when service is not working. Normally you should be able to do so. If not, the driver may hold some resources and in turn blocks the sys file.
If your service indeed blocks the file, you should set the service start to Manual (check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\YourServiceName\Start flag: 0 - start on boot, 3 - manual) and restart your device. This will free up the sys file and you can try again until you fix your clean-up flow.
Well, there is a path limit but not sure the char limit at this movement.Also the the file name should match exe name.sc create MyWinService BinPath=C:\System32\Queue\MyWinService.exe
We recently replaced the rear drum of the HP CDK Laser Station M605 printer. Since then, we have been encountering the error message 59.05.50, despite all diagnostic tests showing no issues. Why is this error message appearing?
This error is a drum motor startup error. That means either the motor has failed or the cartridge is defective and the motor cannot rotate it. Try a different cartridge. If you get the same error you will need to replace M102 motor.
Thank you for your prompt response. I replaced the cartridge, but I'm still experiencing the same issue. So it seems to be a problem with the motor drum not spinning, although the drum itself is also new, I replaced it recently! It may be a more serious issue. I've seen some videos on YouTube showing a problem with the printer's motherboard!?
Can you clarify what you replaced? The drum on this printer is part of the toner cartridge and that is the error you are getting. From your reference to replacing drum at the back, that would be the fuser and is not related to this error. It is the toner cartridge drive motor.
Indeed, you were absolutely right. I replaced the rear drum, so the fuser unit is not the cause of the problem. Then, I tried with another cartridge, but I still have the same error message 59.05.50, along with another message saying "maintenance kit". Apparently, the issue is not with the cartridge, so I am a bit lost!
No the issue is likley the cartridge drive motor. If you have replaced the fuser you can reset the maintenance count, it is not automatic on this model. But that will have no affect on the other issue. I suggest you go into troubleshooting and test the drum motor.
Error code 59.05.50 on the HP CDK Laser Station M605 printer indicates a problem with the drum motor assembly or the drum itself. Check for proper installation, inspect for damage, update firmware if needed, and ensure no electrical issues. If problems persist, contact HP support.
thank you for all your responses. However, I have no idea how to reset the maintenance counter, as you say it's not automatic on this model. Also, how should I proceed with troubleshooting the motor drum and testing it? I am a programming engineer with no training in printer repair.
The Windows Internet Name Service (WINS) service failed to start due to the
following error:
The system cannot find the file specified. any help on finding the file or entering the correct path Thanks
Kooch
This problem is a result of a restore that I had to do. I am having several
errors that I am trying to deal with some I have fixed and some still working
on. To make things worse I am trying to fix this remotely and will not be
back for 3 weeks. Answers to your question
I can NOT start WINS manully, all dependences are started , It is selected
to start on the local machine, error occurs on boot up
This particular error has the following text form event log.
I am getting another error in file replication service that might be related.
Source is NtFrs Event Id is 13559 with following text.The File Replication Service has detected that the replica root path has
changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If
this is an intentional move then a file with the name
NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Changing the replica root path is a two step process which is triggered by
the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. Hope this helps you outThanks Kooch
Thanks for your update.We can check service configuration file in the folder
%windowsroot%\system32\drivers\etc as following: 1.Open Notepad on the SBS server.
2.Open the file %windowsroot%\system32\drivers\etc\services.
3.Check whether the following items are listed. If not, please manually
add them:nameserver 42/tcp name #Host Name Server
nameserver 42/udp name #Host Name Server4.Save the change and reboot the server.After that, please verify whether the issue has been resolved.In case, the issue still persists after using steps above, I suggest
reinstall TCP/IP on the problematic server. For the detailed steps, you can
refer to the following Microsoft Knowledge Base article:How to remove and reinstall TCP/IP on a Windows Server 2003 domain
controller
=kb;en-us;325356 Regarding the NTFRS 13559 event, based on my research, this issue might be
related the movement of the Sysvol folder. Under one of the following
circumstance the issue will occur:
- Sysvol folder has been moved and then has been moved back to the original
location
- The Sysvol folder has been restored from a backup.
To resolve the issue, I would like to suggest the following:
1.Click Start, click Run, type explorer, and then click OK.
2.Locate the root folder of the CurrentLocation folder, where
CurrentLocation is the path that is specified in the Event Viewer
description.
3.Right-click a blank area in the root folder of the CurrentLocation
folder, point to New, and then click Text Document.
4.For the file name of the new text document, type the following, and then
press ENTER:NTFRS_CMD_FILE_MOVE_ROOT 5.You may receive the following message:If you change a filename extension, the file may become unusable. Are you
sure you want to change it?
If you do receive this message, click Yes to save the file without a file
name extension.
After that, please verify whether the issue has been resolved. For more
information, you can refer to the following Microsoft Knowledge Base
article:
Event ID 13559 may be logged in Event Viewer in Windows 2000
=887440Hope it helps and I look forward to hearing from you.Best regards,Crina Li (MSFT)
From: "=?Utf-8?B?S29vY2g=?=" Subject: RE: Event ID 7000 WINS failed to start The system cannot find the
Date: Thu, 19 Jan 2006 22:06:02 -0800
Newsgroups: microsoft.public.windows.server.sbs
Thanks for the info your suggestion fixed the problem Regarding the NTFRS
13559 event.The wins problem I checked the file that you suggested and it has what it
should, I then looked at the reinstall tcp/ip process, I am not having any of
the symptoms with ipconfig that it talked about and don't think that this is
the problem plus I am doing this all remotely and don't wnat to run the risk
of making things worse until I get there so am electing to not do this right
now.
I am getting another error that may or may not be related which is:event id 40960 source LSASRV1. The Security System detected an authentication error for the server
DNS/MBC1.MitchellBerean.local. The failure code from authentication protocol
Kerberos was "The attempted logon is invalid. This is either due to a bad
username or authentication information.
(0xc000006d)".Followed by event id 40961 source LSASRV2. The Security System could not establish a secured connection with the
server DNS/MBC1.MitchellBerean.local. No authentication protocol was
available.Any suggestions
Thanks for your update.For Windows Internet Name Service (WINS) service issue, please try to
reinstall Wins component to see if the problem still occurs:1.Open Control Panel and then click Add or Remove Programs.
2.Click Add/Remove Windows Components.
3.Select Networking Services and then click Details.
4.Check the Windows Internet Name Services(WINS) and then click OK. [Note:
if the check box has been selected, please uncheck it to remove the
component and then reinstall it]Regarding the event LSASRV 40960 and 40961appear on SBS, as I know, this
issue can occur when you restart the SBS 2003 server. A service, for
example, the Windows Time service (W32Time), tries to authenticate before
Directory Services has started. You can just safely ignore the event as it
will not cause any adverse effects to the server. For more information, see:823712 Event IDs 40960 and 40961 in the System Event Log When You Restart
=823712824217 LSASRV Event IDs 40960 and 40961 When You Promote a Server to a
Domain
=824217I would suggest you reboot the server again and see if the event does not
appear. type the following commands:1. Net Stop NETLOGON
2. IPCONFIG /FLUSHDNS
3. IPCONFIG /REGISTERDNS
4. Net Start NetlogonThe issue could also be a similar to the problem described in the following
KB article:826819 The Server Stops Responding and an Access Violation Occurs in
Lsass.exe
=826819I am appreciated your time and look forward to hearing from you.Best regards,Crina Li (MSFT)