Error Opening Main App

[omni]

Roger,

We have a small location where all users connect using remote access to a terminal server, with no access to the data server. Normally not an issue.

3 times in the last week our main app menu (exe) is failing when they attempt to open. The message is that the Xbase development tool has stopped working. Will not open the menu.
Restarting the main server resolves this, but there is not always a person on site to do that.

Have you ever seen this?

As a note, there is another new client we update that we cannot overwrite the exe when doing the update, even though no users are in the system. All are disconnected and all files are closed. When we open task manager there are always a list of tasks that says Xbase Development Tools, probably one for each user, but just guessing on that. Once we stop those tasks, then we can install the update.

Just thinking that might be related.

Both on Win 12 Server.


Thanks

Fred
Omni

[Tom]

Hi, Fred.

It looks like your app closes all dialogs, but it does not quit in some situations. It stays in the memory, but it doesn't do nothing. The EXE can't be overwritten or deleted then. Check out how and where your application can be "closed". Add some logging to those points. Find out what the last thing was the users did before the situation came up.

[rdonnay]

Are your users logging off before closing the app?

[omni]

Last year in a similar situation, not the same server, we found that we had a similar problem. The network showed no files open, but some users at night would connect via remote access (and probably leave our menu open when disconnecting). On those we used terminal manager and disconnected them. This disconnection also closed all files and we could do the update. It is just an issue with remote connections, not work stations.

Fred
Omni