Time Sync Issue (w32tm debug help)

M

Mark Pfeifer

Repost for managed support...

I am running Vista 32-bit with SP2 and I am unable to sync the time via the
w32tm service. I just get an error on the screen with no entries in the
system event viewer. Listed below is the debug of w32tm /resync
/rediscover ... and the UI attempt to update.

Can anyone shed any light on this? Other ntp clients work fine and I am
able to do a stripchart command against time.windows.com w/o an issue. So,
I don't think it is a firewall issue.

Any ideas? TIA
Mark

****************************************
149166 22:37:38.4257189s - ---------- Log File Opened -----------------
149166 22:37:50.9993189s - RPC Caller is
(S-1-5-21-1037478806-2609463539-4057573387-1000)
149166 22:37:50.9993189s - RPC Call Attribute is local=1, kernel=0,
session=0, authentication=6, protocol=2, OpNum=0
149166 22:37:50.9993189s - RPC Call - Rediscover
149166 22:37:50.9993189s - W32TmServiceMain: Network Topology Change (RPC)
149166 22:37:50.9993189s - TimeProvCommand([NtpClient], TPC_NetTopoChange)
called.
149166 22:37:50.9993189s - NtpProvider: Network Topology Change
149166 22:37:50.9993189s - Peers reset: p-p:1 a-p:1 a-x:0
149166 22:37:50.9993189s - NtpProvider: Created 0 sockets.
149166 22:37:50.9993189s - StartListeningThread completed!
149166 22:37:50.9993189s - PeerPollingThread: waiting forever
149166 22:37:50.9993189s - StartPeerPollingThread completed!
149166 22:37:50.9993189s - W32TmServiceMain: waiting 983.204s
149166 22:37:50.9993189s - W32TmServiceMain: ********** Time Slip
Notification **********
149166 22:37:50.9993189s - PeerPollingThread: PeerListUpdated
149166 22:37:50.9993189s - PeerPollingThread: waiting forever
149166 22:37:50.9993189s - ClockDispln TimeSlip:TimeSlip LastUTC:70046
SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
149166 22:37:50.9993189s - TimeProvCommand([NtpClient], TPC_TimeJumped)
called.
149166 22:37:50.9993189s - W32TmServiceMain: waiting i16.000s (1024.000s)
149166 22:37:50.9993189s - PeerPollingThread: PeerListUpdated
149166 22:37:50.9993189s - PeerPollingThread: waiting forever
149166 22:38:07.0049189s - W32TmServiceMain: timeout
149166 22:38:07.0049189s - W32TmServiceMain: waiting 1024.000s
Click to expand...

BTW - Here is the log after the UI attempts to update

