Hi Marco, we have a very similar problem with our customer (Terminal Server, Windows Server 2008 R2, random Uniface crash .... etc.) Was the problem solved in any way? Do we have to force the customer to get a more up-to-date server Windows server? Many thanks Luigi

LG1949 said Hi Marco, we have a very similar problem with our customer (Terminal Server, Windows Server 2008 R2, random Uniface crash .... etc.) Was the problem solved in any way? Do we have to force the customer to get a more up-to-date server Windows server? Many thanks Luigi  

Hi Luigi, If you cannot upgrade to Windows Server 2016 then disabling IAT as described in the other post (An Uniface application that is running on Terminal Server or Citrix may close unexpectedly in Windows Server 2008 R2) should fix the problem. I also heard from a colleague that there is a problem with network shares when a Windows 10 Client is accessing a Windows Server that is older than version 2016. The issue is resolved in the Windows Server 2016 and Microsoft apparently will not fix the problem in older Server versions. Though luck, I guess. Hope this helps. Daniel

Hi Daniel, wonderful solution ! We disabled the IAT parameter and the crashes no longer occurred ! My most sincere thanks Luigi

Basically any version.

diseli said Basically any version.  

Hi, I reopen this post because we are migrating our customer from 9.4 to 9.7.02G201 (32bit), but in this enviroment we have serveral crash after migrate. With Uniface 9.4 crash never appair.   We do the above operations (first method), but the crash is remaining. Our enviroment: Windows 2008R2 (terminal server) Windows 2012 (File server with project and runtime) Oracle 11g   Uniface runnig with this command line \\\\server\\foo untime\\bin\\uniface.exe /asn=\\\\server\\foo\\asn\\cust.asn /ini=\\\\server\\foo\\ini\\cust.ini APS PAR1 PAR2   We try to move the runtime locally, but no change.   We are in huge difficolty on our customer, you have any suggestion?   Marco

Hi, Some toughts: Could you activate proc tracing into your ASN file to understand if Uniface runtime is able to startup or it is crashing directly before any proc code execution? 1) If proc code is reached, analyzing your tracing: are your crashes really random or they could be related to any specific context (a component or a signature or an external library or an integration via 3GL)? 2) I see you are using a customized INI file. Was it migrated (checked against the newest one) or you've directly reused it? 3) Many things changed after leaving apart WinXP; are you using integrations written in 3GL? 4) The issue reported is related to Citrix: are you using Citrix either or just Terminal Server (RDP)? Gianni

Marco said

diseli said Basically any version.  

Hi, I reopen this post because we are migrating our customer from 9.4 to 9.7.02G201 (32bit), but in this enviroment we have serveral crash after migrate. With Uniface 9.4 crash never appair.   We do the above operations (first method), but the crash is remaining. Our enviroment: Windows 2008R2 (terminal server) Windows 2012 (File server with project and runtime) Oracle 11g   Uniface runnig with this command line \\\\server\\foo untime\\bin\\uniface.exe /asn=\\\\server\\foo\\asn\\cust.asn /ini=\\\\server\\foo\\ini\\cust.ini APS PAR1 PAR2   We try to move the runtime locally, but no change.   We are in huge difficolty on our customer, you have any suggestion?   Marco  

Hi Marco, I'm afraid that method 1 (disabling DEP for the Uniface executable) will not work anymore with the version 9.7.02 patch G201. With the Uniface release 9.7.02 the HTML widget has been upgraded to CEF3 and it requires that the DEP policy (Data Execution Prevention) is turned on. The DEP policy is enabled right at the start of the Uniface application (and this will override the workaround mentioned in method 1). This caused problems with some older third party modules (for details see BUG#31255) and as a result the DEP policy is now only enabled when the HTML widget is initialized. This change has been introduced with the patch G202. Maybe you could give it a try with the latest patch for Uniface 9.7, which currently is G307. And did you already check if method 2 will resolve the problem? If this does not work either then we might face a completely different problem here. Hope this helps. Daniel

Hi,

gianni said 1) If proc code is reached, analyzing your tracing: are your crashes really random or they could be related to any specific context (a component or a signature or an external library or an integration via 3GL)?

the incident appears very random, at startup, the execution of form/service or other, and many many cases in a different way

2) I see you are using a customized INI file. Was it migrated (checked against the newest one) or you've directly reused it?

The new ini is built by merging our costum ini with the standard one present in the installation folder, basically adding only the items below in the correct section [widgets] TabEx = utabex FormContainer = ucontainer HTML = uhtml [upi] asynchgui = 0 [screen] DiagramFont = Segoe UI,Western,8,regular ProcboxFont = Courier New,10,regular FormText = Courier New,Western,9,regular

3) Many things changed after leaving apart WinXP; are you using integrations written in 3GL?

We use a custom DLL on different functions, for example at login, but the crash at login is not always, but random so I suspect that is not the cause. We use signature to use Excel API, but I test it and this works correcty.

4) The issue reported is related to Citrix: are you using Citrix either or just Terminal Server (RDP)?

Only on RDP because our customer with Citrix is not migrate.  

Daniel said This caused problems with some older third party modules

Which third part modules? Only OCX or also DLL and signature to call API Excel?

Maybe you could give it a try with the latest patch for Uniface 9.7, which currently is G307. And did you already check if method 2 will resolve the problem?

I will try both last patch that the second method   Thanks Marco

Marco said

Daniel said This caused problems with some older third party modules

Which third part modules? Only OCX or also DLL and signature to call API Excel?   

Basically any third party module (OCX or DLL) that does not work correctly with DEP. Newer versions of Microsoft Office (e.g. Excel) should not cause any problems (if remember it correctly then anything newer than Office 2007 should be okay). Hope this helps. Daniel

Hi Daniel, Thank you for your reply and at this point we will propose to the customer to make this attempt if he does not want to update the operating system. Many thank Luigi