6 Replies Latest reply on Sep 24, 2008 7:55 AM by Sylvain DO Not Use Trudel DO Not Use

    PDM clock sync error

    Jeremy Laha
      This is the message I am receiving from my Design Eng team.

      Failed to add the new file to the vault
      Error = 'E_EDM_UNSYNCED_CLOCK'
      Description = 'the client clock must be synchronized with the sql server clock.'

      They modify there local clock on there computers and lets them add the file to the vault. Seems to keep getting worst. Looking for some ideas to try.
      thanks
        • PDM clock sync error
          Joy Garon
          Hi Jeremy -

          My guess is that you are not ruuning 2008. (This should not be a problem in 2008).

          This occurs when PDME detects that the system clock on the server and the client are not in sync.

          To fix, download a clock sync utility (like Atomic Clock Sync) and run on the server and the client.

          This should fix the problem.

          Joy
          • PDM clock sync error
            Michael Dekoning
            Jeremy,

            About the best thing I could come up with before we upgraded to 2008 was a report a user could run to tell him what the SQL server time was so that he could set the clock on his pc. Not all of our users have internet access so we couldn't use the atomic clock sync solution.

            Mike
            • PDM clock sync error
              Josh Mings
              for a quick fix. you can double-click your clock in the task manager and adjust it up or down 30 seconds. It can't be more than 30 seconds out of sync.
                • PDM clock sync error
                  Spencer Smith
                  Or...

                  Open Notepad, paste in the following (substituting your PDM server name for "pdmserver"):
                  net time \\pdmserver /set /y

                  Save it as a .bat file and stick it in the Startup folder for your user profile.

                  This will sync your local PC time to the PDM server every time you login. When we were on v2007 this eliminated the problem, and I just left it in place now that we are on v2008.

                  Spencer
                    • PDM clock sync error
                      Sylvain DO Not Use Trudel DO Not Use
                      Here are several solutions to get the time synched.

                      -Sylvain

                      OCTOBER, 2006
                      TIME SYNCHRONISATION
                      The PDMWorks Enterprise database server and client workstation clocks must be within 30 seconds of each other. If they are more than 30 seconds apart; an error will be shown stating that the clocks are not synchronised.
                      It is essential to ensure synchronization often to minimize time gap.
                      In a network that has varied network client software, different workgroups, and different domains, maintaining a logon script that issues a net time command can become complex. The solution to keeping all workstations' time synchronized with a particular server is either to run a logon script for each workstation or to have each workstation run a batch file on its own after logging on to the network.
                      For Windows XP: To synchronise the clocks you can add the following statement to the login script:
                      NET TIME \\SQLSERVERNAME /SET /YES
                      References: http://support.microsoft.com/kb/314090/

                      HOW TO SYNCHRONIZE THE TIME ON A MEMBER COMPUTER IN AN ACTIVE DIRECTORY DOMAIN
                      If the computers belong to an Active Directory domain, the Windows Time service configures itself automatically by using the Windows Time service that is available on domain controllers. The Windows Time service configures a domain controller in its domain as a reliable time source and synchronizes itself periodically with this source.
                      Type the following line to resynchronize to the server:
                      W32TM /RESYNC /NOWAIT /REDISCOVER

                      HOW TO SYNCHRONIZE AN INTERNAL TIME SERVER WITH AN EXTERNAL SOURCE
                      You can have Windows contact a time server. You can find a list at http://tf.nist.gov/service/time-servers.html
                      An alternative is to type the following lines in acomand line, where peerlist is a comma-separated list of Domain Name System (DNS) names or IP addresses of the appropriate time sources.
                      W32TM /CONFIG /SyncFromFlags:Manual /ManualPeerList: peerlist
                      W32TM /CONFIG /UPDATE
                      Where peerlist is 0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org
                      W32TM /CONFIG /SyncFromFlags:Manual /ManualPeerList:0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org
                      W32TM /CONFIG /UPDATE
                      NET STOP W32TIME
                      NET START W32TIME
                      To get NTP servers, visit: http://ntp.isc.org/bin/view/Servers/NTPPoolServers
                      References: http://support.microsoft.com/kb/307897
                      http://www.pool.ntp.org/use.html
                      http://www.windowsnetworking.c...ows-Time-Service.html

                      HOW TO STOPS AND START TIME SERVICE
                      After changing the W32TM configuration, stop and restart the Windows Time service using the following commands:
                      NET STOP W32TIME && NET START W32TIME
                      By placing the characters && between two DOS commands in Windows 2000, you can have the second command execute only if the first one ran successfully without errors.

                      FIREWALL
                      UDP port 123 is the default port used by SNTP, which is the protocol used by W32Time for time synchronization over a network. Furthermore, if you deployed Windows XP Service Pack 2 then you need to ensure UDP port 123 is also opened on Windows Firewall on your desktop machines as well.

                      HOW TO ASSIGN A LOGON SCRIPT TO A PROFILE FOR A LOCAL USER
                      A local logon script runs when the local user logs on locally to the computer but does not run when the user logs on to the domain.
                      The default location for local logon scripts is the %SystemRoot%\System32\Repl\Import\Scripts folder. You must share this folder by using the share name netlogon. The script is usually a DOS batch file .bat
                      References: http://support.microsoft.com/kb/315245
                      (end)