PC SOFT

FOROS PROFESIONALES
WINDEVWEBDEV y WINDEV Mobile

Inicio â†’ WINDEV 2024 â†’ Terminal Server problem?
Terminal Server problem?
Iniciado por guest, 20,ene. 2016 17:19 - 19 respuestas
Publicado el 20,enero 2016 - 17:19
Good Afternoon everyone,

I have a Windev 15 program that runs perfectly happily on several different terminal servers, but on one particular server I'm having some issues.

After completing a certain transaction (entering a sales order) the system simply malfunctions - it won't open a screen correctly any more, even if the user logs out (of my system and the terminal server).

The only way I can get him working again is to make a copy of the .exe! So, TradaBase.exe becomes Tradabase - Copy.exe and the user can work again.

Has anyone ever encountered anything like this?

Kind Regards
Reg
Publicado el 20,enero 2016 - 17:32
Hi,

Maybe there is some malware or virus active on that TS ?

Danny
Publicado el 21,enero 2016 - 10:51
I suppose it's possible, but wouldn't it affect every user?
Publicado el 21,enero 2016 - 11:53
Need clarification please.

Are you saying that this only happens on one particular machine, TS1, and only one particular user, User A? So User B on TS1 has no problems, and if User A was on TS2 then there are no problems?
Publicado el 21,enero 2016 - 12:02
Hi,

The problem is only occurring on TS1.

I have this morning managed to recreate the problem with a second user on TS1.

In both cases logging out of the program and/or TS1 does not solve the problem, but launching the renamed executable does work.
Publicado el 21,enero 2016 - 12:42
Hey Reg,

Give the Profiler a try. I think it's been around since WX v9 so should be available to you in V15.

http://help.windev.com/en-US/…

You can turn it on/off with code, but you can also turn it on/off with the key combinations; WINKEY + SHIFT + F10 and WINKEY + SHIFT + F11.

It records the actions of your application into an analysis/log file. I've used it in the past to track down bottlenecks in performance, but maybe you can use it to see whats going on "under the hood" of your application?

The Help says:
From any application: pressing WIN + SHIFT + F10 has the same effect as the call to ProfilerStart. In this case, the analysis ends: •when the application is stopped, •via WIN + SHIFT + F11. When the recording stops, the location of the analysis report is copied into the clipboard.
HTH...
Publicado el 21,enero 2016 - 12:57
I'll give it a try - thanks...
Publicado el 22,enero 2016 - 18:02
Ok, I have an update for anyone who's interested.

I found some entries in the registry on the terminal server. These entries seemed to be named after windows in my application, including the window which has been 'malfunctioning'.

I deleted these registry entries and the user who has been experiencing the problem has been fine until just now.

Does anyone know why/when Windev creates entries in the register for windows?

Rgds
Reg
Publicado el 22,enero 2016 - 18:12
Only way I know of affecting the registry is directly via the related commands/function of WDLanguage or when installing the application because the installer allows you to "play" with registry entries at application install time.
Publicado el 22,enero 2016 - 18:16
I'm definitely not doing anything like that. The entries seem mainly to relate to tables ...
Publicado el 22,enero 2016 - 22:14
Hi SolutionJ-Reg,

could the register-entry be caused by an AAF-function the user has used on some moment?
Publicado el 23,enero 2016 - 12:56
Hi

Windev writes in the registry all the settings of windows (positions, tables columns, etc) so that it can reopen at the same place and all that beautiful stuff

If you don't want it to write in the registry, you can change that by using the initparameter function, by example to tell windev to write in an xml file instead

Best regards
Publicado el 26,enero 2016 - 08:45
Thanks Fabrice

Do you happen to know if global variables (declared in the Window) also be stored in the registry?
Publicado el 26,enero 2016 - 13:55
Hi

they are NOT (there would be no point, as windev does not keep/reuse values of variables from one execution to the next). What is kept is what's automatic (AAF)

Best regards
Publicado el 26,enero 2016 - 13:57
Ok, thanks. I'm guessing the problem the user is having is related to some aspect of his Terminal Server login. I rebooted the Terminal Server over the weekend and he is still having the same problem this morning with one of the windows in my system whereas every other use is working fine.
Publicado el 26,enero 2016 - 14:14
Well, maybe he used the aaf to change and store the order of the columns, or something similar to that, only on that window.

That's why I was saying to try and store the info in an xml file instead, in case he doesn't have the proper permissions to write in the registry

Best regards
Publicado el 26,enero 2016 - 14:18
ok, thanks...
Publicado el 28,enero 2016 - 10:08
We had this too. Same reason. Stored values on controls etc.

It's easy to identify the registry key so you could run a simple script to delete the keys on login. (I think they are stored in the HKEY_LOCAL_USER hive so this would work without elevated privs)

It's either that or go through all your controls and turn off 'store the value'...

Bosh
Publicado el 28,enero 2016 - 10:43
Hi bosh,

That's brilliant, thanks. I thought I was going mad with this :confused

Cheers
Reg
Publicado el 28,enero 2016 - 13:27
or a simple initparameter at the beginning of the project code...

On 1/28/2016 4:08 AM, bosher wrote:
We had this too. Same reason. Stored values on controls etc.

It's easy to identify the registry key so you could run a simple script
to delete the keys on login. (I think they are stored in the
HKEY_LOCAL_USER hive so this would work without elevated privs)

It's either that or go through all your controls and turn off 'store the
value'...

Bosh