Valid Analytics.MaxAcceptedClockDeviation values











up vote
1
down vote

favorite












I am trying to increase the Analytics.MaxAcceptedClockDeviation to a large number, but keep getting:




3876 23:11:29 WARN The "Analytics.MaxAcceptedClockDeviation" setting contains an invalid value. The default value is used instead. Invalid value: "0.24:00:00". Default value: "00:00:10"




The default configuration value is:



<setting name="Analytics.MaxAcceptedClockDeviation" value="0.00:00:10" patch:source="Sitecore.Xdb.config"/>


What is valid format for this setting? For example for setting it to 24 hours?










share|improve this question




























    up vote
    1
    down vote

    favorite












    I am trying to increase the Analytics.MaxAcceptedClockDeviation to a large number, but keep getting:




    3876 23:11:29 WARN The "Analytics.MaxAcceptedClockDeviation" setting contains an invalid value. The default value is used instead. Invalid value: "0.24:00:00". Default value: "00:00:10"




    The default configuration value is:



    <setting name="Analytics.MaxAcceptedClockDeviation" value="0.00:00:10" patch:source="Sitecore.Xdb.config"/>


    What is valid format for this setting? For example for setting it to 24 hours?










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I am trying to increase the Analytics.MaxAcceptedClockDeviation to a large number, but keep getting:




      3876 23:11:29 WARN The "Analytics.MaxAcceptedClockDeviation" setting contains an invalid value. The default value is used instead. Invalid value: "0.24:00:00". Default value: "00:00:10"




      The default configuration value is:



      <setting name="Analytics.MaxAcceptedClockDeviation" value="0.00:00:10" patch:source="Sitecore.Xdb.config"/>


      What is valid format for this setting? For example for setting it to 24 hours?










      share|improve this question















      I am trying to increase the Analytics.MaxAcceptedClockDeviation to a large number, but keep getting:




      3876 23:11:29 WARN The "Analytics.MaxAcceptedClockDeviation" setting contains an invalid value. The default value is used instead. Invalid value: "0.24:00:00". Default value: "00:00:10"




      The default configuration value is:



      <setting name="Analytics.MaxAcceptedClockDeviation" value="0.00:00:10" patch:source="Sitecore.Xdb.config"/>


      What is valid format for this setting? For example for setting it to 24 hours?







      xconnect






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 4 hours ago

























      asked 5 hours ago









      Joost

      59911




      59911






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          4
          down vote













          TimeSpan settings in Sitecore use DateUtil.ParseTimeSpan method internally



          Following metadata of that method: Format must be 00:00:00 representing hours, minutes and seconds. A fourth optional part may be added, representing milliseconds (ie. 00:00:00:00)



          You are using "." in the value, which is not correct.(Sitecore don't expect usage of dot character in this type of settings at all). Remove "0." from your setting and I suppose it will start to work.






          share|improve this answer





















          • The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
            – Joost
            4 hours ago













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "664"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15516%2fvalid-analytics-maxacceptedclockdeviation-values%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          4
          down vote













          TimeSpan settings in Sitecore use DateUtil.ParseTimeSpan method internally



          Following metadata of that method: Format must be 00:00:00 representing hours, minutes and seconds. A fourth optional part may be added, representing milliseconds (ie. 00:00:00:00)



          You are using "." in the value, which is not correct.(Sitecore don't expect usage of dot character in this type of settings at all). Remove "0." from your setting and I suppose it will start to work.






          share|improve this answer





















          • The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
            – Joost
            4 hours ago

















          up vote
          4
          down vote













          TimeSpan settings in Sitecore use DateUtil.ParseTimeSpan method internally



          Following metadata of that method: Format must be 00:00:00 representing hours, minutes and seconds. A fourth optional part may be added, representing milliseconds (ie. 00:00:00:00)



          You are using "." in the value, which is not correct.(Sitecore don't expect usage of dot character in this type of settings at all). Remove "0." from your setting and I suppose it will start to work.






          share|improve this answer





















          • The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
            – Joost
            4 hours ago















          up vote
          4
          down vote










          up vote
          4
          down vote









          TimeSpan settings in Sitecore use DateUtil.ParseTimeSpan method internally



          Following metadata of that method: Format must be 00:00:00 representing hours, minutes and seconds. A fourth optional part may be added, representing milliseconds (ie. 00:00:00:00)



          You are using "." in the value, which is not correct.(Sitecore don't expect usage of dot character in this type of settings at all). Remove "0." from your setting and I suppose it will start to work.






          share|improve this answer












          TimeSpan settings in Sitecore use DateUtil.ParseTimeSpan method internally



          Following metadata of that method: Format must be 00:00:00 representing hours, minutes and seconds. A fourth optional part may be added, representing milliseconds (ie. 00:00:00:00)



          You are using "." in the value, which is not correct.(Sitecore don't expect usage of dot character in this type of settings at all). Remove "0." from your setting and I suppose it will start to work.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 4 hours ago









          Anton

          1,646213




          1,646213












          • The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
            – Joost
            4 hours ago




















          • The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
            – Joost
            4 hours ago


















          The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
          – Joost
          4 hours ago






          The following example values seem to work 1.00:00:00 and 24:00:00. Indeed not recommended values for production, but my dev setup has some problems.
          – Joost
          4 hours ago




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Sitecore Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15516%2fvalid-analytics-maxacceptedclockdeviation-values%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          What visual should I use to simply compare current year value vs last year in Power BI desktop

          Alexandru Averescu

          Trompette piccolo