149166 22:42:17.2065189s - RPC Caller is
(S-1-5-21-1037478806-2609463539-4057573387-1000)
149166 22:42:17.2065189s - RPC Call Attribute is local=1, kernel=0,
session=0, authentication=6, protocol=2, OpNum=0
149166 22:42:17.2065189s - RPC Call - HardResync
149166 22:42:17.2065189s - W32TmServiceMain: ********** Time Slip
Notification **********
149166 22:42:17.2065189s - ClockDispln TimeSlip:TimeSlip LastUTC:87111
SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
149166 22:42:17.2065189s - TimeProvCommand([NtpClient], TPC_TimeJumped)
called.
149166 22:42:17.2065189s - W32TmServiceMain: waiting i16.000s (1024.000s)
149166 22:42:17.2065189s - PeerPollingThread: PeerListUpdated
149166 22:42:17.2065189s - PeerPollingThread: waiting forever
149166 22:42:33.2121189s - W32TmServiceMain: timeout
149166 22:42:33.2121189s - W32TmServiceMain: waiting 1024.000s
149166 22:42:33.2121189s - RPC Call - Query provider status
149166 22:42:33.2121189s - TimeProvCommand([NtpClient], TPC_Query) called.
149166 22:42:33.2121189s - RPC Caller is
(S-1-5-21-1037478806-2609463539-4057573387-1000)
149166 22:42:33.2121189s - RPC Call Attribute is local=1, kernel=0,
session=0, authentication=6, protocol=2, OpNum=6
149166 22:42:33.2121189s - RPC Call - Query Status
149166 22:42:33.2121189s - W32TimeHandler called:
SERVICE_CONTROL_PARAMCHANGE
149166 22:42:33.2121189s - W32TmServiceMain: Param change notification
149166 22:42:33.2121189s - ReadConfig: Found provider 'NtpClient':
149166 22:42:33.2121189s - ReadConfig: 'Enabled'=0x00000001
149166 22:42:33.2121189s - ReadConfig:
'DllName'='C:\Windows\system32\w32time.dll'
149166 22:42:33.2121189s - ReadConfig:
'DllName'='C:\Windows\system32\w32time.dll'
149166 22:42:33.2121189s - ReadConfig:
'DllName'='C:\Windows\system32\w32time.dll'
149166 22:42:33.2121189s - ReadConfig: 'InputProvider'=0x00000001
149166 22:42:33.2121189s - ReadConfig: Found provider 'NtpServer':
149166 22:42:33.2121189s - ReadConfig: 'Enabled'=0x00000000
149166 22:42:33.2121189s - ReadConfig:
'DllName'='C:\Windows\system32\w32time.dll'
149166 22:42:33.2121189s - ReadConfig:
'DllName'='C:\Windows\system32\w32time.dll'
149166 22:42:33.2121189s - ReadConfig:
'DllName'='C:\Windows\system32\w32time.dll'
149166 22:42:33.2121189s - ReadConfig: 'InputProvider'=0x00000000
149166 22:42:33.2121189s - ReadConfig: 'PhaseCorrectRate'=0x00000001 (2)
149166 22:42:33.2121189s - ReadConfig: 'UpdateInterval'=0x00057E40 (2)
149166 22:42:33.2121189s - ReadConfig: 'FrequencyCorrectRate'=0x00000004 (2)
149166 22:42:33.2121189s - ReadConfig: 'PollAdjustFactor'=0x00000005 (2)
149166 22:42:33.2121189s - ReadConfig: 'LargePhaseOffset'=0x02FAF080 (2)
149166 22:42:33.2121189s - ReadConfig: 'SpikeWatchPeriod'=0x00000384 (2)
149166 22:42:33.2121189s - ReadConfig: 'HoldPeriod'=0x00000005 (2)
149166 22:42:33.2121189s - ReadConfig: 'MinPollInterval'=0x0000000A (2)
149166 22:42:33.2121189s - ReadConfig: 'MaxPollInterval'=0x0000000F (2)
149166 22:42:33.2121189s - ReadConfig: 'AnnounceFlags'=0x0000000A (2)
149166 22:42:33.2121189s - ReadConfig: 'LocalClockDispersion'=0x0000000A (2)
149166 22:42:33.2121189s - ReadConfig: 'MaxNegPhaseCorrection'=0x0000D2F0
(2)
149166 22:42:33.2121189s - ReadConfig: 'MaxPosPhaseCorrection'=0x0000D2F0
(2)
149166 22:42:33.2121189s - ReadConfig: 'EventLogFlags'=0x00000002 (2)
149166 22:42:33.2121189s - ReadConfig: 'MaxAllowedPhaseOffset'=0x00000001
(2)
149166 22:42:33.2121189s - ReadConfig: 'TimeJumpAuditOffset'=0x00007080 (2)
149166 22:42:33.2121189s - No params changed for local clock.
149166 22:42:33.2121189s - /--TimeProvider: new enabled provider list
149166 22:42:33.2121189s - | Name:NtpClient, Started:0, Input:1, Marked:0,
RefCount:0, DllName:C:\Windows\system32\w32time.dll
149166 22:42:33.2121189s - >--
149166 22:42:33.2121189s - | Total:1, Input: 1, Marked: 0
149166 22:42:33.2121189s - \--
149166 22:42:33.2121189s - /--TimeProvider: Parameter change before list is
updated
149166 22:42:33.2121189s - | Name:NtpClient, Started:1, Input:1, Marked:0,
RefCount:0, DllName:C:\Windows\system32\w32time.dll
149166 22:42:33.2121189s - >--
149166 22:42:33.2121189s - | Total:1, Input: 1, Marked: 0
149166 22:42:33.2121189s - \--
149166 22:42:33.2121189s - /--TimeProvider: new disabled provider list
149166 22:42:33.2121189s - | Name:NtpServer, Started:0, Input:0, Marked:0,
RefCount:0, DllName:C:\Windows\system32\w32time.dll
149166 22:42:33.2121189s - >--
149166 22:42:33.2121189s - | Total:1, Input: 0, Marked: 0
149166 22:42:33.2121189s - \--
149166 22:42:33.2121189s - /--TimeProvider: Parameter change before list is
updated
149166 22:42:33.2121189s - | Name:NtpServer, Started:0, Input:0, Marked:0,
RefCount:0, DllName:C:\Windows\system32\w32time.dll
149166 22:42:33.2121189s - >--
149166 22:42:33.2121189s - | Total:1, Input: 0, Marked: 0
149166 22:42:33.2121189s - \--
149166 22:42:33.2121189s - TimeProvCommand([NtpClient], TPC_UpdateConfig)
called.
149166 22:42:33.2121189s - ReadConfig:
'AllowNonstandardModeCombinations'=0x00000001 (2)
149166 22:42:33.2121189s - ReadConfig: 'CompatibilityFlags'=0x80000000 (2)
149166 22:42:33.2121189s - ReadConfig: 'SpecialPollInterval'=0x00093A80 (2)
149166 22:42:33.2121189s - ReadConfig:
'ResolvePeerBackoffMinutes'=0x0000000F (2)
149166 22:42:33.2121189s - ReadConfig:
'ResolvePeerBackoffMaxTimes'=0x00000007 (2)
149166 22:42:33.2121189s - ReadConfig: 'EventLogFlags'=0x00000001 (2)
149166 22:42:33.2121189s - ReadConfig: 'LargeSampleSkew'=0x00000003 (2)
149166 22:42:33.2121189s - ReadConfig: 'Type'=NTP (2)
149166 22:42:33.2121189s - ReadConfig: 'NtpServer'=time.windows.com,0x9 (2)
149166 22:42:33.2121189s - ReadConfig:
'ManualPeerList'(parsed)='time.windows.com,0x9'
149166 22:42:33.2121189s - ManualPeerListUpdate: add:0 del:0 noch:1
149166 22:42:33.2121189s - StartListeningThread completed!
149166 22:42:33.2121189s - PeerPollingThread: waiting forever
149166 22:42:33.2121189s - StartPeerPollingThread completed!
149166 22:42:33.2121189s - Provider list: 0 stopped, 0 started, 1 not
changed.
149166 22:42:33.2121189s - /--TimeProvider: Parameter change after list is
updated
149166 22:42:33.2121189s - | Name:NtpClient, Started:1, Input:1, Marked:0,
RefCount:0, DllName:C:\Windows\system32\w32time.dll
149166 22:42:33.2121189s - >--
149166 22:42:33.2121189s - | Total:1, Input: 1, Marked: 0
149166 22:42:33.2121189s - \--
149166 22:42:33.2121189s - W32TmServiceMain: waiting 1024.000s
 
