Daniel_Davila

É só você acessar o /server da tua aplicação. http://localhost:8077/MyApp/MyApp.dll/Server voce cria os usuários pelo arquivo .cfg que fica junto do IIS. English: "You need to grant access via the "/server" link of your application. http://localhost:8077/MyApp/MyApp.dll/Server Users are created through the .cfg file located alongside the IIS."

Update for future users: After making the adjustments in IIS that Farshad recommended and properly handling the access violation occurring in the application, the issue of the suspended node ceased to occur.

I will find the cause and post it here, just to keep the solution for other users

Is it possible to add some form of 'observer' to prevent the server module from crashing?

@Farshad Mohajeri With EurekaLog, when the browser is closed and a session times out, we capture this error. The error only occurs in Delphi and UniGUI source codes. My question is whether this exception is truly an error in UniGUI or if it is something caused by our source code. I've attached the Eurekalog file. IDSSaude_DES-0086_20231011165520.el

IDSSaude.exe: 00000D70: 15:59:15 [::1]:Exception raised while destroying session: Access violation at address 0000000000407B76 in module 'IDSSaude.exe'. Write of address 0000000005C55370 IDSSaude.exe: 00000D70: 15:59:15 [Exception-ServerModule]:EXCEPTION - UnAssigned MainModule(Access violation at address 0000000000407B76 in module 'IDSSaude.exe'. Write of address 0000000005C55370) IDSSaude.exe: 00000D70: 15:59:15 [::1]:EAccessViolation : Access violation at address 0000000000407B76 in module 'IDSSaude.exe'. Write of address 0000000005C55370 : Addr: $0000000000407B76 This error freeze the server module and caused the suspended node. We are addressing the issue of the access violation error occurring, but should an exception in the server module freeze the entire node like this? I believe not. Is there a way to work around this to prevent the ServerModule from freezing in this manner?

We have done this.

The problem occurs sometimes when an error occurs during session timeout, such as when the user closes the Chrome tab or the browser. It happens occasionally, but not every day.

The configuration has always been like that.

Yes, Devart Unidac,.

We are facing a very serious issue regarding the use of UniGui with Hyperserver and IIS. At some point, our clients are experiencing an error, primarily an Access Violation, which we are trying to identify the cause of because it doesn't happen all the time. So far, we haven't been able to replicate it in our internal testing environment, but it occurs more than once a day at our client's sites, and we currently have more than 20 clients with this problem. If an error occurs at any point when releasing a session due to closing the browser or a timeout, the node of the system running on Hyperserver goes into a "Suspended" state. In the Hyperserver log, the following message is recorded: [SendCommand Error, Node: 0]: Read timed out [Node #0]: Node Status request timed out. Node purged. As a result, the suspended node disconnects all logged-in users and starts a new instance. However, it was coming up with the same HTTP port, causing lockups in the new instance. We have already fixed this situation by configuring Hyperserver, but the problem of the node in Hyperserver remaining suspended persists. We need clarification from the UniGui team to identify what could cause the node in Hyperserver to be suspended in this manner. We are using: UNIGUI 1563 in the system and Hyperserver. Windows Server 2019. Delphi 10.2. In the ServerModule, the AsyncMode option is not enabled in ISAPIOptions. And the IIS configuration was done according to the manual: https://www.unigui.com/doc/online_help/index.html?hyperserver-isapi-module-mode.htm

Every time when i set the event on runtime the memory leak on unigui will happen?

Up

After setting the CellClick event at runtime, a memory leak occurs when the application is closed, as reported by EurekaLog. How can I fix this issue? I have attached a demo problem with the EurekaLog report for reference. To replicate the issue, simply enable EurekaLog, click on a cell in the grid, and close the application. GridColumnSort.zip NewReport.pdf

Ok thank's