AW: O$4.3.1 crashing on Terminal Server

[Krüger, Stefanie]

Hi Mary,

I just upgraded my customers from Studio 3.2.1 to Studio 4.3.1.4. They were running 3.2.1 on Terminal Server for years without any problems apart from the known issues with missing or wrong or corrupt printer drivers at startup.
Now they have several crashes a day and are not amused to have payed money for worsen their situation...

There are 2 things I found out already:
- Ole2auto.dll from 4.3.1.4 is buggy (not a Terminal Server issue!). I reported this to Tech Support and got a new one. Crashes reduced a bit after installing it.

- 3.2.1 was quit forgiving about zerodivide. In reports it just showed a '?' as a result and continued execution. 4.3.1.4 reacts in 2 ways: sometimes it issues an error message, in other cases it just crashes. I can't see any difference in the code, in both cases it's just a calulate x as y/z where z is 0. This one also is not related to Terminal Server. I sent a lib and some Dr.Watsons about this to Tech Support yesterday evening.

So maybe your crashes are not related to terminal server but to "normal" bugs in Studio 4?

Regards,
Steffi

-----Ursprüngliche Nachricht-----
Von: omnisdev-en-bounces at lists.omnis-dev.com [mailto:omnisdev-en-bounces at lists.omnis-dev.com] Im Auftrag von Mary Whittaker
Gesendet: Mittwoch, 8. April 2009 07:12
An: OmnisDev List - English
Betreff: O$4.3.1 crashing on Terminal Server


Hi all,

We are trying to run our Omnis app on Windows Terminal Server and
encountering a bizarre error :

        Quitting Omnis due to unrecoverable error.
        Unexpected error code : 1
        APPFMT.CPP:4645

Omnis Tech Support have indicated that they don't support Omnis
running on Terminal Server (or Citrix or Winframe), although they
know that many developers happily do.  They have referred us to this
list for help!!

I have driven myself nuts trying to diagnose the cause of the
problem, because it is quite random, but here are some things that I
have found so far.

1)      It crashes if the client is Remote Desktop.  It doesn't crash if
the client is CoRD (on Mac).  (However, CoRd does ugly things to some
of the graphics !)
2)      It crashes if the user on the windows machine is the same on both
sessions or different
3)      It often crashes when we open a module that opens a separate
library (but not always).  When we open a separate library we copy
objects from the main library to the secondary library and I was
wondering if this might cause access violation issues.
4)      The secondary library contained a timer procedure.  However, I
turned it off and it made no difference.

I will keep experimenting, but was wondering if anyone has any ideas
about what could cause such as problem.  It may save me a lot of time
(and a lot of hair !!)



Kind Regards

Mary Whittaker
Senior Business Analyst





Office:  61 08 8203 0500
mobile: 0417 848028
Email: mary at clintelsystems.com.au


_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com

 
________________________________________________
Unternehmensinformationen nach § 35a GmbHG
Vivantes
Netzwerk für Gesundheit GmbH
Oranienburger Straße 285
13437 Berlin

Geschäftsführer
Joachim Bovelet (Vorsitz)
Dr. Dorothea Dreizehnter
Manfred Rompf
Peter Schnitzler

Vorsitzender des Aufsichtsrats
Dr. Hartmann Kleiner
Amtsgericht Charlottenburg
HRB 77849