Common System Issues

---

Data Loss and Application Hangs

Check the System Log in the Event Viewer on every computer running Execu/Tech software. Look for Event IDs 26 and 50. If you see Delayed Write Failed or Virtual Memory errors you will experience data loss and application hangs.

​

Delayed Write Failed



Here are a few links to assist with the "Delayed Write Failed" error. You should also have your hardware and network checked out by a qualified technician. The best solution is to replace the computer with one running Windows 7 or newer, though this doesn't guarantee you won't experience the problem. Basically, write caching on the drive (the drive on the server containing the data) is failing. You can disable write caching on the drive, but this might result in very slow overall performance. Consult your IT for assistance.

http://support.microsoft.com/kb/321733
http://support.microsoft.com/kb/330174

​

Virtual Memory errors are most often caused by not having enough RAM but can sometimes be a symptom of a memory leak. It's possible that you just need more RAM because you've updated and added software and the software now uses more RAM. Whether this is a memory leak or just not enough RAM to run modern applications, you can try restarting your computer for some temporary relief.

• Be sure that all users running Execu/Tech software have full permissions to the software folder. Also, be sure that the files in the software folder inherit the permissions of the folder. Failing to do this will result in files created by one user being inaccessible by another user.

• If using Windows Vista, Server 2008, or newer, you MUST NOT install the software to the Program Files or Program Files (x86) folder because of 'folder virtualization'.

• In your antivirus software on the CLIENTS, disable any 'on access' scanning or real time scanning of the software folder on the server. This is known to create severe slowdowns and corrupted data.

• In Windows Vista, Server 2008, or newer, disable UAC (User Account Control) before attempting to register any ActiveX controls. You might also need to disable UAC if an application with an older installer doesn't seem to properly install. You may enable it after successfully registering the controls.

​

"The publisher could not be verified" or "We can't verify who created this file" warning when you run our software over the network.

​

IE security settings are just trying to protect you because it thinks the files are located outside of your local network.

Here are two ways your network administrator can remove the warning:

1.  Add the UNC of the share to Local Intranet Zone. This should only affect customers who's software is several years old.


2. Run 'gpedit.msc', go to User Configuration, then Administrative Templates, then Windows components, then Attachment Manager. Once there, open the settings for Inclusion list for moderate risk file types. Add *.EXE to the list and enable the policy if it isn't already.

Disable 'Power Saving' modes on all hard drives and network cards. This can cause communication interruptions that may cause errors and loss of data when you start using the software after a power saving state has been entered.

 In Remote Desktop, you may find that USB barcode scanners and magnetic card swipes do not seem to work properly. 90% of the time the solution is a simple change to the Remote Desktop Connection settings. Open Remote Desktop Connection then click Options. Go to the Local Resources tab and change the Keyboard setting to 'On the remote computer'. You'll have to successfully connect to the server after making this change for it to be saved.

 With Windows Server 2008R2 you may have an issue with DEP, or Data Execution Prevention, causing the application to crash when you attempt to start it or perform certain functions, like Credit Card Processing. To fix this, go to your Advanced System Settings, then Performance Settings, then Data Execution Prevention, then change the setting to "Turn on DEP for essential Windows programs and services only" and then restart the computer.

If you suddenly experience issues that seem firewall related but you are sure your firewall settings are correct, try toggling the Microsoft Firewall on or off then back, again. We have seen cases where the Windows firewall is on even though it is set to off. Toggling this setting has fixed this issue.