R

Robinson Zhang [MSFT]

Hello Mark,

Thank you for posting.

From your post, my understanding on this issue is: Windows Vista SP2 cannot
sync the time via the w32tm service, and you can do a stripchart command
against time.windows.com. If I'm off base, please feel free to let me know.

Before moving on, could you please let me know if the computer is in a
domain? Do you have other Windows Vista computers have same problem?
Thanks.

Mostly, the following factors can cause w32tm service issue:

1. Third party time synchronization product was installed on the computer.
2. Security software block network Ports.
3. Incorrect w32tm service settings.
4. Corrupted system file.
5. Group Policy.

Given the current situation, I have following suggestions:

Suggestion 1: Register dll file and reset SNTP.
============
Please run the following command in a elevate privileges cmd window.

net stop w32time
w32tm /unregister
w32tm /register
regsvr32 c:\windows\system32\w32time.dll
net time /setsntp:time.windows.com,0x1
net start w32time

Then, please test the issue again. If the issue still persists, please take
the following suggestions.

Suggestion 2: Reset Windows Time Service related group policy
============
1. Click Start, click Run, type gpedit.msc , and then click OK.
2. In the Group Policy Object Editor MMC snap-in, expand Computer
Configuration, expand Administrative Templates, expand System, and then
click Windows Time Service.
3. In the right pane, right-click Global Configuration Settings, and then
click Properties.
4. In the Global Configuration Settings Properties dialog box, click Not
Configured, and then click OK.
5. Expand Windows Time Service, click Time Providers, and then set all the
objects in this node to Not Configured. To do this, follow these steps: a.
In the right pane, double-click Enable Windows NTP Client, click Not
Configured, and then click OK.
b. In the right pane, double-click Configure Windows NTP Client, click Not
Configured, and then click OK.
c. In the right pane, double-click Enable Windows NTP Server, click Not
Configured, and then click OK.

