Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Problem with running a Delphi 32bit exe on Windows 2008 Terminal Server after update of this Delphi 32bit executable

Posted on 2011-05-13
Medium Priority
Last Modified: 2012-05-11

We have a problem with updating a Delphi 32bit executable while users are running this
executable on Windows 2008 terminal Server. The executable resides on a remote network
share from another Windwos 2003 File Server and is a single file of 10mb written in Delphi 7.

With the old 2003 terminal server we rename the .exe to .old and copy the new .exe.
Already logged on users continue with the old exe.New users are running the new exe.
No problems.

Now with the new 2008 terminal server we do te same. Rename the .exe to .old and copy the new .exe.
Already logged on users continue with the old exe, no problems for them.
New users are running the old executable according to the main screen but get all
kind of errors (access violations) in de updated modules.
It seems that windows is trying to load the new exe partitially.
When logged on as a domain administrator there are many 100+ minidump....dmp files placed in the
directoty of the executable.

After killing the proces / program for each user the application working fine again if
the exe is started again. Then the new exe is loaded with no problems.
This is no option for us for each update.

Can anyone help with this problem?



Question by:WilliamOorschot

Assisted Solution

pcunite earned 1000 total points
ID: 35757371
Your method of changing out a live and running .exe will not be supported going forward. Window 2008 uses "Address space layout randomization (ASLR) " and that is probably what is causing your error. You need to come up with a better technique ... something like writing to a reg key or file and having the .exe look for the new .exe to load next time. Just forget out touching a running .exe
LVL 14

Expert Comment

ID: 35757406
try to check the compatibility mode of exe properties.
LVL 32

Accepted Solution

Ephraim Wangoya earned 1000 total points
ID: 35820310

Your upgrade program can send a message to all logged on users that the system is going to upgrade in a few minutes and they need to exit the application, if some users are still logged on say after two minutes, log them off automatically then do your upgrade.
As long as the user gets a message that they are about to be upgraded, they should be alright
LVL 101

Expert Comment

ID: 36235313
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
Suggested Courses

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question