exception_eolesyserror_in_module
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
exception_eolesyserror_in_module [2013/05/22 14:29 (11 years ago)] – kevin | exception_eolesyserror_in_module [2020/07/29 16:11 (4 years ago)] (current) – removed kevin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Exception EOleSysError in module ====== | ||
- | [[http:// | ||
- | |||
- | ====== Explanation ====== | ||
- | After upgrading System Five on the server, none of the Terminal Services workstations are able to log into System Five. | ||
- | |||
- | Full Error: | ||
- | |||
- | | ||
- | |||
- | This error will come up when a program is not registered correctly. In the case of the example above, the WindwardPOS.exe file or one of it's components are not registered. It could be the WindwardPOS.exe, | ||
- | |||
- | ====== Detailed Problem Solution ====== | ||
- | |||
- | The simple solution was to reinstall System Five with the S5Install.exe, | ||
- | |||
- | ===== Install on Terminal Services ===== | ||
- | If you have an OLE error on a terminal server. | ||
- | - Create an icon shortcut to WindwardPOS.exe with the command line option /regserver | ||
- | - Run the icon as administrator which will register objects appropriately. | ||
- | |||
- | ---- | ||
- | |||
- | |||
- | Created by Steve Wind May 21 2010 | ||
- | |||
- | Updated by Steve Wind Oct 18 2010 | ||
- | |||
- | ====== | ||
- | [[http:// |
exception_eolesyserror_in_module.1369258168.txt.gz · Last modified: 2013/05/22 14:29 (11 years ago) by kevin