פענוח שגיאה בXP

[צביקי]

Source: W32Time ID: 29 (Windows Operating System 5.1.2600.5512) - Events And Errors Message Center: Message Detailsfunction CloseDiv() {document.all.menuKBsign.src="images/hiderMinus.gif"; menuKBoutline.style.display=''; } // preload images var Open = ""; var Closed = ""; Open = new Image(11,11); Closed = new Image(11,11); Open.src = "images/hiderMinus.gif"; Closed.src = "images/hiderPlus.gif"; function showhide(what,what2,what3) { if (what.style.display=='none') { what.style.display=''; what2.src=Open.src; what3.style.color='#000000'; } else { what.style.display='none'; what2.src=Closed.src; what3.style.color='#003399'; } }

Details Product: Windows Operating System ID: 29 Source: W32Time Version: 5.2 Symbolic Name: MSG_NO_NTP_PEERS_BUT_PENDING Message: The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for %1 minutes. NtpClient has no source of accurate time. Explanation The Windows Time Service cannot synchronize time with its time sources. Windows Time Service will attempt synchronization at a later time.

The W32time 29 message is usually caused by connectivity issues between a client and its source. In some cases, the source computer is unavailable; it may be restarting, disconnected from the network, or unreachable because of firewall or router configurations. If the W32time 29 condition persists, you should immediately troubleshoot the issue to ensure that successful synchronization can resume.

User Action To ensure that the system can connect to the source, do one or more of the following:

• Verify that the local computer is capable of contacting the desired source. In most cases, a simple connectivity test such as “ping” is adequate.
  
• Confirm that Windows Time Service (or other NTP Time Service) is running and available on the source system.
  
• If you are using a manually configured peer, such as time.windows.com, verify that the name is typed correctly and that the system is available.
  
• Confirm that there are no network devices that block traffic on port 123 between the local computer and the time source.

W32time 29 is not a critical message when logged occasionally. It indicates that the system is unable to synchronize, which can present a problem if the condition persists. Always monitor the system after this message appears to ensure that synchronization resumes successfully.

Related Knowledge Base articles

You can find additional information on this topic in the following Microsoft Knowledge Base articles: • Event ID 56 Cites W32Time as Source and Reports That the DC Returned an Incorrectly Signed Time Stamp When you try to gain access to resources in a trusted domain, you may receive an "Access Denied" error message and the System Event log may display the following information: Event Type: Warning Event Source: W32time Event Category: None Event ID:... • Multiple error messages that are similar to Event ID: 29 may occur when you work on a Microsoft Cluster Service (MSCS) cluster that is running Microsoft Windows Server 2003 Describes the problem where multiple error messages that are similar to Event ID: 29 may be logged in the System event log when you work on a Microsoft Cluster Service (MSCS) cluster that is running Windows Server 2003. • In Windows Server 2003 and in Windows XP, W32Time frequently logs Event ID 50, and poor time synchronization occurs When the Windows Time service (W32Time) synchronizes with an external clock, the following event may frequently appear in the System log: In the default domain hierarchy, when a Microsoft Windows Server 2003-based child domain controller tries to... • Directory Service Access Audits for a SAM Object Server Have Incomplete Object Names Audit events (event ID 565) for directory service access may contain truncated distinguished names for the Object Name entries. This problem may occur if the object server is "Security Account Manager." This is an example of an audit with a truncated... • Time synchronization may not succeed when you try to synchronize with a non-Windows NTP server in Windows Server 2003 Describes a problem that may occur when you try to use a non-Windows NTP time server as a time source. Provides steps to let you synchronize to the non-Windows NTP server. • Event ID 528 May Not Be Logged If LsaLogonUser() Is Called Windows 2000 may not log security event ID 528 when a user logs on successfully if the user is authenticated by using the LsaLogonUser function. If the CrashOnAuditFail option is set, the computers stops with code 0xC0000244. • Failure audit event ID 628 occurs when the domain local group member changes the password of another account If you delegate control to a domain local group in Microsoft Windows 2000 Server, and then you assign the group the Reset passwords on user accounts permission (the "User-Force-Change-Password" extended right) for an organizational unit (OU), when a... • Event ID 677 and event ID 673 audit failure messages are repeatedly logged to the Security log of domain controllers that are running Windows 2000 and Windows Server 2003 Fixes an issue where audit failure messages are repeatedly logged to the event security log in domain controllers. Event ID 677 is logged in Windows 2000 and event ID 673 is logged in Windows Server 2003. • The semantic database analysis checker that is included with Ntdsutil.exe may not be able to fix a mangled subref Fixes a problem where Ntdsutil cannot rename a mangled subref after Active Directory replication fails. Provides a hotfix that contains a new version of Ntdsutil. • Random attributes are not migrated when you use the Active Directory Migration Tool version 2 When you use the Active Directory Migration Tool version 2 (ADMT v2) to migrate between two Microsoft Windows 2000 Server domains that are running in native mode, some random attributes may not be set in Active Directory. However, you receive no error... • MS02-001: Forged SID could result in elevated privileges in Windows 2000 Microsoft Windows NT and Windows 2000 protect system resources with access control lists (ACLs). ACLs are lists of security identifiers (SIDs) and lists of access rights or permissions that are granted to that security principal. SIDs are relative... • Availability and description of the Port Reporter tool Describes the Port Reporter tool that you can use to log TCP and UDP port activity on computers that are running Windows Server 2003, Windows XP, and Windows 2000. Contains information about how to obtain, install, and configure the tool.

 

 

אני מקבל את השגיאה הזו ביומן האירועים לאחר קפיאות וקריסות של המחשב. יש רעיונות?

 

תודה , צביקי

[Tzvika-Pick]

W32Time הוא שירות שמכוון את השעון הפנימי של המחשב שלך לפי כמה שרתים מרכזיים באינטרנט.

אתה יכול לבטל אותו בקלות בלוח הבקרה, תחת Date and time ולשונית Internet time.

[ceyal]

או פשוט להוריד עדכון לשעון הקיץ בישראל.

[gsi16v]

לדעתי אין קשר בין הרישום הזה ביומן לבין קריסות המחשב