2017-08-24 49 views
0

我得到這個錯誤Kingswaysoft安全時間戳錯誤在動態CRM Kingswaysoft

System.Exception: An error occurred when updating the component's output columns based on the most recent CRM metadata: KingswaySoft.IntegrationToolkit.DynamicsCrm.CrmServiceException: CRM service call returned an error: An error has occurred when retrieving metadata for CRM entity 'xxxx': CRM service call returned an error: The security timestamp is stale because its creation time ('2017-08-24T17:19:05.744Z') is too far back in the past. Current time is '2017-08-24T17:38:18.038Z', maximum timestamp lifetime is '00:05:00' and allowed clock skew is '00:05:00'. (SSIS Integration Toolkit for Microsoft Dynamics 365, v9.0.0.6522 - devenv, v14.0.25420.1)KingswaySoft.IntegrationToolkit.DynamicsCrm.CrmServiceException

: CRM service call returned an error: The security timestamp is stale because its creation time ('2017-08-24T17:19:05.744Z') is too far back in the past. Current time is '2017-08-24T17:38:18.038Z', maximum timestamp lifetime is '00:05:00' and allowed clock skew is '00:05:00'.System.ServiceModel.Security.MessageSecurityException

: The security timestamp is stale because its creation time ('2017-08-24T17:19:05.744Z') is too far back in the past. Current time is '2017-08-24T17:38:18.038Z', maximum timestamp lifetime is '00:05:00' and allowed clock skew is '00:05:00'. (SSIS Integration Toolkit for Microsoft Dynamics 365, v9.0.0.6522 - devenv, v14.0.25420.1)

這些軟件包設置正確,如果我重新啓動Visual Studio幾次它自我修復。這似乎是隨機發生的,絕對看起來像一個錯誤。有沒有什麼辦法解決這一問題?

回答

0

我沒有遇到這個錯誤,但它似乎是一個系統時間問題。您是否確保所有計算機/服務器上的系統時間自動與中央服務器同步?