Suggestion 3: Take a Clean Boot
============
1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar
and Press "Enter" to start the System Configuration Utility.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box
and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
4. Restart the computer and test the issue.

Please monitor the system in the Clean Boot environment. If the problem
does not occur, it indicates that the problem is related to one application
or service we have disabled. You may use the MSCONFIG tool again to
re-enable the disabled item one by one to find out the culprit.

Does it work? I am looking forward to your reply.

Thanks.

Best regards,

Robinson Zhang
Microsoft Online Support
 
M

Mark Pfeifer

Robinson -

Thank you for your reply. The computer is in a workgroup (not a domain),
another Vista machine (same Dell model) does not have the issue.

Yes, you are correct, Vista SP2 cannot sync the time and I can get access
via w32tm commands to servers. Also, there are no errors in the event log.

I have tried your suggestions with no luck. (1) re-registered DLLs, no
change in behaviour, (2) checked GPs and everything was not configured, (3)
MSConfig restricted start - same issue. Still unable to sync.

Any other ideas? It seems so simple. Yet, I am concerned there is nothing
reported in the event viewer.

Thanks
Mark

"Robinson Zhang [MSFT]" said:
Hello Mark,

Thank you for posting.

From your post, my understanding on this issue is: Windows Vista SP2
cannot
sync the time via the w32tm service, and you can do a stripchart command
against time.windows.com. If I'm off base, please feel free to let me
know.

Before moving on, could you please let me know if the computer is in a
domain? Do you have other Windows Vista computers have same problem?
Thanks.

Mostly, the following factors can cause w32tm service issue:

1. Third party time synchronization product was installed on the computer.
2. Security software block network Ports.
3. Incorrect w32tm service settings.
4. Corrupted system file.
5. Group Policy.

Given the current situation, I have following suggestions:

Suggestion 1: Register dll file and reset SNTP.
============
Please run the following command in a elevate privileges cmd window.

net stop w32time
w32tm /unregister
w32tm /register
regsvr32 c:\windows\system32\w32time.dll
net time /setsntp:time.windows.com,0x1
net start w32time

Then, please test the issue again. If the issue still persists, please
take
the following suggestions.

Suggestion 2: Reset Windows Time Service related group policy
============
1. Click Start, click Run, type gpedit.msc , and then click OK.
2. In the Group Policy Object Editor MMC snap-in, expand Computer
Configuration, expand Administrative Templates, expand System, and then
click Windows Time Service.
3. In the right pane, right-click Global Configuration Settings, and then
click Properties.
4. In the Global Configuration Settings Properties dialog box, click Not
Configured, and then click OK.
5. Expand Windows Time Service, click Time Providers, and then set all
the
objects in this node to Not Configured. To do this, follow these steps: a.
In the right pane, double-click Enable Windows NTP Client, click Not
Configured, and then click OK.
b. In the right pane, double-click Configure Windows NTP Client, click
Not
Configured, and then click OK.
c. In the right pane, double-click Enable Windows NTP Server, click Not
Configured, and then click OK.

Suggestion 3: Take a Clean Boot
============
1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar
and Press "Enter" to start the System Configuration Utility.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box
and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
4. Restart the computer and test the issue.

