Skip to main content
K
khoppe15-Moonstone
15-Moonstone
January 10, 2019
Solved

Using ILM via Citrix lead temporarily to wrong timestamp in local Sandbox

  • January 10, 2019
  • 1 reply
  • 2668 views

We are using ILM 10.9 on Server with a 10.4 Client providing via Terminal Server (Citrix), to allow especially for external Partner Access to Integrity without the Need of local Tool Installation.

Server-sided we use as Default Setting the Working Timestamp as Revision Timestamp.

We now face the issue that from time to time the Timestamp within the Sandbox differs from the Timestamp stored on the Server.  Testing this issue more detailed it doesn't matter whether we use the Resync-Option "Restore Revision Timestamp" or not, syncing data lead randomly to such Timestamp deviations, usually with only 1 or 2 Seconds.

 

Does anybody have an idea of Root Cause?

Can it be avoided?

(If I could force the behavior, I would create a case ....)

 

Hoping on a usefull hint,

Klaus

Best answer by kthierer

Just for curiosity:

If you dont use "Restore Revision Timestamp" how would you then detect a time deviation?

 

This makes me remenber an issue I called "Pseudo Diffs". These can happen regulary e.g. if build tools

regenerate Makefiles without changing them.
My procedure then was: if "si diff member" reports no differences then resync the member.

This might be a repair approach in case you also have "Pseudo Diffs"

 

SETLOCAL ENABLEDELAYEDEXPANSION
mkdir .PTCTMP 2> nul
type nul > .PTCTMP\IntegrityMembersPseudoDiff.txt
si print -R --revision=:head --format="{membername}\n" --noHeaderFormat --noTrailerFormat --filter=changed:working > .PTCTMP\IntegrityMembers.txt

@REM :: si diff per Member
echo OFF
@FOR /F "tokens=*" %%i IN (.PTCTMP\IntegrityMembers.txt) DO (
 echo si diff "%%i"
 si diff "%%i" 1> nul 2>nul
 @if !errorlevel! == 0 (
 echo %%i >> .PTCTMP\IntegrityMembersPseudoDiff.txt
 ) else (
 echo DIFF::::::::::::: %%i && echo %%i >> .PTCTMP\IntegrityMembersDiff.txt
 )
)
si resync -F .PTCTMP\IntegrityMembersPseudoDiff.txt

1 reply

K
kthierer12-AmethystAnswer
12-Amethyst
February 19, 2019

Just for curiosity:

If you dont use "Restore Revision Timestamp" how would you then detect a time deviation?

 

This makes me remenber an issue I called "Pseudo Diffs". These can happen regulary e.g. if build tools

regenerate Makefiles without changing them.
My procedure then was: if "si diff member" reports no differences then resync the member.

This might be a repair approach in case you also have "Pseudo Diffs"

 

SETLOCAL ENABLEDELAYEDEXPANSION
mkdir .PTCTMP 2> nul
type nul > .PTCTMP\IntegrityMembersPseudoDiff.txt
si print -R --revision=:head --format="{membername}\n" --noHeaderFormat --noTrailerFormat --filter=changed:working > .PTCTMP\IntegrityMembers.txt

@REM :: si diff per Member
echo OFF
@FOR /F "tokens=*" %%i IN (.PTCTMP\IntegrityMembers.txt) DO (
 echo si diff "%%i"
 si diff "%%i" 1> nul 2>nul
 @if !errorlevel! == 0 (
 echo %%i >> .PTCTMP\IntegrityMembersPseudoDiff.txt
 ) else (
 echo DIFF::::::::::::: %%i && echo %%i >> .PTCTMP\IntegrityMembersDiff.txt
 )
)
si resync -F .PTCTMP\IntegrityMembersPseudoDiff.txt
K
khoppe15-MoonstoneAuthor
15-Moonstone
February 19, 2019

Thanks for approach.

In the meantime we decided to not use certain Filters in an Integrity Client started from a Terminal Server with writing a Sandbox to a Remote Drive.

Have a great day.

Terms & ConditionsCookie settingsAccessibility statement