Hi all! We are experiencing the following problem: On our 2008 server, we have 2 virtual servers, both 2003 64bit. When I reboot 1 of these machines, i get a message saying that a service was unable to start. Ater checking the eventviewer, I found out that it was the time service. So in services.msc I tried to start but in stead of starting, it gives me an error, saying that he couldn't find a file. After unregistering and registering the service, I'm able to start the service. These are 2 event logs i am getting: Event Type: ErrorEvent Source: W32TimeEvent Category: NoneEvent ID: 30Date: 15-7-2009Time: 20:10:31User: N/AComputer: FANGORNDescription:The time service encountered an error while reading its configuration from the registry and cannot start. The error was: The system cannot find the file specified. (0x80070002)For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp. Event Type: ErrorEvent Source: W32TimeEvent Category: NoneEvent ID: 46Date: 15-7-2009Time: 20:10:31User: N/AComputer: FANGORNDescription:The time service encountered an error and was forced to shut down. The error was: 0x80070002: The system cannot find the file specified.For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp. I tried searching with google on the internet and the technet forums but I can't find something similar anywhere. Please help

Hi FontaThis problem may occur when your computer sends synchronization requests by using symmetric active mode. By default, Windows Server 2003 domain controllers are configured as time servers and use symmetric active mode to send synchronization requests. Some NTP servers that do not run Windows respond only to requests that use client mode.Click Start, click Run, type cmd, and then press Enter. At the command prompt, type the following commands in the order that they are given. After you type each command, press Enter: w32tm /config /manualpeerlist:NTP_server_IP_Address, 0x8 syncfromflags:MANUAL net stop w32time net start w32time w32tm /resyncAfter applying these steps, the problem should be solved. Refer Url:http://support.microsoft.com/kb/932462http://support.microsoft.com/kb/892501Hope this help. Deva Tomorrow's life is too late. Live today.

Hello,have a look here:http://technet.microsoft.com/en-us/library/cc733213(WS.10).aspxhttp://www.eventid.net/display.asp?eventid=46&eventno=3032&source=W32Time&phase=1Are the servers usihng SP2 and the latest available patches?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Hi deva_1002, I tried those steps you provided, but after a reboot, the service won't start anymore.

Hi Meinolf, As stated on the pagehttp://technet.microsoft.com/en-us/library/cc733213(WS.10).aspxi checked the permissions in the registry. The time service is started with local service account which has the permissions on the different register keys. When I precisly do what they tell me to do on that page and so, unregister and register the service, I am able to start the service but after a reboot,it doesn't work anymore. The both servers are using SP2 and have the latest patches.

Hi all! this issue is solved! After enabling debug logging for the time server i got the following: 149220 10:07:10.1265000s - ---------- Log File Opened ----------------- 149220 10:07:10.1265000s - Entered W32TmServiceMain W2K3SP1 149220 10:07:10.1265000s - CurSpc:15625000ns BaseSpc:15625000ns SyncToCmos:Yes 149220 10:07:10.1265000s - PerfFreq:3579545c/s 149220 10:07:10.1265000s - Time zone OK. 149220 10:07:10.1265000s - ReadConfig: Found provider 'NtpClient': 149220 10:07:10.1265000s - ReadConfig: 'Enabled'=0x00000001 149220 10:07:10.1265000s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll' 149220 10:07:10.1265000s - ReadConfig: 'InputProvider'=0x00000001 149220 10:07:10.1265000s - ReadConfig: Found provider 'NtpServer': 149220 10:07:10.1265000s - ReadConfig: 'Enabled'=0x00000000 149220 10:07:10.1265000s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll' 149220 10:07:10.1265000s - ReadConfig: 'InputProvider'=0x00000000 149220 10:07:10.1265000s - ReadConfig: Found provider 'VMICTimeProvider': 149220 10:07:10.1265000s - Logging error: The time service encountered an error while reading its configuration from the registry and cannot start. The error was: The system cannot find the file specified. (0x80070002) 149220 10:07:10.1265000s - Service shutdown initiated with exit code: -2147024894. 149220 10:07:10.1265000s - Exiting ServiceShutdown 149220 10:07:10.1265000s - ---------- Log File Closed ----------------- Because the service initiated his shutdown after finding the VMICTimeProvider, i thought something must be wrong with the integration services of hyper-v. So, I inserted the integration services disk and clicked OK to do a repair. When this finished, I rebooted the server and the error was gone!

Damn it, how strange!The problem returned. After every reboot of the server the service can't start anymore.When I take a look in the registry I see inHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\A folder called VMICTimeProviderWhich has another folder beneath it, called Parameters.When I remove the VMICTimeProvider folder, the time service is able to start but after a reboot, the folder is back in the registry and sothe time service can't start.What can I do to prevent the VMICTimeProvider folder from coming back?

Anyone who can help me on this one?

Hello,if you find out it is Hyper-V related better use:http://social.technet.microsoft.com/Forums/en/winserverhyperv/threadsorhttp://social.technet.microsoft.com/Forums/en/windowsserver2008r2virtualization/threadsBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

I had a similar problem, solved it by disabling the "Time Synchronization" for the virtual machine in Integration Services on the Hyper-V host. Then stopping and disabling the "Hyper-V Time Synchronization Service", in the services on the virtual machine. And finaly removing the vmictimeprovider folder in the registrey on the virtual machine, before restarting it. Apparently the "Hyper-V Time Synchronization Service" is inserted when you first run the integration services, and not removed when running repair.