Jun 08, 2011 Windows Vista and later (Windows 7, Windows Server 2008, and Windows Server 2008 R2) In Windows Vista and later, the firewall service is 'Windows Firewall' (MPSSVC); it combines both Firewall and IPsec functionality. Hi, I just installed Mezzmo version 2.4.2.0 on my computer using windows 7 64 bits. When i try to start the server, i have this error 'Error 1068 The Dependency. To access the shadow copies on your Windows Server 2008 R2 server, the users must be running an operating system that supports the Shadow Copy Client. Windows Vista, Windows 7, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 all have built-in support for the Shadow Copy Client. Dec 04, 2012 Hi, I´ve created a service in a windows server 2008 R2, but when I try to start the service: Windows could not start the Test service on Local Computer Error 1068.
Active3 years, 5 months ago
This issue seems to be widely discussed, but I have problems with finding the solution in my particular case.
My service is set up to be running under
Local System
account. On my first machine with Windows 7 SP1 (64-bit) installed, everything works as expected. But, just after I try to start the service on my second machine with Windows Server 2008 R2 SP1 (64-bit), not even a second passes, and I'm facing this annoying error: The
System Log
shows 2 entries: and:
The implementation looks following:
Program.cs:
ProService.cs:
The
jwaliszkojwaliszkoOnStart
method is just starting a new thread, so it takes almost NO time load to execute. I used RequestAdditionalTime
statement just in case - to reject this matter as a source of my problem. In addition, as you can see, I'm handling all of the exceptions, but no exception is written to my custom service event log during the startup (btw: logging is working on the first win7 machine). How to investigate what's going on ?12k1818 gold badges7979 silver badges141141 bronze badges
5 Answers
I've figured out what was going on in a few steps:
- I've written console application - wrapper for what is basically done in
OnStart
method from service. - I've executed console application - application started normally.
- I've copied content of service configuration file to console application configuration file.
- I've executed console application once again - application aborted silently and immediately (surprisingly similar to our service behavior, something is wrong).
- I've compared 2 configs - from service, and original from console application. As a result I've found some differences. Among others, there was such an entry - the source of the problem (after removal, everything works):
So basically I had out of date configuration file. Previously service was compiled under .NET 4.5, then I've changed the framework to 4.0 and deployed files to the server, but left the previous configuration file (I've changed the target framework because my development machine has .NET 4.5 while server does not). I wouldn't have thought the shown lines would hide all problems without any reasonable information, which could help to track the mess. Bungie.
jwaliszkojwaliszko12k1818 gold badges7979 silver badges141141 bronze badges
![X64 X64](/uploads/1/2/6/0/126060662/791895612.png)
Check for missing dependencies/DLLs.
If you haven't already done so, allow your service to be invoked as a regular application (a great technique for long-term debugging) and see if it starts properly on your Windows 2008 machine.
If works that way, then there may be an issue with running in the LocalSystem account. Move on to starting your application from a command prompt running in the LocalSystem account (example setup here).
CoreTechCoreTech2,04211 gold badge1414 silver badges2222 bronze badges
I tried the following fix which was provided at this link
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
- In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER. - Right-click ServicesPipeTimeout, and then click Modify.
- Click Decimal, type 60000, and then click OK.
This value represents the time in milliseconds before a service times out. - Restart the computer.
But still I had the problem to start the service.
The fix which worked for me was,
- Go the services.msc
- Double click the service which you are trying to start.
- Take the Logon Tab
- Changed Log on as: to Local System account.
- Tried starting the service after this change.(Still gave the 1053 error)
- Took the Log on tab again, changed it to Network Service (gave a random new password)
- Tried starting the service again.(The service started perfectly)
5,61244 gold badges3939 silver badges5757 bronze badges
Ramachandran GokulachandranRamachandran Gokulachandran
I tried the below steps. It worked like a charm.
1.Go the services.msc2.Double click the service which you are trying to start.3.Take the Logon Tab4.Changed Log on as: to Local System account.5.Tried starting the service after this change.(Still gave the 1053 error)6.Took the Log on tab again, changed it to Network Service (gave a random new password)7.Tried starting the service again.(The service started perfectly)
But I just want to know what will be the issue.
SrinivasanSrinivasan
![1068 1068](/uploads/1/2/6/0/126060662/231378710.jpg)
After installing service, i have to gave full control permission(Everyone) for installation folder. Then, my service will started perfectaly.
user5185809user5185809
Not the answer you're looking for? Browse other questions tagged .netwindows-serviceswindows-server-2008-r2 or ask your own question.
Active5 years, 8 months ago
Could somebody please help me identify an issue I suddenly started having with Replication between 2 of our DCs. I inherited this system which was working perfectly fine but the problem happened suddenly and I am not too sure where to start looking.
This is a school with 2 DCs, both are on Server 2008R2 SP1:
DC1 is also a DNS server
DC2 is also DNS, DHCP and Deployment Server
A couple of days ago I created a policy object and realized that group policies stopped working across the domain. The error message indicated that the gpt.ini file for the policy could not be found.
As soon as I remove the object everything goes back to normal.I tested out the SYSVOL shares on each of the servers by creating files manually and the shares are visible between both of them however if I create a new policy object the physical files for it are not created even locally on the DC that I am working on at the time.
So I ran DCDIAG on both servers and found that DC1 has this error message:
After looking inside Services I am unable to start the File Replication Service or the DFS Service because it gives out an 1068 error saying that 1 of its dependencies cannot be started.
What could be causing this? I ran SFC and it found no errors
ArturskiArturski
2 Answers
Have you checked the services the FRS and DFS depend upon. Checking the Properties of both, it looks like they both depend upon RPC, which in turn depends upon DCOM Server Process Launcher, and RPC Endpoint Mapper. Check these to be sure that they are running or runable.
My guess is that you will find an issue with one of these.
BillNBillNActive Directory
1,16811 gold badge1111 silver badges2727 bronze badges
I have resolved the issue. The problem was the COM+ Event System Service.
After carefully looking through services list and troubleshooting the RPC issues I realised that the COM+ Event System which is supposed to be on automatic start has stopped. When I started the service it automatically stopped and after searching around it lead me to this article which solved the issue.
Dell Servers
ArturskiArturski