Please monitor the system in the Clean Boot environment. If the problem
does not occur, it indicates that the problem is related to one
application
or service we have disabled. You may use the MSCONFIG tool again to
re-enable the disabled item one by one to find out the culprit.

Does it work? I am looking forward to your reply.

Thanks.

Best regards,

Robinson Zhang
Microsoft Online Support
Click to expand...
 
M

Mark Pfeifer

Also, on the machine that is working the DLL is version 18000 and mine is
18005.

Thanks
Mark

"Robinson Zhang [MSFT]" said:
Hello Mark,

Thank you for posting.

From your post, my understanding on this issue is: Windows Vista SP2
cannot
sync the time via the w32tm service, and you can do a stripchart command
against time.windows.com. If I'm off base, please feel free to let me
know.

Before moving on, could you please let me know if the computer is in a
domain? Do you have other Windows Vista computers have same problem?
Thanks.

Mostly, the following factors can cause w32tm service issue:

1. Third party time synchronization product was installed on the computer.
2. Security software block network Ports.
3. Incorrect w32tm service settings.
4. Corrupted system file.
5. Group Policy.

Given the current situation, I have following suggestions:

Suggestion 1: Register dll file and reset SNTP.
============
Please run the following command in a elevate privileges cmd window.

net stop w32time
w32tm /unregister
w32tm /register
regsvr32 c:\windows\system32\w32time.dll
net time /setsntp:time.windows.com,0x1
net start w32time

Then, please test the issue again. If the issue still persists, please
take
the following suggestions.

Suggestion 2: Reset Windows Time Service related group policy
============
1. Click Start, click Run, type gpedit.msc , and then click OK.
2. In the Group Policy Object Editor MMC snap-in, expand Computer
Configuration, expand Administrative Templates, expand System, and then
click Windows Time Service.
3. In the right pane, right-click Global Configuration Settings, and then
click Properties.
4. In the Global Configuration Settings Properties dialog box, click Not
Configured, and then click OK.
5. Expand Windows Time Service, click Time Providers, and then set all
the
objects in this node to Not Configured. To do this, follow these steps: a.
In the right pane, double-click Enable Windows NTP Client, click Not
Configured, and then click OK.
b. In the right pane, double-click Configure Windows NTP Client, click
Not
Configured, and then click OK.
c. In the right pane, double-click Enable Windows NTP Server, click Not
Configured, and then click OK.

Suggestion 3: Take a Clean Boot
============
1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar
and Press "Enter" to start the System Configuration Utility.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box
and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
4. Restart the computer and test the issue.

Please monitor the system in the Clean Boot environment. If the problem
does not occur, it indicates that the problem is related to one
application
or service we have disabled. You may use the MSCONFIG tool again to
re-enable the disabled item one by one to find out the culprit.

Does it work? I am looking forward to your reply.

Thanks.

Best regards,

Robinson Zhang
Microsoft Online Support
Click to expand...
 
R

Robinson Zhang [MSFT]

Hi Mark,

Thank you for your detail information.

According to previous troubleshooting, we know the w32tm service works
fine. Given the situation, I suggest we confirm the following points at
this time:

1. Confirm Time Zone. Incorrect Time Zone setting in registry may cause
sync problem. Please try to change Time Zone to another location and change
it back.
2. Enable netmon to capture network packets on the computer. The reason why
we doing it is to check if Windows receives response from time.windows.com.

1) Download NetMon3.3 from the following website and install it on the
computer
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b
941d-06cb-4658-b7f6-3088333d062f
2) Launch NetMon3.3.
3) In the Microsoft Network Monitor 3.3 window, click Create a new capture
tab ¡­
4) In the new tab, select all the Network Adapters in the Select Networks
window.
5) Go to sync time page. Then, switch to Network Monitor, press F5 to start
NetMon.
6) Try to sync time.
7) Go back to the NetMon window and press F7 to stop the NetMon.
8) Press Ctrl+S to save the Netmon file named test.

