When the On-Premise Agent is hosted on a server with a system time that is different from the time on the local PC used to access the TIBCO Scribe® Online User Interface, the TIBCO Scribe® Online Cloud time, or the time on the server where third-party applications used for integration are hosted, you could experience issues similar to the following:
Agent Server Time Different Than Local PCOn the Solution Edit page, when you select Run, the Solution starts and the Status displays in the top right corner. The duration associated with the
In Progress status is affected by the difference between the Agent time and the local PC time. For example, if the PC time is 2 minutes ahead of the Agent time and a Solution starts, the duration associated with the In Progress status immediately goes to 2 minutes.
This can be confusing because the duration as the Solution executes, continues to be inflated. When you view the Execution History after the Solution completes, the duration there would be 2 minutes less than the duration displayed in the Solution Edit Status field. (S41043)
Make sure that the time on the server where the TIBCO Scribe® Online On-Premise Agent is installed and the time on your local PC match.
Agent Server Time Different Than Microsoft Dynamics 365 ServerIn this scenario, a Security Time Stamp Error is generated. This error is the result of an issue in the way Microsoft Dynamics 365 or CRM tracks time. The Dynamics CRM Server, which is set to UTC/GMT, cannot generate a timestamp if the minutes value on the computer where the TIBCO Scribe® Online On-Premise Agent is installed differs by more than 5 minutes from the Dynamics CRM Server time.
The Dynamics CRM Server uses your local time zone. Therefore, this problem only occurs if the minutes, not hours, are off by more than 5 minutes, known as the skew time. To ensure that you do not get this message, make sure the minutes on the computer where the TIBCO Scribe® Online On-Premise Agent is installed reflect the same minutes value as UTC/GMT time.
See the following articles for additional scenarios: