• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2230
  • Last Modified:

DFS Error 1075 - cannot start service

Error 1075
I get the above message when trying to start the service.

I have checked the dependancies and all 4 are started and the 2 drivers are in the system32/drivers folder.

I dont really want to uninstal and reinstal the role as I have quite a few active shares on it.

Im not sure what the maked for deletion part may be.
0
BHeshka
Asked:
BHeshka
  • 3
  • 3
2 Solutions
 
Ayman BakrSenior ConsultantCommented:
Try first to go to services.msc > locate Windows Management Instrumentation extension Driver change it to automatic and start it. Then check if your DFS Namespace service would start. If still it doesn't start then return everything as it was and do the following:

1. Backup your registry in case things go wrong, so you can restore the original settings.
2. Open registry and browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DFS Namespace
3. Locate the entry DependOnService
4. Delete that entry
5. You might require to restart the server
0
 
BHeshkaAuthor Commented:
Mutawadi thanks for the response.

I located Windows Management Instrumentation (did not see "extension driver") and it was already started.

I have backedup and deleted the Depend on Service reg key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DFS (did not see the "Namespace" part)

I have not yet restarted.  Will do later in day. Tried starting service (without restart) and same issue.

Ill see what happens after I restart
0
 
BHeshkaAuthor Commented:
Mutawadi, I spotted this error in event viewer.
Error 7003. The DFS Namespace service depends the following service: Active Directory Domain Services. This service might not be installed.

I removed the ADDS portion from the Depend on Service key.  I can now start the service but have to do it manually although it is set to delayed startup.

Any idea why this would cause issues even with ADDS running with no errors
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Ayman BakrSenior ConsultantCommented:
With Event ID Microsoft suffices with a resolution to remove the dependancy service as you did: http://technet.microsoft.com/en-us/library/cc756359(v=ws.10).aspx

I am not really sure about ADDS and what is causing it (is your server a member of a domain?); however, if you want to pursue it further, looking into similar issues and threads, some noted that they got the problem resolved by removing and reinstalling the Client for Microsoft Networks located in the properties of your Local Area Connection Adaptor. This had the effect of repairing the remote procedure Call (RPC).

I would suggest that you re-add the ADDS dependancy and try the above (Doing the above requires a restart so you need to do it during a maintenance window). Moreover if it is a production server, then it would be best to have a roll-back plan in case things go wrong (it is not that it is a serious operation, however precautions are always advised.
0
 
Ayman BakrSenior ConsultantCommented:
Just an update. I have tested removing Client for Microsoft Networks and the result is that it corrupted my network UNC path and identification of common commands like CMD. On an attempt (couple of attempts, restarting after each) to install it back, the installation hanged. I ended up doing a system restore for a point prior to uninstallation action.

I would recommend, for resolving this issue, to use either comment #a38848041 or comment #a38843338, as noted by the author, whichever would resolve your issue when consulting this thread.
0
 
BHeshkaAuthor Commented:
Refined answer to only disable conflicting service.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now