Please upload the file to Windows Live SkyDrive
(http://www.skydrive.live.com/) and share the URL with us.

Thank you for your cooperation. I am looking forward to your reply.

Thanks.

Best regards,

Robinson Zhang
Microsoft Online Support
 
R

Robinson Zhang [MSFT]

Hi Mark,

Thank you for your reply. We have made progress on the issue. Now we know
the issue only occurs when using UI sync time.

Before moving on, I would like to let you know UI doesn't use time service
when sync time. So we can focus on the UI component. I have following
suggestions:

1.Try to switch to other time server, such as time.nist.gov or
time-a.nist.gov. Does it work?
2.Run SFC to scan system files to check if it is caused by corrupt system
file.

Use the System File Checker (SFC) to scan system files
=====================================================
The System File Checker tool enable an administrator to scan all protected
files to verify their versions. To do so, follow these steps:

1. Click "Start", type "CMD" (without quotation marks) in the "Start
Search" box. Right click on the "CMD.exe" file, choose "Run as
Administrator"
2. Copy and paste "SFC /Scannow" (without quotation marks) in the "Open"
box, and click "OK".

Note: There is a SPACE between "SFC" and "/Scannow", this command will take
several minutes to complete and may require access to the Windows
installation source files. If you are prompted to insert the CD, click
"Continue" each time it prompts.

Does it work? Hope it helps.

Best regards,

Robinson Zhang
Microsoft Online Support
 
R

Robinson Zhang [MSFT]

Hello Mark,

How are you doing? I am just checking to see how things are going there on
this issue. If you would like further assistance, please do not hesitate to
let me know. It is my pleasure to help. :)

Thanks, and have a great day!

Best regards,

Robinson Zhang
Microsoft Online Support
 
M

Mark Pfeifer

Robinson -

I had replied to your message which you replied to :) I guess you missed
it.

Thanks. There is no network traffic that I can see when I use the date/time
user interface. I have attached to files - one is the date_ui capture and
the other is the stripchart command for the same server. You will see
network traffic on the stripchart using w32tm but not the date time ui. I
think.

Thanks
Mark

http://cid-4b81f747617c9dfe.skydrive.live.com/browse.aspx/.Public?uc=2
 
R

Robinson Zhang [MSFT]

Hi Mark,

It seems a problem was occurred when I sent my previous email to you.
However, I re-post my reply which was sent on 06/03/2009 as follows.
Thanks.

--------------------------------------------------

Hi Mark,

Thank you for your reply. We have made progress on the issue. Now we know
the issue only occurs when using UI sync time.

Before moving on, I would like to let you know UI doesn't use time service
when sync time. So we can focus on the UI component. I have following
suggestions:

1.Try to switch to other time server, such as time.nist.gov or
time-a.nist.gov. Does it work?
2.Run SFC to scan system files to check if it is caused by corrupt system
file.

Use the System File Checker (SFC) to scan system files
=====================================================
The System File Checker tool enable an administrator to scan all protected
files to verify their versions. To do so, follow these steps:

1. Click "Start", type "CMD" (without quotation marks) in the "Start
Search" box. Right click on the "CMD.exe" file, choose "Run as
Administrator"
2. Copy and paste "SFC /Scannow" (without quotation marks) in the "Open"
box, and click "OK".

Note: There is a SPACE between "SFC" and "/Scannow", this command will take
several minutes to complete and may require access to the Windows
installation source files. If you are prompted to insert the CD, click
"Continue" each time it prompts.

Does it work? Hope it helps.

Best regards,

Robinson Zhang
Microsoft Online Support
 
M

Mark Pfeifer

None of the time servers work. Even added one and that didn't work either.
Also, nothing found or corrected on the SFC scan.

Ugg! Other ideas?

Thanks

Mark
 
R

Robinson Zhang [MSFT]

Hi Mark,

Thank you for your latest information. I have involved my colleagues and we
need time to do some research. I will contact you as soon as possible.

Thank you for your understanding.

Best regards,

Robinson Zhang
Microsoft Online Support
 
R

Robinson Zhang [MSFT]

Hi Mark,

Here is Robinson again. Could you please help me collect a screenshot of
error message when using UI sync time?

