TimeZone related Agentry Client Error (11)

[Former Member]

Hi all,

today (Sunday ) a colleague of mine discovered some very disturbing behavior of the Agentry Client 7.0.5 (also occurs in the Test Environment). The error message (11) on the client is indicating that the connection between client and server has been dropped.

Copying an Agentry.db file (from last week) into the Client directory and resetting the client to that older state resulted in an application crash! It took me a while, but finally, I found some entries in the windows application events log like this one (Source: ".NET Runtime"):

Anwendung: AgentryClient.exe

Frameworkversion: v4.0.30319

Beschreibung: Der Prozess wurde aufgrund eines Ausnahmefehlers beendet.

Ausnahmeinformationen: System.Runtime.InteropServices.SEHException

Stapel:

   bei <Module>._CxxThrowException(Void*, _s__ThrowInfo*)

   bei <Module>.Syclo.TimeZone.{ctor}(Syclo.TimeZone*, std.tstring*)

   bei <Module>.SQLiteStorageManager.getSingleColumnBOP(SQLiteStorageManager*, BusinessObjectPropertyTypes.PropertyType, BusinessObjectProperty*, Processor*, Int32, AgentryModule*)

   bei <Module>.SQLiteStorageManager.populateBusinessObjectDataFromRow(SQLiteStorageManager*, BusinessObject*, BusinessObjectPropertyTypes.PropertyType, Int64, Processor*, Int32, Boolean)

   bei <Module>.SQLiteStorageManager.populateBusinessObjectData(SQLiteStorageManager*, BusinessObject*, BusinessObjectPropertyTypes.PropertyType, Int64, Boolean)

This indicates that the problem is caused by the change from daylight saving time to standard time (which happend to be this night). Changing the date of the windows system time to last week "resolved" the crash problem and also made the error message (11) go away during sync. Obviously this is NO SOLUTION! Is anyone aware of this problem and maybe already got a solution as well?

Thanks in advance,

Daniel

[Former Member · Accepted solution]

Hi all,

for your information. This issue has been resolved in the new client release (7.0.5.4), available for download since yesterday.

Regards, Daniel

[Former Member]

Daniel,

I would suggest you open a issue with the support team so they can have development look into the issue.

The other option is to clear the client and rebuild it to see if resolves the issue after the timezone change.

The US doesn't change the time back until next weekend so only EU and other countries that have the timezone change now would see the error.

Stephen.

[Former Member]

Hi,

clearing the client results in the error 11 during sync, not clearing the client and using the db file results in the client crash.

I guess I will open an issue with support...

Daniel

[Former Member]

Hi again,

I did open an issue on monday, but it does not seem as if anything will happen very soon. I would be interested to hear if or if not this issue occurs in other time zones / in other systems.

Regards, Daniel

[Former Member]

US does the timezone change this weekend so we may see more chases next week.

Stephen

[agentry_src]

Hi Daniel,

Ran into a somewhat similar issue with MII a couple of years ago when the US changes the dates that it implemented Daylight Saving Time.  Ultimately it was resolved with a change to the underlying Java implementation.  What version of Java do you have implemented?

Cheers, Mike

SAP Customer Experience Group - CEG

[Former Member]

Hi Michael,

we are using the JVM provided by the SMP 3.0 (see folder sapjvm_7 in the SMP installation folder). Some further testing shows that it seems to be a WPF Client / Test Environment problem only, on Android devices I cannot see the same kind of behavior.

Regards, Daniel

[agentry_src]

Hi Daniel,

Does not sound like the same issue I experienced.  May want to create a ticket and have the developers take a look.

Regards, Mike

[Former Member]

Hi,

I already did on monday... if anyone is experiencing the same problem, please create tickets as well so this will get more attention. Thank you!

Regards, Daniel