Please upload the file to Windows Live SkyDrive
(http://www.skydrive.live.com/) and share the URL with us.

Thank you for your cooperation.

Best regards,

Robinson Zhang
Microsoft Online Support
 
R

Robinson Zhang [MSFT]

Hello Mark,

We suspect the issue is caused by following factors:

1.A specific software block it.
2.System file corrupt.

Given the situation, it is recommended to test the issue in Safe Mode.
Thank you for your cooperation.

Windows Time service will not work under Safe Mode by default. To make
Windows Time work under Safe Mode, you need to create a registry entry for
Safe Mode you are logged in to.

1.Start the computer in Safe Mode with network.
2.Click Start, type CMD and press Enter.
3.Please run the following commands one by one.

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\W32time"
/VE /T REG_SZ /F /D "Service"

net start w32time

4.Then, Windows Time service will be started.

Please test the issue by UI. Does it work?

If the issue still persist, we will focus on the system file next time.

Thanks.

Best regards,

Robinson Zhang
Microsoft Online Support
 
M

Mark Pfeifer

Robinson -

Thanks - I tried the steps below and the service started just fine.
However, no luck on the UI. Tried several servers and all gave the same
error message w/o anything in the event log.

Next up? <g>

Thanks for continuing with this,
Mark
 
R

Robinson Zhang [MSFT]

Hi Mark,

Could you please help me collect a screenshot of error message when using
UI sync time?

Please upload the file to Windows Live SkyDrive
(http://www.skydrive.live.com/) and share the URL with us.

Thank you for your cooperation.

Best regards,

Robinson Zhang
Microsoft Online Support
 
R

Robinson Zhang [MSFT]

Hi Mark,

I am writing as a courtesy to follow-up on this issue. Do you have any
updates? If so, please let me know at your earliest convenience. I am
standing by for your reply and am happy to be of further assistance. Thanks!

For your reference, I have re-posted my previous post.
------------------------------
Hi Mark,

Could you please help me collect a screenshot of error message when using
UI sync time?

Please upload the file to Windows Live SkyDrive
(http://www.skydrive.live.com/) and share the URL with us.

Thank you for your cooperation.

Best regards,

Robinson Zhang
Microsoft Online Support
 
R

Robinson Zhang [MSFT]

Hi Mike,

As the new report issue you mentioned is different from the one discussed
in this current thread, we'd recommend that you start up a new thread for
it. We generally focus on one topic in one thread because in this way it
will be better for other community members to participate in the
discussion, and to search/find specific answers more efficiently in the
future.

Thank you for your understanding.

Best regards,

Robinson Zhang
Microsoft Online Support
 
M

Mark Pfeifer

Mark Pfeifer said:
Robinson -

Thanks - I tried the steps below and the service started just fine.
However, no luck on the UI. Tried several servers and all gave the same
error message w/o anything in the event log.

Next up? <g>

Thanks for continuing with this,
Mark

"Robinson Zhang [MSFT]" said:
Hello Mark,

We suspect the issue is caused by following factors:

1.A specific software block it.
2.System file corrupt.

Given the situation, it is recommended to test the issue in Safe Mode.
Thank you for your cooperation.

Windows Time service will not work under Safe Mode by default. To make
Windows Time work under Safe Mode, you need to create a registry entry
for
Safe Mode you are logged in to.

1.Start the computer in Safe Mode with network.
2.Click Start, type CMD and press Enter.
3.Please run the following commands one by one.

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\W32time"
/VE /T REG_SZ /F /D "Service"

net start w32time

4.Then, Windows Time service will be started.

Please test the issue by UI. Does it work?

If the issue still persist, we will focus on the system file next time.

Thanks.

Best regards,

Robinson Zhang
Microsoft Online Support
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

w32tm debug help 1
Domain Controller Unable to connect to the Time Server 0
An error occurred while Windows was synchronizing with time.nist.g 3
change res. for VIA EPIA-M (CLE 266) doesn't work 4
Can't set display settings in TD using Intel(R) 82945G Express video driver 6
STOP 7B when booting El Torito CD 6
kept rebooting when FBA 9
FBA error 1

Top